One MDX Pipeline for Docs and Blog#
The moment blog content lives in the library, duplicating the MDX renderer stops making sense.
Shared rendering keeps authors productive#
Authors can keep using the same callouts, cards, tabs, files, and code blocks across docs and blog posts.
One syntax
Reuse the same MDX components instead of teaching two systems.
One theme
Keep spacing, borders, and prose styles aligned by default.
One syntax#
Reusing the same component map means the library only needs one place to define the MDX contract.
One theme#
The docs theme variables already define surfaces, borders, foreground colors, and density. Blog pages should consume those same tokens instead of inventing a second theme layer.
