-
Notifications
You must be signed in to change notification settings - Fork 1.5k
[Sistent] Make Sistent navigation and pagination dynamic from MDX content #7585
Copy link
Copy link
Open
Labels
kind/enhancementNew feature or requestNew feature or requestlanguage/javascriptIssues or pull requests that use Javascript or ReactIssues or pull requests that use Javascript or Reactlanguage/markdownIssues or pull requests that use MarkdownIssues or pull requests that use Markdownproject/sistent
Description
Current Behavior
Currently the pagination is hardcoded - we have to manually add all routes in
src/components/SistentNavigation/content.js every time a new component is added. This requires:
- Manually maintaining 160+ entries with correct IDs and ordering
- Updating both navigation sidebar and pagination components separately
- Risk of inconsistencies between navigation and pagination order
Desired Behavior
The pagination and navigation should be fully dynamic:
- Automatically fetch all Sistent components from MDX files via GraphQL
- Display components in alphabetical order
- Include all sub-pages (overview → guidance → code) in correct sequence
- No manual updates required when adding new components
Contributor Resources and Handbook
The layer5.io website uses Gatsby, React, and GitHub Pages. Site content is found under the master branch.
- 🎨 See Sistent Repository.
- 📚 See contributing instructions.
- 🎨 Wireframes and designs for Layer5 site in Figma (open invite)
- 🙋🏾🙋🏼 Questions: Discussion Forum and Community Slack.
Join the Layer5 Community by submitting your community member form.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
kind/enhancementNew feature or requestNew feature or requestlanguage/javascriptIssues or pull requests that use Javascript or ReactIssues or pull requests that use Javascript or Reactlanguage/markdownIssues or pull requests that use MarkdownIssues or pull requests that use Markdownproject/sistent