Reorganize docs folder into guides, architecture, features, and research#1750
Reorganize docs folder into guides, architecture, features, and research#1750johan-bell wants to merge 2 commits into
Conversation
Review summary — 🟡 Approve with nitsClean, well-executed docs reorg; two pre-existing broken links carried forward rather than fixed.
🤖 AI-assisted review summary (Claude Code). Read-only analysis of the PR diff — not a substitute for human review. |
Move flat docs/ files into a clearer hierarchy, add docs/README.md index, archive historical-upgrades stub, consolidate project-automation guide, and update cross-repo references to the new paths. Co-authored-by: Cursor <cursoragent@cursor.com>
55cc4ca to
3db899d
Compare
ivanslabbert
left a comment
There was a problem hiding this comment.
added a few comments. But I think we should generally move away from a separate docs folder (except perhaps for a few diagrams like the data model, permission system etc. diagrams).
Documentation describing the actual implementation should live in the app / cms / api / shared library codebases, referenced from the main README of the individual folder.
The projects root level's README serves as the springboard into all the sub-project's documentation, and everything should be reachable by drilling down into sub-project readme files, and drilling down into individual functions
…cross-cutting content Per Ivan's review: docs/ now holds only ADRs, cross-cutting guides, and architecture diagrams. Vue-plugin-architecture moves to app/docs/, rest-api/socket-io-messages/s3-multi-bucket move to api/docs/, api-testing folds into api/README.md, the stale post-checkout git-hook doc is removed (hook script was already deleted from the repo), and docs/research/fts/ (superseded by ADR 0009) is deleted.
Move flat docs/ files into a clearer hierarchy, add docs/README.md index, archive historical-upgrades stub, consolidate project-automation guide, and update cross-repo references to the new paths.