Use Starlight built-in components across docs#1763
Open
kmcginnes wants to merge 1 commit into
Open
Conversation
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.
Summary
Replace plain markdown link lists and numbered steps with Starlight's built-in components for a more polished, interactive docs experience.
Changes
Components added:
LinkCard+CardGrid— section index pages and "Next Steps" navigationCard+CardGrid— feature highlights on the Features pageSteps— numbered procedures in getting-started, deploy guides, security, troubleshootingTabs+TabItem— Neptune DB vs Analytics policies, JSON vs env var configFileTree— certificate directory listing in security referenceNavigation cleanup:
Workflow:
workflow_dispatchinput to deploy-docs workflow for building from any branchTesting
pnpm docs:buildpasses with all 26 pages built successfully