docs: restructure and expand project documentation#11
Conversation
Restructure the README and add a durable docs/ handbook. Move long-form content out of README into docs/*.md, add CI/release, getting-started, fixtures-and-schemas, configuration, server-and-viewer, package-api, integrations, concepts, generated-files, and architecture updates. Update examples READMEs and AGENTS.md to reference the new docs and clarify generated output and trusted local code. Rationale: keep root README concise and provide task-focused, linkable docs for contributors and consumers.
|
Caution Review failedPull request was closed or merged during review 📝 WalkthroughWalkthroughThis PR comprehensively restructures jsondb's documentation. The root README shrinks from embedded API and behavioral details to a lean data-first workflow with links to modular docs. A new ChangesDocumentation Restructure & Modularization
Estimated code review effort🎯 2 (Simple) | ⏱️ ~12 minutes
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Restructure the README and add a durable docs/ handbook. Move long-form content out of README into docs/*.md, add CI/release, getting-started, fixtures-and-schemas, configuration, server-and-viewer, package-api, integrations, concepts, generated-files, and architecture updates. Update examples READMEs and AGENTS.md to reference the new docs and clarify generated output and trusted local code. Rationale: keep root README concise and provide task-focused, linkable docs for contributors and consumers.
Summary by CodeRabbit