feat(Settings): Add more information about setting inheritance
What does this MR do?
Adds more guidance about communicating settings inheritance.
I did an audit in #1272 and we are inconsistent in the way that settings inheritance is communicated. It's not totally possible to have a rigid visual and copy definition of what settings inheritance looks like, as settings themselves are quite different. This MR proposes more abstract guidance - to make sure it's always stated that a setting's inheritance is communicated at both the parent and child level.
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.