In T363788#9808321, @Urbanecm_WMF wrote:

Carrying over Elena's comment:

In T365142#9806897, @Etonkovidova wrote:

(3) Special:CommunityConfiguration and MediaWiki:GrowthExperimentsSuggestedEdits.json can be moved/deleted (in the Tools menu). To have Special pages to options to be moved/deleted is somewhat unusual. For example, Special:Recentchanges, Special:Watchlist, Special:Contribute do not have these options. Should we disable Move/Delete options for Special:CommunityConfiguration(and submodules) also?

@Etonkovidova , to note while testing this, there are 2 new line breaks between the two paragraphs in the informational section of the Suggested edits because MediaWiki ignores single line breaks by treating them as a single space. The design in the figma could not be achieved.
@JFernandez-WMF, is this acceptable?

In T359080#9794246, @Sgs wrote:

In T359080#9794243, @Cyndymediawiksim wrote:

@JFernandez-WMF - the figma design(Labelled as New Design) in the task contains another paragraph starting with Some type of Newcomer Tasks are surfaced..... Is this paragraph also supposed to be part of the Acceptance Criteria? CC: @KStoller-WMF

That text is contextual to the first field not the whole form so we cannot display now as it shows in the designs. Also we don't have support for html parsing (hence the links) in help texts yet. I would omit it for now.

@JFernandez-WMF - the figma design(Labelled as New Design) in the task contains another paragraph starting with Some type of Newcomer Tasks are surfaced..... Is this paragraph also supposed to be part of the Acceptance Criteria? CC: @KStoller-WMF

@KStoller-WMF , yes it needs more work but we do not need a separate task for it.IMO, it shouldn't be a big fix. I"ll create patches for it.

@Urbanecm_WMF, thank you for solving this quickly during our sync session. Assigning this to you to be moved to Q/A :).

In T362203#9739672, @Tacsipacsi wrote:

In T362203#9739550, @Cyndymediawiksim wrote:

However, this approach could lead to a situation where there is no obvious way for users to navigate back to the Special:CommunityConfiguration page from the history page as @Urbanecm_WMF highlighted above.

This is what the link among the content actions aims to solve.

In T362203#9705899, @Urbanecm_WMF wrote:

Would it be okay if the "View History" link lead directly to eg. https://es.wikipedia.beta.wmflabs.org/w/index.php?title=MediaWiki:GrowthExperimentsMentorship.json&action=history (where there would be no obvious way to get back)? Or do we want to do something to make this more clear?

In T362203#9707924, @Tacsipacsi wrote:

Couldn’t the action=history page be made linking back to Special:CommunityConfiguration? Similarly to VisualEditor’s Edit link, Community Configuration provides an alternate edit view of the same page, so putting its link among the content actions would make sense. (And even vice versa: simply call Skin::setRelevantTitle() on Special:CommunityConfiguration, which gives a history link, a talk page link etc. for free.)

@Etonkovidova, yes you can add providers to an extension.json file. In the CommunityConfigurationExample, a provider FooBar is declared. Some other providers are also declared in GrowthExperiments' extension.json file. To test, you would need to add the "skipDashboardListing": true flag to each provider you do not want to be seen on the dashboard. Like so :