Frontend Horizon admin platform
Knowledge Base
Content, design system, skills + standards
Scaffold deployed · routes not yet migrated · coupling: needs-decision
Routes (7)
- /admin/content
- /admin/design-system
- /admin/skills
- /admin/standards
- /admin/templates
- /admin/playbooks
- /admin/presentations
API routes (11)
- /api/admin/content
- /api/admin/content-engine
- /api/admin/blog
- /api/admin/design-system
- /api/admin/skills
- /api/admin/standards
- /api/admin/playbooks
- /api/admin/presentations
- /api/admin/templates
- /api/admin/layout-flags
- /api/admin/smart-tag
Lib domains (8)
- lib/content
- lib/design
- lib/skills
- lib/standards
- lib/playbooks
- lib/presentations
- lib/richtext
- lib/layout-guard
Routes keep their exact /admin/* paths, so the migration is a directory move and no URL changes. The backend is the shared FH Supabase project — this surface reads the same fh.* schema as every other, and never imports another surface's data layer.