feat(guide): markdown-driven backend API, retire DB/CRUD (Phase 1) #2
Reference in New Issue
Block a user
Delete Branch "feat/1-markdown-guide-backend"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Phase 1 of the guide rebuild (DESIGN.md).
What changed
MarkdownGuideServicescanscontent/**/*.md(frontmatter: module/title/tab/order/audience), no DB.GET /api/v1/guide/nav+GET /api/v1/guide/modules/{module}; internal-audience tabs gated to MSP_ADMIN/BCOS_ADMIN.devices.sw-deploy(Overview / The Data / Technical-internal),fleet.tasks.Verified locally: boots with no DB, loads 4 docs; nav returns the tree; customer sees 2 tabs, MSP_ADMIN sees 3 (Technical internal); no-token → 401.
Refs #1
Phase 1 of the guide rebuild (DESIGN.md): - MarkdownGuideService scans content/**/*.md (frontmatter: module/title/tab/order/audience) - GET /api/v1/guide/nav + /api/v1/guide/modules/{module}; audience gated by role (internal tabs only for MSP_ADMIN/BCOS_ADMIN) - Removed JPA/Flyway/Postgres, Guide entity/repo/service, admin CRUD, seed migrations - Seed content: devices.sw-deploy (Overview/Data/Technical-internal), fleet.tasks - Verified: boots with no DB, loads 4 docs, nav + audience filtering + 401 all correct Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>