What is a custom field?
Out of the box, a CMS gives every post the same handful of slots: a title, a body, a featured image, a date, a category. A custom field is a slot you add. A case study might get a client name, an industry and a year. A product might get a price, a material and a size chart. A glossary term might get a one-line definition and a list of questions and answers. Each is stored separately from the body, under a name, where templates and code can find it.
In WordPress custom fields are post meta, created directly or through a plugin such as Advanced Custom Fields that gives editors a proper form for each one. Other systems call them fields, attributes or properties. The idea is the same everywhere: structured data instead of a blob of text, so the same content can be shown, sorted, filtered and reused in more than one way.
Why it matters
Why a custom field matters
Structure is what makes a site more than a pile of pages. With the client name in its own field, the site can build a page per client automatically. With the year in a field, the work can be sorted. With the FAQ in fields, it can be rendered as fold-out questions on the page and as schema markup for search engines at the same time, from one source. Without custom fields, editors fake structure with formatting inside the body, and every redesign means rewriting every page by hand.
In practice
How a custom field works in practice
- 01
The work begins with modeling. Before anything is built we list the kinds of content the site has, what each one needs to carry and how it will be displayed, then define fields to match. Names matter: a field called client, used consistently across every project, is worth more than ten clever ones used once. Field types matter too, so a date is a date picker, a relationship is a link to another post, a choice is a select list.
- 02
Then the templates read them. A case study template pulls the client, the credits and the deliverables from their fields and lays them out the same way every time, so editors never touch layout. The fields also feed the parts of the page nobody sees: the meta title, the Open Graph image, the structured data. The result is a site where adding a project is filling a form, and the form cannot be filled wrong.
At RIOT
Custom fields at RIOT
This glossary is built on custom fields. Each term carries its definition, its category and its questions and answers as separate fields, and the page template assembles them: the definition becomes the lede, the questions become the fold-out FAQ and the FAQ schema that search engines read. riot.nyc is a WordPress site we design and build ourselves, so the fields are the ones we need and no more.
Watch out
What people get wrong about custom fields
Using the body for everything. A page with the price typed into a paragraph is a page that cannot be sorted by price. The opposite mistake is field sprawl: a template with sixty optional fields that editors fill inconsistently, so half the site shows gaps. Fields should be few, named plainly and required where they matter. And they should be planned before the content is written, because migrating unstructured text into fields afterwards is slow, dull work.
