Page MenuHomePhabricator

Growth features: Migrate Help panel settings from Special:EditGrowthConfig to Community configuration 2.0
Open, HighPublic3 Estimated Story Points

Description

As part of migrating Special:EditGrowthConfig to the Community configuration 2.0 system, we need to migrate the "Help panel settings" and "Help panel links" sections from https://en.wikipedia.org/wiki/Special:EditGrowthConfig to Special:CommunityConfiguration. This task captures that work.

Design for Help panel links

Screenshot 2024-04-18 at 17.35.16.png (1×1 px, 311 KB)
help panel links example.png (824×950 px, 39 KB)
Existing implementationProposed design for the links section
Acceptance Criteria
  • "Help panel settings" configuration options are moved to Special:CommunityConfiguration/HelpPanel
  • "Help panel links" configuration options are moved to Special:CommunityConfiguration/HelpPanel

Event Timeline

This is currently blocked on implementing the agreed-on changes to T357718: Support schema references. Moving to Blocked to reflect that.

KStoller-WMF set the point value for this task to 3.Tue, Apr 2, 4:30 PM

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

[mediawiki/extensions/GrowthExperiments@master] Config: add HelpPanel schema

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

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

[mediawiki/extensions/CommunityConfiguration@master] Editor: add control for array type

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

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

[mediawiki/extensions/CommunityConfiguration@master] Object control: use fieldset to display a main label

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

Change #1021411 had a related patch set uploaded (by Urbanecm; author: Urbanecm):

[mediawiki/extensions/CommunityConfiguration@master] Introduce AbstractProvider::storeConfiguration

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

Change #1020873 merged by jenkins-bot:

[mediawiki/extensions/CommunityConfiguration@master] Object control: use fieldset to display a main label

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

Change #1021411 merged by jenkins-bot:

[mediawiki/extensions/CommunityConfiguration@master] Introduce AbstractProvider::storeConfiguration

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

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

[mediawiki/extensions/CommunityConfiguration@master] [refactor] Factor out ui subschema construction

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

Sgs added subscribers: JFernandez-WMF, KStoller-WMF.

@JFernandez-WMF @KStoller-WMF In the existing implementation we have a recommended link for each item in the list, should we keep that information? The new design does not reflect it.

@JFernandez-WMF - Should we add that recommendation as a replacement for the "placeholder" Label text?
We should replace the link "placeholder" text as well. Should we provide an example for how the link should be formatted?

@JFernandez-WMF @KStoller-WMF In the existing implementation we have a recommended link for each item in the list, should we keep that information? The new design does not reflect it.

Yes sorry I missed that on the designs. Can we have the recommended labels and destinations in the Placeholder text instead of having 'recommended: X" in the label?

Should we provide an example for how the link should be formatted?

@Sgs is the 'Destination page' field using Lookup? If it does then I don't think it is necessary to provide examples since admins can search through suggested results, but feel free to disagree.

@JFernandez-WMF @KStoller-WMF In the existing implementation we have a recommended link for each item in the list, should we keep that information? The new design does not reflect it.

Yes sorry I missed that on the designs. Can we have the recommended labels and destinations in the Placeholder text instead of having 'recommended: X" in the label?

That sounds ok from a design pov but sadly we don't have support for custom placeholders yet, filed as T363051: Add support for field placeholders.

Should we provide an example for how the link should be formatted?

@Sgs is the 'Destination page' field using Lookup? If it does then I don't think it is necessary to provide examples since admins can search through suggested results, but feel free to disagree.

Yes it is, agreed.

This is now blocked on the support for enumerations which will be tackled in T362685

Sgs triaged this task as High priority.Sat, Apr 20, 12:40 PM

Change #1021465 merged by jenkins-bot:

[mediawiki/extensions/CommunityConfiguration@master] [refactor] Factor out ui subschema construction

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

Change #1017302 merged by jenkins-bot:

[mediawiki/extensions/CommunityConfiguration@master] Editor: add control for array type

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

Change #1017256 merged by jenkins-bot:

[mediawiki/extensions/GrowthExperiments@master] Config: add partial HelpPanel schema

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

@Sgs I think this still misses the variables that depend on the enum. Depending on whether we want to do that here or in a follow-up, this should probably be in Doing or QA. In either case, I do not see any patch to review that'd be linked to this task (or that'd be pending patches), so I am moving this to Doing for now. However, feel free to move it further as appropriate (incl. back to CR if I failed to see a pending patch here).

@Sgs I think this still misses the variables that depend on the enum. Depending on whether we want to do that here or in a follow-up, this should probably be in Doing or QA. In either case, I do not see any patch to review that'd be linked to this task (or that'd be pending patches), so I am moving this to Doing for now. However, feel free to move it further as appropriate (incl. back to CR if I failed to see a pending patch here).

Agreed, it was an oversight from my side, thanks for the catch. Working on it :)