User story & summary:

As a designer, I want to be able to easily mockup Community Configuration copy and design requirements, because then I can clearly visualize our form needs while ensuring the form is supported by Community Configuration.

Background & research:

WMF teams generally start with product & design researching a problem space and detailing requirements. It would be easier for other WMF teams to detail their requirements if there was a Figma file template that documents all of the data types and associated components that the Community Configuration form supports. This should help support other teams as they start to explore using Community Configuration.

The fundamental idea of community configuration is to store certain configuration settings as JSON pages in the MediaWiki namespace, so the full suite of MediaWiki curation, audit and authorization workflows naturally applies to them; but JSON (or in general, machine-readable text) is not a user-friendly interface, so we provide various forms to edit these pages in a highly structured way, and also to inject documentation and minor validation (e.g. existence checks for page names) into the editing process.

Related tasks:

T343072: Community configuration: Write specifications for the Editing form
This task might be best tackled after: T363401: Community configuration: Clearly document the data type for config

Design:

[[ |Figma designs]]

Acceptance Criteria:

Figma file that mocks up the general data types and associated components that are supported by Community Configuration