docs(fumadocs): document on-demand SSR blog architecture#121
Draft
tembo[bot] wants to merge 1 commit into
Draft
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Contributor
Author
|
Requesting review from @leoisadev1 who has experience with the following files modified in this PR:
|
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
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.
Summary
PR #119 switched the blog from build-time prerendering to on-demand SSR, but
apps/fumadocs/README.mdstill described the old "fully static, baked at build time" model. This updates the Blog content (Notra) section to match the shipped behavior.Docs updated
apps/fumadocs/README.md→ "Blog content (Notra)" — rewritten to document the new architecture:/blog,/blog/$slug, and/og/blog/*(live fetch, edge-cached ~60s, no rebuild) vs. the build-time snapshot that now backs onlysitemap.xml/rss.xml/feed.json.notra-runtime.ts,fetch-notra-posts.ts,notra-content.ts, and thevercel.jsonBuild Output change.NOTRA_API_KEYis now required at both build time and runtime (the deployed SSR function needs it).Codepaths covered
Verified against source — no behavior described that the code doesn't do:
apps/fumadocs/src/lib/notra-runtime.ts— request-time server functions, dynamic SDK import, edge caching.apps/fumadocs/src/routes/blog/index.tsx,blog/$slug.tsx,og/blog/$.ts— load from the runtime fetch withCache-Controlheaders.apps/fumadocs/vite.config.ts—prerender.filterexcludes blog routes.apps/fumadocs/scripts/fetch-notra-posts.ts+src/lib/blog.ts— snapshot now feeds sitemap/RSS/JSON only.vercel.json— deploys the full.vercel/outputso the Nitro SSR function ships.Key knowledge gaps addressed
NOTRA_API_KEYmust be present at runtime in production, not just at build.Documentation-only change; no source files modified.