How it works
How SEK works
SEK borrows a discipline from frontend development: split your work by section, not by technology. A section is one articulable unit - its fields, its config, and its template - kept together instead of scattered across a template file, a JSON export, the database, and the editor UI.
One decision
Four properties follow from that one decision, and each protects a section's meaning across a handover.
- 01
Co-located config
A section is a YAML file plus a template, living side by side in your theme. The config declares the fields; the template renders them. Everything about what a section is and how it looks sits in one place you can open and reason about, instead of tracing it across four systems.
- 02
Source of truth in version control
Because the config is a file, it lives in git: reviewable in a pull request, diffable across changes, portable to another site by copying the files. The database holds the content an editor entered; the config holds the definition, and the definition is the source of truth, not a copy that drifts.
- 03
Schema-evolution safety
Configs change. When you rename a field, remove one, or add another, reconciliation re-shapes the saved data to match the new config the next time the editor opens the page: missing fields get defaults, removed fields move to Inactive Fields (lost values, recoverable), renamed sections run their migration rules. A config change never breaks a saved page.
- 04
Data and frontend separation
The data an editor enters and the template that renders it are separate concerns. Change the template and the content is untouched; change the content and the template is untouched. That separation lets a dev restyle a section without disturbing an editor's work, and an editor edit without risking the build.
The payoff
Value preserved upward
Put the four together and a section carries its own meaning forward. The value your discovery and design work created - why this section exists, what it is for, how it behaves - survives the handover to the next dev, the editor, and the maintainer, instead of eroding across the chain. Meaning is the carrier of value, and structure is what keeps the meaning intact.
The fastest way to see all four working in a real theme.
The starter kit is a real theme wired for SEK, so you can watch co-located config, version control, safe schema changes, and data-and-template separation in one place.