Editable content models built to fit the project — a generic, schema-driven content layer instead of a bolted-on CMS.
When a site needs editable content, I build a content model that fits the project rather than bending the project around a general-purpose CMS. A generic, schema-driven content layer lets a new content type be declared once — its fields, its URL, its relationships — and get listing, reading, and admin editing without a new set of templates each time.
This site runs on exactly that layer: case studies and capabilities are content types, not hardcoded pages.
Discuss your project