docs(site): restore the lost blog posts and the Mermaid page - #3549
Merged
Conversation
Three finished blog posts and the Mermaid addon page were written but never committed, so they were lost when the site branch was squashed: the textkit walkthrough, the pdfkit fork retrospective, the web worker post, and the `@react-pdf/mermaid` reference. The textkit post is the reason `components/text-lab` comes back with it: the prose leans on four interactive labs, and without them the page does not render. They need fontkit and textkit, which the site already resolved transitively and now declares. The Mermaid page called a `<Usage name>` component that no longer exists, and the snippet files it pointed at never did; its three examples are plain code blocks now, like the Math page next to it.
|
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Four finished pages were written during the site rebuild but never committed, so they went with the squash. They only survived in Conductor's working-tree checkpoints; this restores them as they were.
Blog
How react-pdf renders text— the six-pass textkit walkthrough, with the four interactive labsDropping the pdfkit fork— the retrospective on@react-pdf/pdfkitand the upstream PRs that ended itLarge documents in the browser— why a big render freezes the tab, and the web worker setup that fixes itDocs
v4/addons/mermaid— the@react-pdf/mermaidreference, back in the Addons nav next to MathWhat had to change to make them build
components/text-labcomes back with the text post: the prose is written around<RunsStrip>,<GlyphLab>,<LineBreakLab>and<LineBoxLab>, and MDX throws on an undefined component, so the page does not render without them. They are wired into the blog page's component map. They importfontkitand@react-pdf/textkit, which the site was already resolving transitively — now declared, at the versions already inyarn.lock, so the lockfile is untouched.The Mermaid page called
<Usage name="addons/mermaid" />, an API that no longer exists pointing at snippet files that never did. Its three examples are plain code blocks now, matching the Math page beside it.Verified with a production
next buildfrom a clean--frozen-lockfileinstall: all five routes prerender and serve 200, including the three new blog entries and the Mermaid page.Not restored, for the record: the
_dummy-*.mdxscaffolding, andv4/advanced/large-documents.mdx, a stub that only linked out to a dev.to post — the blog entry above replaces it.🤖 Generated with Claude Code