// service · wordpress development
WordPress development
Headless or classic — scaled, hardened, and migrated when it's time.
WordPress is still the right answer for editorial-heavy sites where non-developers need to publish daily. We modernize the WP install (Bedrock, secrets in env, deploys via CI), build content models that editors actually like, and front it with whatever frontend stack matches the site’s ambition — from a fast classic theme to a full Astro/Next headless frontend.
Stack & defaults
CMS
WordPress + Bedrock
API
WPGraphQL / REST
Frontend (headless)
Astro / Next.js
Frontend (classic)
Roots Sage
Cache + Media
Cloudflare + R2
Content modeling
ACF Pro
Tooling
Composer + Trellis
Observability
Sentry
What you receive
Hardened install
Bedrock layout, secrets out of the repo, plugin auto-updates pinned and reviewed.
Editor-friendly content model
ACF blocks designed with editors in the room. No 'guess the field name' guessing.
Edge caching + image pipeline
Cloudflare cache rules, R2-backed media, on-demand image variants.
Headless or classic, your call
Astro/Next + WPGraphQL when it pays off; Sage when classic is right.
Migration from anything
Webflow, Squarespace, custom CMS — we've moved sites with 10k+ posts intact.
Editor training + handoff doc
Loom walkthroughs and a one-pager. Your editors are productive on day one.
Timeline
Wk 1
Audit / IA
Content audit, IA proposal, content model agreement.
Wk 2–3
Build
Theme/headless frontend, ACF blocks, design system.
Wk 4–5
Migrate + harden
Content migration, redirects, security pass.
Wk 6
Launch
DNS cutover, editor training, post-launch sweep.
FAQ
Should I go headless or classic?
Headless if your frontend needs are demanding (heavy interactivity, multiple frontends, perf-sensitive). Classic if your editors live inside WP and the frontend is essentially a brochure.
Can you handle the migration from my current CMS?
Yes. We've moved sites from Webflow, Squarespace, custom CMSs, and ancient WordPress installs. We script the data, redirect every URL, and validate post-cutover.
What about WP plugins?
We pin and review. Auto-updates are configured but go through a staging build first. We avoid plugins that ship with their own 'kitchen sink' frameworks.
Do you cover WooCommerce?
For simple stores yes. For anything with serious cart logic, payments, or B2B pricing we'll usually recommend a headless setup with Stripe + a real backend instead.