Custom fields without losing your mind

Real content is almost never «title plus text». You want a subtitle, a label, an accent colour, a reading time… All of that is custom fields, and they’re precisely what turns your WordPress into a proper CMS rather than a glorified notepad.

Native meta, no plugins

WordPress lets you register fields and publish them to the REST API directly, without installing anything:

<?php
register_post_meta( 'post', 'subtitle', array(
  'type'         => 'string',
  'single'       => true,
  'show_in_rest' => true,   // ← the line that makes it visible in the API
) );

That show_in_rest line is the key: it makes the field show up inside each post at /wp-json/wp/v2/posts, ready for the front end to render wherever it likes. This very site uses it for the accent colour of each card: it isn’t in the design, it comes out of a CMS field.

What about ACF?

If whoever edits is going to touch a lot of content, Advanced Custom Fields gives them a comfy interface in the editor: date fields, image fields, select fields… With the «Show in REST» option turned on, those fields come out through the API just the same. The front end doesn’t even notice which of the two methods you used: it sees JSON and that’s that.

Model content as data, not as text. You add the design afterwards, without touching what the editor wrote.

Check it

After registering a field and filling it in on a post, watch it come out through the API:

curl "http://your-site.local/wp-json/wp/v2/posts/1?_fields=title,meta"

Let your agent design them

Add custom fields to my posts following the wp-wow skill:
register native meta with show_in_rest (subtitle, accent colour and
reading time) and show me how they look in the REST API.

With the content well structured, it’s time to send it out into the world. Let’s talk about the deploy.