WordPress craft

WordPress development that editors can live in

I build and maintain WordPress sites as a contractor or team hire: themes, plugins, ACF, custom post types, Gutenberg, and the glue that keeps content teams productive. Not a page-builder specialty profile: real WordPress engineering with clear handoff to the people I work with.

Custom & child themes

Brand-true themes built around your pages and publishing flow, with lean assets, semantic markup, and templates that survive core updates.

Advanced Custom Fields (ACF)

Field groups, flexible content, options pages, and relationship fields modeled so editors fill structured data, not fight the UI.

Custom post types & taxonomies

CPTs for products, team, events, case studies, and more, registered cleanly with archives, REST/GraphQL exposure, and admin UX that matches how you work.

Gutenberg & block themes

Custom blocks, block patterns, template parts, and FSE-aware builds so the block editor feels like your design system, not a blank canvas.

Plugins & integrations

Purpose-built plugins, WooCommerce hooks, forms, CRM connections, and third-party APIs, without stacking five tools that do one job badly.

Performance & maintainability

Caching strategy, asset hygiene, accessibility, and update-safe architecture so the site stays fast and editable after launch.

How I work across the WordPress stack

Classic PHP, block themes, ACF page sections, or a hybrid. I help the team pick what fits editors and the roadmap, not a one-size template.

Classic PHP themes

Template hierarchy, hooks, enqueue discipline, and child themes when you need surgical changes on an existing install.

Block / hybrid themes

theme.json, patterns, and custom blocks when the editorial team lives in Gutenberg and needs reusable layouts.

ACF-driven page building

Flexible content and clone fields that map to component sections: structured enough for consistency, flexible enough for marketing pages.

Editor training & handoff

Short docs and walkthroughs so your team can publish without calling a developer for every headline change.

Where I fit

  • Teams hiring a WordPress engineer (contract or full-time) who can own theme and plugin work
  • Product or marketing orgs stuck on a bloated page builder who need cleaner, faster WordPress
  • Squads that need CPTs and ACF for real content models, not just blog posts
  • Sites migrating themes, consolidating plugins, or preparing for headless later

Need the CMS for content and a Next.js frontend for performance? See WP Engine Headless + Next.js. Prefer staying fully on WordPress with a strong theme and plugin layer? This is the skill set I bring to that role.