[UI Shell] Component Clarification, Behavior Rules, and Terminology Alignment

[Kritvi-bhatia17]

Description

As part of the ongoing work in the UI Shell (Labs → Core) migration, we need to clarify and standardize how navigational and action components are defined, named, and implemented across the system. This requires competitor research and a review of existing product patterns to determine the following:

Identify the Correct Components Used Across Navigation

• Determine which component is being used for:
  • Sub‑menu (navigational items)
  • Menu / Action items
• Validate the Environment Switcher Trigger Behavior
  • Confirm whether the switcher trigger is intended to be a Menu Button or a Dropdown.
  • Note that in Core, a Menu Button does not update its label based on the selected option—check whether this matches intended behavior and whether there are any accessibility concerns.

Finalse the Component States & Behavioral Rules

• Document all their states (default, hover, active, focused, disabled).
• Determine rules around full‑width behavior, text wrapping, and max character limits.

Standardize Terminology Across Navigation

• Audit the terms currently used and determine the correct, consistent terminology for:
  Sub‑menu, Menu, Sub‑links, Nested menu, etc. (including Storybook references)
• Once a design stance is established, validate it with Accessibility and Dev teams to ensure consistency across design, code, and documentation.

---

After we figure all this out, we’ll pull everything together into final specs and anatomy and share it with the devs for implementation.