-
Notifications
You must be signed in to change notification settings - Fork 601
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: add navigation menu component #3111
feat: add navigation menu component #3111
Conversation
Approved but had a second thought. I think we should prefix all the components built specifically for the site with something other than |
sites/fast-website/src/app/components/site-navigation/site-navigation.ts
Outdated
Show resolved
Hide resolved
5c3eb72
to
8dc8c69
Compare
09aa0d4
to
1eaf9c4
Compare
6b62de6
to
cde05a6
Compare
I think this should be a feat - not a chore :) |
I think we should add |
sites/fast-website/src/app/components/navigation/navigation.template.ts
Outdated
Show resolved
Hide resolved
…servable, add withBehavior to styles file
cde05a6
to
b27d226
Compare
* create initial files for navigation component * add slotted for nav items * use the prefix site for the components, addressed rtl, removed adding role attribute * rebased. add start and end template, removed slotted directive and observable, add withBehavior to styles file
* create initial files for navigation component * add slotted for nav items * use the prefix site for the components, addressed rtl, removed adding role attribute * rebased. add start and end template, removed slotted directive and observable, add withBehavior to styles file
* create initial files for navigation component * add slotted for nav items * use the prefix site for the components, addressed rtl, removed adding role attribute * rebased. add start and end template, removed slotted directive and observable, add withBehavior to styles file
* create initial files for navigation component * add slotted for nav items * use the prefix site for the components, addressed rtl, removed adding role attribute * rebased. add start and end template, removed slotted directive and observable, add withBehavior to styles file
* create initial files for navigation component * add slotted for nav items * use the prefix site for the components, addressed rtl, removed adding role attribute * rebased. add start and end template, removed slotted directive and observable, add withBehavior to styles file
* create initial files for navigation component * add slotted for nav items * use the prefix site for the components, addressed rtl, removed adding role attribute * rebased. add start and end template, removed slotted directive and observable, add withBehavior to styles file
* create initial files for navigation component * add slotted for nav items * use the prefix site for the components, addressed rtl, removed adding role attribute * rebased. add start and end template, removed slotted directive and observable, add withBehavior to styles file
* create initial files for navigation component * add slotted for nav items * use the prefix site for the components, addressed rtl, removed adding role attribute * rebased. add start and end template, removed slotted directive and observable, add withBehavior to styles file
Description
Created a navigation component to use for the navigation page menu. The template is a nav element with a slotted directive. Each navigation item also gets an attribute of
role="listitem"
added. Implemented the control on the page in the header and footer.Motivation & context
Issue type checklist
Is this a breaking change?
Process & policy checklist