Update Navigation
Add new documentation pages to the docs.json navigation structure.
Instructions
- •
Identify the page: Determine which page needs to be added to navigation
- •If not specified, ask the user which file/page to add
- •Confirm the file path is correct (relative to docs root)
- •
Determine navigation group: Figure out where in the navigation this belongs
- •Ask which navigation group it should go in if not specified
- •Common groups: "Get Started", "Developer Resources", "Products", "API Reference", "Recipes"
- •Read docs.json to see current navigation structure and group names
- •
Read current docs.json:
- •Understand the existing navigation structure
- •Find the correct group to add to
- •Note the format and patterns used
- •
Update docs.json:
- •Add the new page entry to the appropriate navigation group
- •Maintain consistent formatting
- •Preserve alphabetical or logical ordering within the group if applicable
- •Ensure proper JSON syntax
- •
Show changes:
- •Show the user what was added to docs.json
- •Confirm the placement is correct
Navigation structure notes
- •Pages are organized by user journey, not by file structure
- •The main tabs are: Guides, API Reference, Recipes, Data
- •Navigation group names should match existing patterns
- •Each entry typically includes just the file path
Example
If user says "Add the new webhook-setup.mdx page to the Developer Resources navigation":
- •Verify file exists at the specified path
- •Read docs.json to find the "Developer Resources" group
- •Add "guides/developer-resources/webhook-setup" to the appropriate location in that group
- •Show the diff for confirmation