feat: add documentation about acceptance of terms
What does this MR do?
This MR adds the legal guidance for the exact UI text we use in settings to enable or disable Experiment and Beta features. The reason to add this to Pajamas so that MR reviewers will have a reference to point to if the UI copy deviates from the recommendations of legal. The goal is that the terms acceptance always follow this exact UI copy.
Does this MR meet the acceptance criteria?
-
The MR title and commit messages meet the Pajamas commit conventions. -
The “What does this MR do?” section in the MR description is filled out, explaining the reasons for and scope of the proposed changes, per “Say why not just what”. - For example, if the MR is focused on usage guidelines, addressing accessibility challenges could be added in a separate MR.
-
Relevant label(s) are applied to the MR. -
The MR is added to a milestone. -
If creating a new component page from scratch, it follows the page template structure. -
Content follows the Pajamas voice and tone guidelines, falling back on the GitLab Documentation Style Guide when needed. -
Related pages are cross-linked, where helpful. Component pages have related components and patterns defined in their Markdown front matter. -
If embedding a Figma file, it follows the Figma embed guide. -
Review requested from any GitLab designer or directly from a maintainer or trainee maintainer.
Links
Edited by Katie Macoy