02 / custom-coded wordpress
custom-coded wordpress
Custom-coded WordPress means custom post types, custom fields and hand-built templates — content behaving like structured data rather than a pile of pages — using tools such as JetEngine, ACF and WooCommerce.
WordPress done properly is not a template you buy. It is a content framework. The difference between a bad WordPress site and a very good one is entirely in how it is built, and we build them the hard way.
typical timeline: A structured WordPress build typically runs 4 to 10 weeks depending on how many content types and how much migration is involved.
who this is for
pick this if any of these are true.
not this? Anything where users log in and transact with each other. That is a product, and products belong in a custom build.
- Directories, listings, portfolios, property or event catalogues
- Editorial sites where several people publish
- Businesses that must add new content types without a developer
- Ecommerce that needs control over the checkout, via WooCommerce
- Sites migrating off a builder they have outgrown
what you actually get
custom post types
Each kind of content gets its own type with its own fields, so a new entry renders correctly without anyone touching a page.
JetEngine & ACF
Field groups, relations, repeaters, conditional logic and dynamic listings — the structural work most builds skip.
hand-built templates
Coded templates and blocks rather than a bought theme, so the site stays fast and the layout does what the design says.
editor experience
An admin your team can actually use: sensible labels, only the fields that matter, roles that prevent accidents.
speed & core web vitals
Query tuning, image pipelines, caching, script discipline. Measured on a mid-range phone, not a designer's laptop.
care plan
Managed hosting, tested backups, staged plugin updates and someone accountable when something breaks.
how we do it
content audit
We work out what your content really is, and what the repeated shapes are. That becomes the post types.
structure & fields
Types, fields, relations and taxonomies defined before design, so nothing gets hardcoded into a page.
design & build
Templates, listings, filters, forms and the editor experience, built against real content.
migrate & optimise
Content moved with redirects mapped so you keep the search authority the old URLs earned.
maintain
Updates, monitoring, backups and improvements on a monthly rhythm.
the tools we use
Named, not implied. If a tool is on this list we have shipped production work with it.
core
- WordPress
- custom post types
- custom taxonomies
- WP-CLI
content engineering
- JetEngine
- Advanced Custom Fields
- Crocoblock suite
- Gutenberg blocks
commerce
- WooCommerce
- Stripe & PayPal
- subscriptions
- shipping rules
performance & search
- object & page caching
- Cloudflare
- Rank Math or Yoast
- schema markup
questions people ask
Is WordPress still a good idea in 2026?
For content-heavy sites, yes. It remains the fastest route to a site where non-technical people publish confidently, and with custom post types and proper templating it handles thousands of structured entries happily.
Are page builders like Elementor fine?
For a small site, they are workable. At scale they add weight and lock your layout into a plugin. We use coded templates and reserve visual builders for clients who genuinely need to compose new pages themselves.
Do we need a maintenance plan?
If nobody is responsible for updates, a WordPress site becomes a security problem within a year. Either we look after it, or your host does, but somebody must.
read deeper
Written from the work, not from a keyword list.
start somewhere
what are you trying to make better?
Answer a few quick questions and we will come back with a price bracket, a timeline and a scope you can hold us to.