feat: implement dynamic routing for Sistent components#7408
feat: implement dynamic routing for Sistent components#7408rishiraj38 wants to merge 2 commits intolayer5io:masterfrom
Conversation
github-actions
bot
added
area/projects
Migrate Sistent components to MDX-based dynamic routing. This removes the hardcoded content.js and replaces it with a scalable, GraphQL-driven approach suitable for large component libraries. Signed-off-by: Rishi Raj <rishiraj438gt@gmail.com>
rishiraj38
force-pushed
the
feat/sistent-refactor-mdx
branch
from
860abe1 to
b7bc06b
Compare
|
@Rajesh-Nagarajan-11 Could you please review and give some feedback? |
|
🚀 Preview for commit b7bc06b at: https://69849a8800c6f13b7bbb8e77--layer5.netlify.app |
Migrated all Sistent components to dynamic MDX routing. Standardized component header layouts by moving descriptions to frontmatter. Cleaned up legacy content.js and deprecated code. Signed-off-by: Rishi Raj <rishiraj438gt@gmail.com>
|
@Rajesh-Nagarajan-11 Could you please review this? Is this the correct way? |
|
This needs a bit more focus. I just need a review to see if I’m moving in the right direction or if I’m increasing your workload. 😅 |
|
present it in monday's website meeting please |
|
🚀 Preview for commit e33a175 at: https://6985ed49e6962ec326ad1365--layer5.netlify.app |
OK, but what was your initial thought about this? Does it look good? |
|
Like all components in the sistent, each has three sub-components: overview, guidance and code. I tried adding everything into a single index.mdx file but it became too large. It was too difficult to find and fix anything so I divided them into three separate files. |
|
🚀 Preview for commit e33a175 at: https://698605f323fdac1a22f3038b--layer5.netlify.app |
|
@rishiraj38 Thank you for your contribution! Let's discuss this during the website call tomorrow at 6:30 PM IST | 7 AM CST Add it as an agenda item to the meeting minutes, if you would 🙂 |
4 participants
Description
This PR refactors the Sistent component documentation system to migrate from a hardcoded data source (content.js) to a dynamic, MDX-driven approach using Gatsby's data layer. This change improves scalability and maintainability of the design system documentation.
Signed commits