feat(blueprint): serve features from an MDX content source - #366
Merged
Conversation
The features route resolved pages through a hand-maintained module map, so every new feature page required editing the route, and /features had no sidebar tree of its own — it fell through to the changes tree. Register content/features as a second fumadocs source so pages are discovered from disk, and give the layout shell the features tree. Convert the three platform pages from TSX to MDX in the process; their decision records are still the JSON files on disk, imported by the MDX and rendered through DecisionTimeline, so PlatformFeaturePage is no longer needed. Existing feature URLs are unchanged.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Contributor
Deploying with
|
| Status | Name | Latest Commit | Preview URL | Updated (UTC) |
|---|---|---|---|---|
| ✅ Deployment successful! View logs |
volleybro-blueprint | e356e42 | Commit Preview URL Branch Preview URL |
Aug 06 2026, 11:37 AM |
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.
Summary
Registers
blueprint/content/featuresas a second Fumadocs content source so feature pages are discovered from disk instead of resolved through a hand-maintained module map, and gives/featuresa sidebar tree of its own.Problem
features/[[...slug]]/page.tsxheld afeatureModulesrecord mapping every slug to a dynamicimport(). Adding a feature page meant editing the route./featureshad no page tree.DocsLayoutShellfell through to the changes tree, so the Features tab showed the Changes sidebar.Changes
source.config.ts/src/lib/source.ts: addfeaturesSource(content/features, base URL/features)features/[[...slug]]/page.tsx: dropfeatureModules; resolve viafeaturesSource.getPage()/generateParams(), withInteractiveFlowchart,StatusBadge, andDecisionTimelineregistered as MDX componentslayout.tsx/DocsLayoutShell:/featuresusesfeaturesSource.pageTree; every other section keeps the changes treeindex,team-management,game-recording,analytics,notifications,account,platform,landing) plusmeta.json, and aStatusBadgecomponentDecisionTimeline— soPlatformFeaturePagehas no remaining consumers and is removed.Verification
pnpm verify:allpasses — 100 suites / 784 tests, app build,assert-sw: OK, blueprint buildtype-checkclean, 16 suites / 37 tests pass/features/platform/{blueprint,agent-orchestration,delivery-workflow}keep their existing URLsDecisionTimeline; flowcharts and status badges render/featureslists the top-level pages and expands the platform folder when activeknipreports nothing newNotes
No changeset: this changes the Blueprint site only, not app runtime behaviour.
Recovered from a stash taken on
feat/blueprint-features; the rest of that stash had already landed ondevin a newer form.摘要（zh-TW）
把 Blueprint 的 features 頁面從手維護的 module map 改成 fumadocs MDX content source。原本每新增一頁都要改 route，且
/features沒有自己的 page tree，側欄會 fallback 成 Changes 的樹。這次新增featuresSource、8 個 feature MDX 頁與StatusBadge，並把 platform 三頁從 TSX 轉成 MDX——decision JSON 沿用磁碟上既有檔案，由 MDX 直接 import 後交給DecisionTimeline，因此PlatformFeaturePage一併移除。既有 URL 全部不變，pnpm verify:all通過。因僅影響 Blueprint 站台、不動 app runtime，未附 changeset。