Documentation
¶
Overview ¶
Package cms declares the Hanzo CMS content model as DocType fixtures on the framework engine (clients/framework). CMS is NOT a bespoke subsystem and mounts NO HTTP surface of its own: a "collection" IS a framework DocType in module "cms", a content entry IS a framework document, media IS an Attach-backed document, and publishing IS a status field. All CRUD, permissions, tenant isolation, and install are the framework's generic, already-live surface (/v1/framework/*). This package only DECLARES the fixtures and registers them with the engine at init — the ONE source of truth for the CMS content model, per-org on Base/SQLite.
This is the first app lane on the framework and the template for the rest: ERPNext DocTypes and Helpdesk register their fixtures the same way (framework.RegisterModule) and are installed + rendered by the SAME generic install path and the SAME generic @hanzo/ui DocType renderer. One engine, one renderer, every business app.
Index ¶
Constants ¶
const Module = "cms"
Module is the framework module tag every CMS DocType carries. The console's CMS surface is the generic DocType renderer scoped to this module.
const RoleContentEditor = "Content Editor"
RoleContentEditor is the editorial role the CMS content DocTypes grant read/ write/create/delete. The org owner (System Manager, seeded trust-on-first-use) assigns it to teammates via /v1/framework/roles; a role-less member stays denied (secure by default). Publishing is a status write, so it needs no extra right.
Variables ¶
This section is empty.
Functions ¶
Types ¶
This section is empty.
Source Files