Skip to content
John Carter Portfolio

Capability

WordPress and Web Systems

Custom WordPress structures, child themes, CPTs, ACF fields, responsive templates, and publishing workflows built for real editors.

I build WordPress systems around the content model first: post types, fields, templates, navigation, and editing flows that make the site easier to maintain after launch.

For me, WordPress works best when it is treated as a publishing system, not just a page builder. A good setup gives each type of content a clear home, a clear purpose, and a clear way to be reused across the site.

That can mean custom post types for case studies, capabilities, design archive items, radio shows, campaign posts, resources, or internal project records. It can also mean custom fields, taxonomies, shortcodes, archive templates, single templates, and REST API workflows that make the site more structured and less fragile.

My focus is on building systems that real editors can use. The backend should make sense. The fields should match the way the content is actually created. The front-end templates should pull from structured data instead of relying on manual layout work every time something new is published.

This approach keeps the site easier to update, easier to expand, and easier to connect to future workflows.

WordPress becomes the place where content, structure, design, and publishing logic come together.

What This Capability Covers

  • WordPress child theme structure
  • Custom post type planning
  • ACF field groups and structured fields
  • Archive and single template planning
  • Responsive page templates
  • Shortcodes and reusable sections
  • Taxonomies and content relationships
  • Editor-friendly publishing workflows
  • REST API content creation workflows
  • Private and role-based site structures

How I Use This

I use WordPress and web systems work to turn a site from a collection of pages into a structured publishing environment.

That might mean building a portfolio where case studies and capabilities are reusable content types. It might mean creating a private media platform with member areas, social posts, radio entries, TV feeds, and internal planning tools. It might mean building a campaign generator where structured fields help turn a subject and creative brief into a scheduled content series.

The work usually starts with questions like:

  • What kinds of content does this site actually need?
  • What fields should each content type have?
  • What should editors be able to update without touching code?
  • Where should the content appear across the site?
  • Which parts should be reusable, automated, or connected through the REST API?

Related Case Studies