You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Carbon Platform's nav data is different. Instead of YAML it is authored as a JavaScript object. The screenshot of Carbon Platform above is set by this data:
As such, this won't be a copy/paste job. (E.g. the heading comes from the title key in Carbon Platform, and I'm recommending we use the heading key in the YAML data model.)
Also, I'll create a separate issue for upgrading the current side nav to the new NavTree. Since in Carbon Platform this is coming from the same component, I recommend doing this and that other issue in the same pull request.
Specific timeline issues / requests
N/A
Available extra resources
@glapadre may consider contributing this enhancement.
The text was updated successfully, but these errors were encountered:
Summary
The current side nav is limited by being a single list with one level of children:
The Carbon core team added headings to the side nav in Carbon Platform (see "Catalogs" example):
Let's bring that to the Gatsby theme so other sites can also benefit from the improved information architecture.
Justification
This allows website maintainers to group and categorize nav items. It can be used to simplify and improve information architecture.
Desired UX and success metrics
The visuals, behavior, etc. should match the side nav heading in Carbon Platform: https://next.carbondesignsystem.com
You can see the side nav heading used in this Carbon Platform design spec, but I'd view the coded side nav the source of truth unless a bug is identified: https://www.figma.com/file/M1UolPMDngdACDMMLU7WpX/v1_landing_pg_redlines?type=design&node-id=0-1&mode=design&t=CT82XGPPKAwhWeb2-0
Must-have functionality
This is the current nav data:
Any number of headings should be supported. Only top level. I'm thinking something like this would work by adding support for:
- heading: My heading
.Development considerations
This was built as part of the
NavTree
component in Carbon Platform. Source here: https://github.com/carbon-design-system/carbon-platform/tree/main/services/web-app/components/nav-treeCarbon Platform's nav data is different. Instead of YAML it is authored as a JavaScript object. The screenshot of Carbon Platform above is set by this data:
As such, this won't be a copy/paste job. (E.g. the heading comes from the
title
key in Carbon Platform, and I'm recommending we use theheading
key in the YAML data model.)Also, I'll create a separate issue for upgrading the current side nav to the new
NavTree
. Since in Carbon Platform this is coming from the same component, I recommend doing this and that other issue in the same pull request.Specific timeline issues / requests
N/A
Available extra resources
@glapadre may consider contributing this enhancement.
The text was updated successfully, but these errors were encountered: