feat(docs): add nav registry - #53
Open
mikhd wants to merge 2 commits into
Open
Conversation
Author
|
Warning This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
This stack of pull requests is managed by Graphite. Learn more about stacking. |
This was referenced Jul 15, 2026
mikhd
marked this pull request as ready for review
July 15, 2026 11:29
mikhd
force-pushed
the
feat/2-nav-registry
branch
from
July 23, 2026 10:33
edcda6d to
690cb8c
Compare
mikhd
changed the title
mikhd
force-pushed
the
feat/1-doc-model-types
branch
from
July 24, 2026 10:17
031428e to
f85956e
Compare
mikhd
force-pushed
the
feat/2-nav-registry
branch
from
July 24, 2026 10:17
690cb8c to
ec0d87c
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
[2] Builds the navigation layer on top of the doc-model types from #52 52. Turns a Spec into a path registry every page links through.
Adds:
buildNavRegistry(spec, pathConfig)- the address book. Assigns eachDocRefitspathSegmentsup front, so any page can resolve a link to any other regardless of render order.categoryGroups- single source of "which entities a category holds," reused by registry, navigation, and (later) the category index so listings and links stay in agreement.CategoryGroup / CategoryGroupItemtypes.