Ideas, carefully
made real.
Strategy, design and engineering in one place.
EditingA structured WordPress theme and editor for composing real components without trapping the content inside a page builder.
Beta · WordPress 6.7+ · PHP 8.2+ · Theme + editor
Strategy, design and engineering in one place.
EditingThe page-builder bargain
Most page builders begin with a blank canvas and end with the entire site stored in a format only that builder understands. Editors can move everything, so developers spend the next few years stopping everything from moving.
Hewn starts with the system you meant to build. Developers define the components. Editors arrange and populate them. WordPress keeps the content, and the theme stays capable of rendering it.
A more deliberate workflow
Enough visual control for editors. Enough structure for the site to remain coherent.
Build reviewed theme components with the fields, variants and design rules each one needs.
Choose from the approved library and arrange a page without opening a template file.
Connect headings, images, links, groups and repeaters to WordPress or ACF.
See the assembled page before the change is written. Production stays intentional.
The component system
Every component arrives with a purpose, a content model and the styling your design system already approved.
Hero3 variants
ReadyEditorialText + media
ReadyFeature gridRepeatable items
ReadyCall to action2 treatments
ReadyPages, media, native fields and ACF values stay where the rest of WordPress can understand them.
New components follow the same review, versioning and deployment path as the rest of the theme.
Authors work with recognisable page pieces instead of field-group archaeology.
The editor stays out of the public request. The theme renders the page from real content.
Built to be handed over
Templates, components and design tokens live in the codebase. Hewn provides the workshop for using them, not a second rendering system that replaces them.
Review the assembled result before production content changes are committed.
Bind native WordPress content or ACF fields without exposing the page’s implementation.
Keep the content workflow in the system the editorial team already knows.
Editors choose from components and variants the design can support. Developers add new capabilities through source control, not mystery PHP generated in a browser.
Currently in beta
Hewn is being proven with real component systems, real editorial teams and the constraints of production WordPress. Beta access starts with a conversation so we can understand the theme and the handover.
Also included in Nought Suite →Hewn beta
Who it is for
WordPress developersGive clients visual composition without surrendering the theme architecture.
Digital agenciesTurn a component system into a repeatable, calmer handover.
Editorial teamsBuild useful pages from approved pieces without breaking the design.
Questions, answered
Have a particular theme or component model? Tell us about it.
No. Hewn composes pages from components registered in the theme. It gives editors a visual way to arrange and populate those components without turning the page into a proprietary canvas.
In WordPress. Hewn can bind components to native post data, media and custom fields, including Advanced Custom Fields. The theme remains responsible for rendering the page.
No. Developers create and review components in code, then Hewn makes that approved library available to editors. That boundary keeps design and implementation deliberate.
Hewn is designed around its reference theme. Support for selected third-party themes is being proven during beta, so compatibility should be discussed before relying on it.
Hewn is currently in beta. Join the beta to talk through the site, the component model and whether the present build is a sensible fit.
Hewn for WordPress
A structured theme and editor for content that should outlast the canvas.
Join the Hewn beta → Beta access is currently handled by Nought Digital