docs([DST-1163]) : Raw markdown view for documentation pages#5095
docs([DST-1163]) : Raw markdown view for documentation pages#5095sinan-rsvx wants to merge 19 commits intomainfrom
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
2 Skipped Deployments
|
|
![github-advanced-security[bot]](https://avatars.githubusercontent.com/in/57789?s=60&v=4){kind=small}
sinan-rsvx
changed the title
Coverage Report for Marigold Code Coverage
File CoverageNo changed files found. |
|
Accessibility tests executed. Download the report here. |
|
Accessibility tests executed. Download the report here. |
|
Accessibility tests executed. Download the report here. |
|
When using fumadocs we will no longer generate the JSON 🙈 maybe we can use the stuff from fuma to get the types? |
sinan-rsvx
force-pushed
the
DST-1163-raw-markdown-view-for-documentation-pages
branch
from
714c642 to
27e4377
Compare
|
Accessibility tests executed. Download the report here. |
|
Accessibility tests executed. Download the report here. |
|
Accessibility tests executed. Download the report here. |
|
Accessibility tests executed. Download the report here. |
2 participants
Description
This PR introduces a parser that converts all MDX documentation files in our design system to plain Markdown (.md) files. The main goal is to prepare our documentation for the upcoming MCP server, which will use these Markdown files as its primary data source.
Adds a build step that scans all MDX files in the documentation, parses them, and outputs equivalent Markdown files.
Translates all MDX/JSX syntax to Markdown and inlines the content of all imported or custom components, so the resulting Markdown is fully self-contained.
Only code from
<ComponentDemo>is inlined and preserved as code blocks; all other JSX and imports are resolved or removed.Test Instructions:
Run the following command to build the Markdown documentation and check docs/app/mcp/output/ for generated md files.
Reviewers:
@marigold-ui/developer
Pull Request Checklist: