Rebuild guide as markdown-driven, tabbed, API-served (retire DB/CRUD) #1

Open
opened 2026-06-30 23:38:30 -04:00 by hiveiq · 0 comments
Owner

Per DESIGN.md (committed to develop). Greenfield rebuild:

  1. Backend (this phase) — read markdown from content/**/*.md (frontmatter: module/title/tab/order/audience), serve GET /api/v1/guide/nav + GET /api/v1/guide/modules/{module}; retire the DB content_json model + admin CRUD; audience gates customer vs internal (role-based).
  2. Frontend tabbed slide-out reader.
  3. Author content (devices.sw-deploy + fleet.tasks pattern), then all modules.
  4. Technical guides (internal).

Decisions: markdown files in git served via API; start over (no compat shim); retire Guide Admin CRUD, keep internal docs.

Per DESIGN.md (committed to develop). Greenfield rebuild: 1. **Backend** (this phase) — read markdown from `content/**/*.md` (frontmatter: module/title/tab/order/audience), serve `GET /api/v1/guide/nav` + `GET /api/v1/guide/modules/{module}`; retire the DB content_json model + admin CRUD; `audience` gates customer vs internal (role-based). 2. Frontend tabbed slide-out reader. 3. Author content (devices.sw-deploy + fleet.tasks pattern), then all modules. 4. Technical guides (internal). Decisions: markdown files in git served via API; start over (no compat shim); retire Guide Admin CRUD, keep internal docs.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: hiveiq-src/hiveops-guide#1