[codex] Publish reference docs nav#103
Draft
NathanFlurry wants to merge 1 commit into
Draft
Conversation
…eference, nodejs-compatibility, security-model, architecture, cost-evaluation, comparison/*); wire Reference sidebar
|
🚅 Environment secure-exec-pr-103 in rivet-frontend has no services deployed. |
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.
What changed
Adds the restored reference documentation pages and wires them into the docs sidebar/navigation.
Why
The reference docs are intentionally not exposed on
mainyet. This PR makes the nav/page publication explicit and reviewable.Validation
origin/mainhas the reference nav commented out and does not contain the new reference MDX pages.pnpm --dir website buildsuccessfully in an isolated worktree with local dependencies.