docs(Feature Management): Introducing discovery patterns and examples

Context

We're planning to update the product handbook with better guidance for teams looking to enhance the discoverability of their features; encouraging everyone to consider options beyond just throwing more links into the navigation. The specific guidance and examples should live in Pajamas, so that's what this MR is doing.

What does this MR do?

This MR updates the discovery moments section of Feature management to include a section for specific patterns that were shared and discussed in the UX weekly on Aug 1. The original page focused exclusively on contextual notices but this didn't encompass all of the relevant examples.

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