Headless WP

Running WordPress headless is straightforward right up until you reach the content model itself. Default REST output reflects how WordPress stores its data rather than how a front end intends to consume it, and that gap only widens as a project grows.

Advanced Custom Fields values arrive inconsistently shaped, relationships surface as bare numeric IDs, and media needs a second request to resolve. This starter closes that gap while keeping WordPress as the editing environment that editors know.

Field groups and custom post types are registered in code, so the content model moves through version control instead of living only inside a production database. Responses are shaped explicitly, with relationships resolved and field names normalised.