4: The admin and API
With models and a menu declared, the CMS serves a full admin and a matching REST API.
4.1: URLs
| Path | Shows |
|---|---|
/articles |
the list for a model (the menu uri) |
/article/5 |
one record and its relations |
/create/article |
the create form |
/change/article/5 |
the edit form |
/api/... |
the JSON API for the same resources |
List and record URIs come from each model's table name (or its uriList / uriRecord overrides), and the sidebar uri should match.
4.2: The REST API
Every model is reachable as JSON over GET, POST, PUT, PATCH and DELETE, including nested child operations. Writes are CSRF-protected; the same forms and the API share the validation defined by your schema.
4.3: Look and feel
The CMS ships themes and transitions as resources. An app picks defaults with prop theme and prop trans, and users can switch at runtime. Because the whole admin is generated, restyling is a theme choice, not a template rewrite.
4.4: Auth is optional
The CMS does not force authentication. The production Dashboard layers auth on top (login, roles, per-module permissions); a small internal tool, like the demo, can run open. Add the auth resource and gate routes when you need access control.