Structured editing
Content is typed. Pages are assembled from blocks and fields instead of a single free-form editor, so a headline stays a headline and a table stays a table.
Blocks, fields, validationCDPCMS · Laravel 13
Author in a modern backend. Ship pages that are just files.
CDPCMS separates the two jobs a content system has to do. Editing, review and scheduling run on Laravel 13. What visitors receive is a flat page with one stylesheet and no framework at all.
Four jobs
Everything a site needs, and nothing it does not.
CDPCMS covers the whole path from the first draft to the delivered byte, and hands each step to the tool that is actually good at it.
Draft, review, schedule
Every change is a revision with an author and a timestamp. Drafts are previewed on the real layout, scheduled for a date, and rolled back to any earlier revision.
Revisions and rollbackBuild to flat files
Publishing writes the site out as plain directories and PHP files. No database query, no template engine and no framework sit in the visitor’s request path.
Framework-free deliveryPart of the platform
Sites, domains, TLS, mail and the firewall are managed in ControlDeskPanel. CDPCMS publishes into that, instead of bringing its own hosting ideas.
Runs on CDPCapabilities
What the Laravel 13 backend gives you.
- Block libraryReusable content blocks with typed fields, repeatable groups and per-block validation rules.
- Media pipelineUploads are converted to WebP and AVIF, sized for the layout, and written with width and height so nothing shifts.
- Multi-siteOne installation serves several domains, each with its own navigation, theme tokens and legal pages.
- Roles and 2FAEditor, reviewer and administrator roles; the login follows the CTPF standard with a two-factor field.
- RevisionsEvery save is a version. Compare two revisions, restore one, and see who changed what.
- SchedulingPublish and unpublish at a set time, driven by the queue rather than by a visitor hitting the page.
- RedirectsRenaming a page writes the redirect for you, so an address that once existed keeps working.
- Search indexA static index is built at publish time, so on-site search needs no database at request time.
- APIA read API for other CTPF systems, and a write API so an external process can file content.
The stack
Boring where it counts.
These are the facts of the system, not a promise. The public side carries no framework, which is why it stays fast without a cache in front of it.
Laravel 13Authoring backend, queue and API
PHP 8.5Runtime on the CDP servers
0JavaScript frameworks on the public page
HTTP/3Delivery with TLS 1.3 and HSTS
Principles
Six rules the system is built on.
The visitor pays nothing
No framework, no render step and no database query between the request and the page.
Content is typed
Fields have a kind. What cannot be expressed as a field does not belong in the content.
Every change is a version
Nothing is overwritten without a way back.
Addresses are absolute
A site lives at the root of its own domain. No base-path indirection anywhere.
One stylesheet
The output loads a single stylesheet and, at most, a few kilobytes of script.
Operations included
Publishing, TLS, mail and the firewall are one platform, not four vendors.
The published site is a C-Muster site.
Root holds only C-directories and one index.php. That is what makes the output this small.