A block theme
A theme defined in theme.json with design tokens, templates and patterns, so spacing, colour and typography stay consistent wherever editors build.
Service · Content platforms
We build and rebuild WordPress sites where publishing is the core of the business: block themes your editors can work with, custom blocks for your content, structured post types and a plugin set you can trust. You receive a site that is quick, maintainable and documented.
Block themes built on theme.json
Custom blocks with locked, editor-friendly patterns
Plugin estates audited and reduced
Deliverables
A theme defined in theme.json with design tokens, templates and patterns, so spacing, colour and typography stay consistent wherever editors build.
Blocks registered with block.json and built with the official scripts package, with server rendering where SEO or caching needs it and locked layouts where brand rules apply.
Custom post types, taxonomies and meta fields that reflect what you publish, with REST exposure and editorial screens that guide authors.
Every plugin reviewed for necessity, maintenance and security history, with abandoned ones replaced and overlapping ones consolidated.
Object caching, image handling, query fixes, least-privilege roles, automatic minor updates and a tested backup and restore.
Early decisions
New builds should usually use block themes. Classic themes remain sensible for sites tied to page builders or complex legacy templates we are not replacing.
Third-party builders speed up layouts but lock content into their markup. Native blocks and patterns keep content portable.
Registered meta with block bindings, a field framework such as ACF, or custom blocks. The choice decides how editors enter structured data.
Multisite shares code and users across many sites; it also shares failure modes and complicates plugin choices.
Headless WordPress via REST or WPGraphQL suits a JavaScript front end, at the cost of losing previews and plugins that output markup.
Engagement
We interview editors about how they publish, and audit the theme, plugins, database and hosting together.
Post types, fields and block patterns are specified alongside theme.json tokens, so design and content structure agree.
Editors try new blocks and patterns on staging each sprint, so the authoring experience is tested before launch.
Content is moved or reformatted, redirects mapped, and the site launched with monitoring and editor training.
Fit
Teams that publish daily or weekly and need a familiar, flexible editor.
Campaign pages built from approved patterns without developer time.
Forms, SEO, memberships or events where maintained plugins cover most of the need.
Alternatives
For large organisations with detailed workflows and access rules, Drupal handles structure better.
Open registerIf apps and several front ends share content, a headless CMS like Contentful may suit.
Open registerFor catalogue and checkout work, see our WooCommerce service.
Open registerWith theme.json, the design system lives in configuration the editor understands. Colour palettes, font sizes and spacing scales appear as editor choices, and nothing outside them is offered. That moves design control out of CSS overrides and into a single file both designers and developers can read.
Sites become hard to manage when everything is a page with free-form content. If you publish case studies, people profiles or events, they deserve their own post types and fields so they can be listed, filtered and reused. We define that model before templates, because it shapes navigation, search and the REST API.
Each plugin brings code, database tables and an update schedule you do not control. We keep a register of plugins with their purpose and owner, remove those that duplicate core features, and replace small ones with a few lines of custom code where that is safer.
This register makes later audits and handovers straightforward.
Most WordPress speed problems are a handful of slow queries, unoptimised images and front-end scripts from plugins loaded on every page. Page caching, a persistent object cache and conditional asset loading solve the majority. We measure with real templates before and after, not just the home page.
FAQ
Much less so. We use theme.json to limit colours and sizes to your palette, and lock patterns where layout must stay fixed, while leaving text and images editable.
Yes. We can keep the builder and tidy around it, or migrate key templates to native blocks over time. Moving everything at once is rarely necessary.
Sometimes. It helps when a JavaScript front end or several channels need the same content. It costs previews, many plugins and simple hosting, so we only recommend it with a clear reason.
Few, maintained plugins; automatic minor updates; least-privilege roles; two-factor login for admins; and hosting that isolates sites. Most compromises come from neglected plugins.
Related services
Primary sources
Dated official documentation, standards, and research that support the factual claims on this page.
Blocks, theme.json and editor extensibility.
Endpoints and custom routes for headless and integration use.
How to read this page
Scope, cost and timeline figures are planning guidance until confirmed in a written proposal. Diagrams and screens are illustrations, not client deliverables, and source-code rights and handover follow the signed agreement. See the delivery process and the full disclaimer.
Next decision
Define outcomes, constraints, evidence, rights and handover before delivery begins.
Commercial rights, repositories, environments, documentation, acceptance and handover remain contract-defined.