WordPress site fleet
Tens of WordPress builds across verticals. Realtors, doctors, politicians, retailers, B2B e-commerce. Custom themes when stock will not do, ACF and Gutenberg blocks for editors, performance and accessibility on every build. Hosting and maintenance under contract when wanted.
The problem
A studio needed WordPress builds across many verticals: realtors, doctors, politicians, retailers, B2B e-commerce. Off-the-shelf themes did not differentiate the brands; plugin sprawl broke at every core update; performance and accessibility lagged. Hosting was inconsistent across the fleet, and editors learned a different admin per site.
The approach
We built dozens of bespoke WordPress sites on a shared theme architecture: per-site customization via ACF and Gutenberg blocks designed for editors, performance budgets enforced at deploy time, WCAG 2.2 AA accessibility from day one, LiteSpeed-tuned hosting under contract for sites that wanted it. Every site has a structured block library so editors compose pages without HTML, and the shared admin pattern means an editor moves between sites without retraining.
Stack and engineering choices
- WordPress core + custom theme
- ACF + Gutenberg block library
- WCAG 2.2 AA from day one
- Performance budgets in CI
- LiteSpeed-tuned hosting
- Per-site config via ACF options
- Maintenance under contract
Outcome
Editors run their own sites; developers ship updates across the fleet without per-site contortions. Performance and accessibility stay green through feature work. Hosting and maintenance are predictable line items, not surprise tickets, and an editor moving between brands lands in a familiar admin.
See more web development work at quadevs across other engagements with similar shape.
Have a project that overlaps this work?
Send a one-paragraph brief. We reply within one business day.
hello@quadevs.com