Journal
How DynapiCMS works under the hood: write-ups, practices, recipes.
Secrets in a write-only store, http_post with a secret:// key, an inbound webhook behind a digest_matches gate, and the order number in your own admin — the admin as a client of outside APIs.
Localized fields as {ru,en} maps, project languages, the request locale, and a language switch in your own admin — the flow returns the map, the client picks the language.
A cover link field on the book type, /api/media flows for the library and by-URL adds, a picker in your own admin, and an honest storage quota — no server code.
Filters, search, and pagination inside a flow’s graphql node, POST validation with per-field errors, and endpoint debugging via dry run and the runs journal — no server code.
Registration with email confirmation, link-based password recovery, and reader roles — on site flows, no server code. Signed links in letters, the SMTP password in project secrets, and a role gate in the flow.
A book catalog as a closed Vue admin panel example: password sign-in through a flow, a JSON API on site routes, app statics on /static/.