Should the message be dismissable?

if possible yes, given that the echo notification is redirecting newcomers to this exact dialog.

What should the exact copy be?

Congrats on {$threshold*} edits! Available suggested edits have changed.

*or total edits if count is > threshold after deploying this feature.

after chatting with @KStoller-WMF we decided that the copy should be valid for both newcomers reaching this milestone after a community admin has set a threshold, but also for those newcomers beyond the threshold (given that the system is going to change their selection).

original copy (where 100 is equal to {$THRESHOLD})

• Congrats on 100 edits! Available suggested edits have changed.

proposals:

1. Congrats on passing 100 edits! Available suggested edits have changed.
2. Congrats on reaching 100 edits! Available suggested edits have changed.
3. Congrats on your 100th edit! Available suggested edits have changed.

design recommends to go with option 3.

Change #1151249 had a related patch set uploaded (by Sergio Gimeno; author: Sergio Gimeno):

[mediawiki/extensions/GrowthExperiments@master] [WIP] feat(AddLink): add reinforcing message when the task is unavailable

https://gerrit.wikimedia.org/r/1151249

I'm unsure on what storage to use for "remembering" the message dismissal. @Michael mentioned about user options but, even if we use conditional defaults for this, bisecting all users from a big wiki between greater/lesser than 10, 50, 200, 500 edits will mostly result into also two big balanced cohorts. LocalStorage is not ideal for a consistent experience over time and devices so unless @Urbanecm_WMF or @Cyndymediawiksim have alternative ideas for this, we'd have to go with user options.

One possible action to pay some user option debt, aside from using conditional defaults where possible, would to consolidate some options into a json blob, specially those that have similar meaning/prupose like seen discovery tours, dismissed modals, etc.

In T393920#10899057, @Sgs wrote:

I'm unsure on what storage to use for "remembering" the message dismissal. @Michael mentioned about user options but, even if we use conditional defaults for this, bisecting all users from a big wiki between greater/lesser than 10, 50, 200, 500 edits will mostly result into also two big balanced cohorts. LocalStorage is not ideal for a consistent experience over time and devices so unless @Urbanecm_WMF or @Cyndymediawiksim have alternative ideas for this, we'd have to go with user options.

One possible action to pay some user option debt, aside from using conditional defaults where possible, would to consolidate some options into a json blob, specially those that have similar meaning/prupose like seen discovery tours, dismissed modals, etc.

@Sgs if dismissing the message is non-trivial, we could also explore a design solution that works around existing technical constraints. here's a rough idea: instead of displaying the message below the task, we could "hide" it behind an info button

if dismissing the message is non-trivial, we could also explore a design solution that works around existing technical constraints

👍 I'm in support of limiting the complexity of this task. This menu isn't viewed often, so let's aim to pursue a solution that doesn't require a major effort.

In T393920#10901441, @KStoller-WMF wrote:

if dismissing the message is non-trivial, we could also explore a design solution that works around existing technical constraints

👍 I'm in support of limiting the complexity of this task. This menu isn't viewed often, so let's aim to pursue a solution that doesn't require a major effort.

thanks, i'm going to update figma and the screenshots in the task description.

task description updated. a few notes:

• when the task is disabled, we can hide the 🤖 Machine suggestions verbiage
• for the info icon, i've used the the upcoming button small T352201. if it's not ready by the time we need it, we can fallback to the current quiet icon-only button
• popover is cdx-popover. popover title is the same as the task label, eg. "Add links between articles"
• the copy is the same as T393771, expect the metrics part "Congrats on your 100th edit! Articles you’ve edited received 17,210 views recently. Available suggested edits have changed."

In T393920#10903763, @AAlhazwani-WMF wrote:

task description updated. a few notes:

• for the info icon, i've used the the upcoming button small T352201. if it's not ready by the time we need it, we can fallback to the current quiet icon-only button
• popover is cdx-popover. popover title is the same as the task label, eg. "Add links between articles"

These won't be possible because the suggested edits module is built with OOUI. See also T393769#10905618

In T393920#10908627, @Sgs wrote:

In T393920#10903763, @AAlhazwani-WMF wrote:

task description updated. a few notes:

• for the info icon, i've used the the upcoming button small T352201. if it's not ready by the time we need it, we can fallback to the current quiet icon-only button
• popover is cdx-popover. popover title is the same as the task label, eg. "Add links between articles"

These won't be possible because the suggested edits module is built with OOUI. See also T393769#10905618

acknowledged, let's use what's available in OOUI then, eg. fieldset help:

This is how it looks with the OOUI component, pretty close:

Let me know about the final copy.

In T393920#10909403, @Sgs wrote:

This is how it looks with the OOUI component, pretty close:

looks gooood, thank you!

Let me know about the final copy.

let's go for {@THRESHOLD} edits, congrats! Available suggested edits have changed.

i'll update the task description. mostly as FYI, when i was thinking about this copy, i was trying to make it possible to re-use the strings for the notification copy too (shared parts in bold)

100 edits, congrats!
+
Articles you’ve edited received 17,210 views recently.
+
Available suggested edits have changed.

Change #1151249 merged by jenkins-bot:

[mediawiki/extensions/GrowthExperiments@master] feat(AddLink): add reinforcing message when the task is unavailable

https://gerrit.wikimedia.org/r/1151249

Checked in beta - all functionality is in place.

