Skip to content

GRO-686 Docs nav rework - #1315

Open
bpander wants to merge 7 commits into
masterfrom
gro-686-docs-nav
Open

GRO-686 Docs nav rework#1315
bpander wants to merge 7 commits into
masterfrom
gro-686-docs-nav

Conversation

@bpander

@bpander bpander commented Sep 1, 2026

Copy link
Copy Markdown
Contributor

GRO-686

Makes the left nav read from _docs/[version]/util/data/nav.yml instead of _data/docs/nav/[version].yml.

This is a mainly a quality of life change. It keeps the nav data close to the source files and it eliminates the need to manually create a new nav file every time we release a new version.

Migrating the nav files from this repo to the metabase repo will be done in metabase/metabase#81703. Once all those auto-generated PRs are merged, I'll run ‎copy-navs-from-mb.sh‎ on this branch and delete it along with the _data/docs/nav folder.

@bpander bpander self-assigned this Sep 1, 2026
@linear

linear Bot commented Sep 1, 2026

Copy link
Copy Markdown

GRO-686

@bpander
bpander marked this pull request as ready for review September 2, 2026 13:20
@bpander
bpander requested a review from a team September 2, 2026 13:20
@bpander
bpander force-pushed the gro-835-hot-reload-local-metabase branch from c17596c to b21f85c Compare September 2, 2026 13:29
Base automatically changed from gro-835-hot-reload-local-metabase to master September 2, 2026 18:39

@gantoreno gantoreno left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Already approved metabase/metabase#81703 (review), found no blocking issues here

One minor thing: fmt:check fails on NewDocsLayout.astro, run a formatting pass and should be good to go

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants