WordPress development
Themes, Gutenberg blocks and ACF layouts editors can actually use.
Custom themes and block editing built so the content team can lay out a page without asking for a deploy. Thirty one live WordPress sites in the portfolio, from single-language brochures to multisite networks.
Project pricing
From $4,500
That covers a block library and a template rebuild on an existing site. A full build with custom post types, several languages and a content migration runs to $19,000.
Send the brief and get a number back.
Describe the projectEvery page change turns into a ticket
The site launched well and then slowly stopped being yours. Landing pages are hardcoded templates, so a campaign page needs a developer and a deploy. The workaround was a page builder, which the content team can drive but nobody can maintain, and which now holds your content in its own markup. Plugins accumulated, several doing overlapping jobs, one or two abandoned by their authors. Updates stopped, because the last one broke a layout, so the site sits versions behind while the person who built it has moved on. None of this is a crisis. It is just a site that costs money every time it needs to say something new.
What gets built
Blocks your editors can actually use
Custom blocks with the layout locked and only the choices that matter exposed: a variant, an image, a link. Not a panel of forty settings where anyone can break the grid. Each block ships with variations and a real preview, so the person assembling a page sees what will publish before it publishes.
Content as records, not as typed pages
Cases, products, locations, people and offers become post types with fields, through Secure Custom Fields or native block bindings. One record then feeds a page, a listing, a filter and a feed. Typing the same fact into three places is how a site goes stale, and that is a structure problem rather than a discipline problem.
Handed to the editors, not to the designer
The acceptance test is a content person building a new page unaided while we watch and say nothing. Whatever they stall on gets fixed before launch. A site that passes a design review and fails that test comes back as a developer ticket within the month.
Why it is built this way
Native blocks over a page builder
A page builder is fast and then it is permanent. Content ends up in its own markup or in plugin tables, so leaving later means rebuilding every page by hand, and the render cost rides along on every request in the meantime. Core and custom blocks store content in the post itself. Replace the theme, or replace us, and the content is still content.
Every plugin is a dependency you inherit
A plugin is somebody else's release schedule, business model and security posture, installed in one click and rarely reviewed again. On 12 October 2024 the Advanced Custom Fields listing on WordPress.org was taken over and republished as Secure Custom Fields under a new maintainer, and sites on the free version updating from the directory received it automatically. Fewer dependencies, each chosen deliberately and written down with the reason, is the whole strategy.
How it runs
A read of the current site: theme type, page builder, the plugin list with what each one actually renders, where content is stored and what your team edits in a normal week.
A structure map agreed before design starts: post types, fields, blocks and templates, with what an editor can change inside each.
The build happens on a staging copy loaded with your real content rather than placeholder text, so the layout meets long titles and missing images before your customers do.
Migration, then a working session with the people who will run the site: they build pages, we fix whatever slows them down.
Launch with redirects checked and old URLs answering, then a fix window while the team works in it for the first time.
Background
What WordPress work looks like now
Block themes won the roadmap, classic themes still run the sites
An analysis of 14,800 themes in the WordPress.org directory in June 2026 put block themes at 8.3 per cent of the non-default install base against 91.7 per cent classic, roughly eleven to one. At the same time about half of new theme submissions in 2026 are block themes, against almost none in 2019, and five non-default block themes have passed a hundred thousand active installs. Both things are true at once: the platform's direction is blocks, and the web that exists is still classic, with no announced end to classic support. That is why serious builds ship hybrid, taking block editing where it earns its place and keeping PHP templates where control matters.
The week ACF changed hands
On 12 October 2024 the Advanced Custom Fields entry in the WordPress.org plugin directory was taken over and republished as Secure Custom Fields under a new maintainer. Sites running the free version and updating from the directory received it automatically. Sites on ACF PRO, which updates from the vendor, did not. Most sites carried on working, which is why the episode reads as trivia unless you are the one responsible for the site. What it demonstrated is that the update channel of a plugin holding your entire content model can change hands overnight. The answer is not to avoid plugins. It is to know which ones your content depends on, where each updates from, and what leaving would cost.
One network or several installs
A multisite network fits when the sites are one brand across markets: shared templates, one block library, a single place to ship a change, and separate country domains with their own language and pricing. It stops fitting when the sites have different owners, need different plugins or want their own release schedule, because then every update becomes a negotiation between stakeholders. Both shapes are in the portfolio, including a network running twelve live domains across six European markets from one codebase.
What the handover should contain
A theme somebody else can read, a written map of post types, fields and blocks, and a plugin list with the reason each one is installed. Plus the staging copy and the deployment path, so the next change does not begin with an archaeology bill. Thirty one WordPress projects in the portfolio run forty eight live domains between them, from single-language brochure sites to multisite networks, and every one of those domains is fetched and checked before anything is published here.
Describe the project
Tell us what you have and what should change. Within two working days you get a written calculation: the scope broken into parts with a price against each, or the questions needed to write one. No discovery call in between.
Questions
WordPress work, asked and answered
Usually a hybrid, and the numbers explain why. Block themes hold a small share of the installed base while classic themes run most live sites, and there is no announced end to classic support. So block editing goes where it genuinely helps the editors, and PHP templates stay where control matters. Committing to either extreme for its own sake costs you either flexibility or budget.
Not necessarily. If the team is productive in it and the site performs, the honest answer is to leave it alone and spend the budget elsewhere. The case for leaving is when page load is suffering, when the licence is a growing line item, or when you want the content to survive the next redesign, and that case gets made with your numbers rather than as a matter of principle.
It depends on which one you are actually running. The free plugin from the WordPress.org directory is now Secure Custom Fields under different maintenance. ACF PRO updates from the vendor and was not touched. Both work. What matters is knowing which is installed, where it updates from, and whether your field definitions are in code or only in the database, because that is what decides how hard it would be to move.
That is the deliverable, not a side effect. Pages are assembled from blocks with locked layouts, content lives in fields, and the handover includes a session where the team builds pages while we watch. If a routine page still needs a developer afterwards, the structure was drawn wrong and gets redrawn.
A block library and a template rebuild on an existing site is usually weeks. A full build with custom post types, several languages and a content migration takes longer, and the number comes after the review of what you have rather than before it.