docs: add CLI and Standard library sidebar landing pages#3408
Merged
Conversation
d5f82a6 to
a4eb934
Compare
josh-collinsworth
approved these changes
Jul 14, 2026
josh-collinsworth
left a comment
Contributor
There was a problem hiding this comment.
Looks good, also added some styling to make the sidebar buttons look more like buttons
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
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.
The "CLI" and "Standard library" groups in the runtime reference sidebar were
dropdown accordions with no clickable top-level page, so there was no landing
page introducing either section. The CLI subcommand overview already existed at
/runtime/reference/cli/ but the sidebar never linked to it.
This gives both groups the opt-in
disclosuretreatment used elsewhere in thesidebar: the label becomes a link to the section landing page while a separate
chevron toggles the children. CLI now points at its existing overview. For the
Standard library, whose pages under runtime/reference/std/ are generated and
gitignored, the curated intro (what @std is, getting started with
deno add,and a note on package stability) is baked into the index template in
generate_std_docs.ts so it is produced on every build, with the package list
still auto-filled between the existing markers.