Contentful for WordPress Developers
If your site was previously in WordPress, working through a redesign in Contentful can feel disorienting at first. You are still shaping pages and experiences, but the way content is structured, delivered, and rendered will be different from what you are used to. While partnering with a project team, you have likely been introduced to new patterns and workflows that may not feel fully second nature yet. This guide is here to support you as you move forward. It maps the concepts you already know to their Contentful equivalents so you can evolve your implementation after the project wraps.
The core shift: headless vs. coupled
In WordPress, the CMS and the frontend are tightly coupled. Contentful takes a headless approach, meaning it only handles content storage and delivery. Your frontend (whether it's React, Next.js, or something else) fetches that content via an API and decides how to render it. Think of Contentful as WordPress with the theme layer removed entirely.
Concept mapping
What does not exist in Contentful
A few WordPress staples have no direct equivalent in Contentful. There are no themes, no plugins (that directly affect your site), and no server-side rendering built in. Contentful is purely a content repository. Routing, templating, and presentation logic all live in your frontend application.
This is the biggest mental shift. In WordPress, the CMS owns the page. In Contentful, your code owns the page and asks the CMS for data.
Modeling content
In WordPress, a developer might register a custom post type with ACF fields. In Contentful, you do the same thing through the Content Type editor in the web app (or via the Management API). You define each field's type, whether it is required, and any validation rules. Once published, authors can create Entries based on that Content Type.
References are especially powerful. A Content Type can include a field that links to other Entries, which is how you build relationships between content, similar to post relationships in ACF or custom database joins in WordPress.
Fetching content
Instead of WP_Query or get_posts(), you request content from Contentful's Content Delivery API using a REST endpoint or an official SDK (like GraphQL). Queries are filtered by Content Type, field values, and other parameters. The response is JSON, which your frontend then maps to components.
Once the vocabulary clicks, Contentful's model is straightforward. You are still defining content schemas and creating entries against them. The main difference is that rendering is entirely your responsibility, which gives you more flexibility and more control over the final output.