Moving to Design review column (@AAlhazwani-WMF) - any follow-ups are needed for minor UI issues?
Note: - wouldn't it be confusing for users with more than the current limit on edits suddenly be congratulated on the number of edits that reflects only the limit of the 'Stop suggesting "Add a link" tasks..." option on CommunityConfiguration/Suggested edits page without any additional explanation?

figma design	eswiki beta
	- a small info icon is bigger than in figma - creating a misalignment effect
	(1) icons are of different sizes (2) font in the popover should be bigger? ( see this comment that approves a preliminary implementation)

The intro tour with the disabled Add link task:

Mobile UI:

In T393920#10940461, @Etonkovidova wrote:

Checked in beta - all functionality is in place.

Moving to Design review column (@AAlhazwani-WMF) - any follow-ups are needed for minor UI issues?

yes, we'd like to address these UI issues. specifically, even if we're using OOUI, we can style the info button following the styling of the cdx-button--size-small, see https://doc.wikimedia.org/codex/latest/components/demos/button.html#button-sizes-1

we'd like to vertically align the info button with the checkbox.

we'd like these changes to be applied on desktop, on mobile, and in the info tour.

Note: - wouldn't it be confusing for users with more than the current limit on edits suddenly be congratulated on the number of edits that reflects only the limit of the 'Stop suggesting "Add a link" tasks..." option on CommunityConfiguration/Suggested edits page without any additional explanation?

yeah, that might happen. i'll file a separate task for considering a bespoke copy for newcomers beyond the threshold.

figma design	eswiki beta
	- a small info icon is bigger than in figma - creating a misalignment effect

same feedback as above.

	(1) icons are of different sizes (2) font in the popover should be bigger? ( see this comment that approves a preliminary implementation)

(1) the icons sizes are different by design, so they can stay as is. and for (2) we can keep it as is, it's probably a misalignment between the codex popover (used in figma), and the OOUI popover (used in code).

The intro tour with the disabled Add link task:

same feedback as above. we should also uncheck the checkbox.

Mobile UI:

same feedback as above.

Change #1163808 had a related patch set uploaded (by Sergio Gimeno; author: Sergio Gimeno):

[mediawiki/extensions/GrowthExperiments@master] css(AddLink): decrease icon size and adjust vertical align

https://gerrit.wikimedia.org/r/1163808

Change #1163809 had a related patch set uploaded (by Sergio Gimeno; author: Sergio Gimeno):

[mediawiki/extensions/GrowthExperiments@master] fix(StartEditing): avoid showing unavailable tasks as selected

https://gerrit.wikimedia.org/r/1163809

In T393920#10940461, @Etonkovidova wrote:

The intro tour with the disabled Add link task:

Could you give me the specific steps that got you to this panel? I'm struggling to reproduce it. This what the GuidedTour "homepage welcome" looks like for me, and it seems like a clearly different panel:

I got to my by executing new mw.Api().saveOption( 'growthexperiments-tour-homepage-welcome', '0' ) in the console and then reloading the homepage.

Change #1163808 merged by jenkins-bot:

[mediawiki/extensions/GrowthExperiments@master] css(AddLink): decrease icon size and adjust vertical align

https://gerrit.wikimedia.org/r/1163808

In T393920#10950490, @Michael wrote:

In T393920#10940461, @Etonkovidova wrote:

The intro tour with the disabled Add link task:

Could you give me the specific steps that got you to this panel? I'm struggling to reproduce it. This what the GuidedTour "homepage welcome" looks like for me, and it seems like a clearly different panel:

I got to my by executing new mw.Api().saveOption( 'growthexperiments-tour-homepage-welcome', '0' ) in the console and then reloading the homepage.

Basically, I was checking a somewhat edge case:

• • a user reached the limit with Add link
• for some reason, that user reset all user settings in Preferences - Homepage will be disabled
• a user enables Homepage and get the tour. The previous edit count of Add link limit would be preserved - that's was a purpose of the test to check if a user can reset the count.

Change #1163809 merged by jenkins-bot:

[mediawiki/extensions/GrowthExperiments@master] fix(StartEditing): avoid showing unavailable tasks as selected

https://gerrit.wikimedia.org/r/1163809

@KStoller-WMF @Sgs there has been feedback on dewiki that this message could be improved
https://de.wikipedia.org/wiki/Wikipedia_Diskussion:Neulings-Startseite#c-Isderion-20251013094700-Johannnes89-20251013085400

The current message congratulates users on their edit count and mentions that the available tasks have changed without much explanation. It might be better to explicitly state that easy tasks like add a link are only available until a user reached a certain edit count?

Thanks for the feedback, @Johannnes89.
We designed the notification to be concise and positive, focusing on celebrating a milestone rather than implying a tool was removed. That said, I can see how the current message may be too brief and potentially confusing. I’ll connect with the Growth team’s designer and Product Ambassadors to discuss if we think more clarification is needed. Please share any specific suggestions you might have!

For context, here's the (imperfectly) translated feedback:

...he also doesn't understand why he can't make simple edits anymore. I took a look at the interface and can see why. There, I can no longer select "simple edits," and the only reason I get is "5 edits, congratulations! The available edit suggestions have changed." This text should be changed.

Regarding text: He sees that he can no longer make simple edits, but doesn't know exactly why. "5 edits, congratulations! The available edit suggestions have changed." doesn't explain it (well, in my humble opinion). Something like "Due to your progress (5 edits), simple edits are no longer available" would explain it better.

I created a potential follow-up task here: T407149: Add a Link: improve clarity for newcomers when task is no longer available

Thanks for filing the task!