[Feature flags] Narrow down iterations and create final designs

[laurenmrice]

Acceptance criteria

• Now that we have a couple solid different directions of where to take this work, the goal of this issue is to thoroughly explore these directions and play them back to decide on some final design outcomes.

---

1. General guidance

Overview > Components tab

Tags in image cards:

• [x] Mock up how to display the Feature flag tag in the cards.
  • Suggestion: Try putting them at the bottom of the card. Does there need to be a rule divider to separate the image from the content? Does the aspect ratio of the card need to change to account for that? How would multiple tags look in this scenario (like adding an AI tag)? Try using a smaller height tag.

Overview > Feature flag tab

• [x] Mock up what this would look like from what Scott said in Slack.

Help > FAQs page

• [x] Mock up how the content should be rewritten here to make the experimental information more clear while also referencing what feature flags are.

2. Component usage tab guidance

• [x] Omit the following ideas for now: Accordions, Tags in anchor links, UI shell left panel tags.
• [x] See what feature flags we currently have and show how the feature flag sections would play out on these pages within a full page flow. You could do multiple for the different versions you had of how to display these sections/notifications. - Suggestion: Seems like Structured list and Tile would be good ones to start with.

---

Playback 1

• [x] Playback explorations to designers, devs, and a11y on a call.
• [x] Receive feedback and consolidate iterations

Playback 2

• [x] Playback explorations to designers, devs, and a11y on a call.
• [ ] Make final outcomes.