[Masthead L1 v2.2.0]: Epic for new L1 Nav v2.2.0

[sirkitree]

The problem

This is an epic for the Web Components development effort for updating the L1 Nav to reflect the new design coming from the Interfaces team. Current Nav 1 component - https://carbon-design-system.github.io/carbon-for-ibm-dotcom/canary/web-components/?path=/story/components-masthead--with-l-1

L1 Navigation Redesign

• The Interfaces team has asked us to implement some new design treatments for the Masthead L1 component.
• This L1 Nav will be used in all of the product pages across AEM pages.

The solution

We propose following the same feature branch model that we took for the L0/Masthead v2.
(see - #9208)

We also have gone through the intended designs and broken them down into the following tasks in Jira. We can discuss if we'd like to track those all separately here in GitHub as well.

Epic in Jira: AEMSITES-150 Navigation - L1 Component Development v2

• ADCMS-2723 Define data model for Nav L1
• ADCMS-2724 Devise a method for managing L1 data
• ADCMS-2726 Nav - L1 Section name
• ADCMS-2727 Nav - L1 Log in link Story
• ADCMS-2728 Nav - L1 Optional CTA
• ADCMS-2733 Nav - L1 Navigation Links
• ADCMS-2734 Nav - L1 Menu UI elements
• ADCMS-2735 Nav - L1 Columns
• ADCMS-2736 Nav - L1 Overflow behavior
• ADCMS-2737 Nav - L1 Breakpoints
• ADCMS-2738 Nav - L1 Tab tip attachment
• ADCMS-2739 Nav - L1 Mobile navigation
• ADCMS-2740 Nav - L1 On-page behaviors

Application/website

IBM.com AEM Sites

Business priority

Low Priority = release date is not dependent on fix or not upcoming

What time frame would this ideally be needed by (if applicable)

Q1 of 2023

Examples

Design & Functional Specs:
https://www.figma.com/file/35JfN0Sg4ltIIjM7jBDKMk/Navigation?node-id=2330%3A134392

Code of Conduct

• I agree to follow this project's Code of Conduct
• I checked the current issues for duplicate issues