feat(docs): remove the primitives and recipes pages, keep the exports - #157
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Advanced Run ID: 📒 Files selected for processing (28)
💤 Files with no reviewable changes (17)
Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review. 📝 SummarySummary by CodeRabbit
WalkthroughThe docs site removes primitive and recipe pages, data, demos, catalog entries, and navigation. It updates search, accessibility coverage, documentation links, project guidance, and catalog types for a component-focused structure. ChangesDocumentation surface removal
Estimated code review effort: 3 (Moderate) | ~20 minutes Merge Risk: ⚪ Minimal · up to Documentation navigation and search now omit the removed primitive and recipe content while preserving component documentation and primitive package exports. No merge-blocking current-head risk is evidenced. 🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
Full details: Docstring CoverageExplanation Docstring coverage is 50.00% which is insufficient. The required threshold is 80.00%. Docstring coverage is scoped to functions touched by this diff. Analyzed 2 functions across 8 files. (3 skipped: 3 unsupported.)
✨ Finishing Touches 💡 1📝 Generate docstrings 💡
Warning Some tools did not complete. Review the errors below. 🔧 ESLint
ESLint install failed. For unrecoverable errors, disable the tool in CodeRabbit configuration. Comment |
|
React Doctor found no new issues. 🎉 Reviewed by React Doctor for commit |
|
@CodeRabbit review |
✅ Action performedReview finished.
|
Why
The eleven primitive pages and five recipe pages still wore launch placeholder styling, and their slider playgrounds duplicate what the editor does better. SHA-136 decided the primitives stay exported, because eject-to-code imports them by name, but get no doc pages.
What changes
The routes and their data go
/primitives,/recipes, both data files, and the five docs components that only served them are deleted. The Primitives sidebar group, thecatalognav item kind, and the primitives entries in the search index go with them, since nothing else used them. The Engine API page keeps its Tier 2 list as bare signatures.The header's Examples link points at /examples
It pointed at
/recipesas the nearest thing to examples./examplesis the placeholder page SHA-135 will design, so the link never 404s.AGENTS.md describes a two-tier model
Tier 3 recipes no longer exist anywhere, so the project-shape paragraph drops them and records why the primitives stay exported.