EasySiteControl
Content modelling with teeth
Typed schemas whose rules are enforced by the server — not described and hoped for.
What you get
- Seventeen field types, from text and enumerations to relations, components and dynamic zones
- Required, ranges and formats validated server-side with per-field errors
- Unique fields backed by real database indexes — two simultaneous writes can't both slip through
- Relations must reference records that actually exist
- Every create, edit and delete writes a history entry — your undo trail
Rules that hold under pressure
A schema here is a contract the server enforces, not a form hint. Writes from the dashboard, the API and automations all pass the same validation, so 'required' and 'unique' mean exactly that — uniqueness is backed by real database indexes, and a reference to a deleted or mistyped record is rejected with a clear per-field error instead of becoming a dangling pointer.
Model real pages, not just posts
Components define reusable field groups once — a call-to-action, an SEO block — and dynamic zones hold ordered lists of them, validated instance by instance. That's the page-builder pattern with the guarantees of a typed schema.