Skip to content
Kaarne Superstore⌕
Marketing & Messaging

Agree the Content Model Before Adding More Custom Fields

Agree a field’s purpose, example, owner and display use before expanding the content model. Use a compact card to expose duplication and missing rules.

An editor and developer connect a purpose symbol, photo example and page destination to one content card.

The editor asks for a “short description” field. The developer adds it. A week later, the same record also has an “overview,” an “intro” and a “card summary,” with nobody sure which one should change when the offer changes. Begin with the meaning and use of the content, not the next empty input.

Write one representative entry together

In this fictional workshop directory, a developer and editor prepare one real-shaped example before expanding the schema. They need to describe the session, identify who it suits and show a short listing card. The editor brings working copy; the developer brings the places where that copy will appear.

Read the entry as a complete explanation. What does a prospective participant need to understand? Which facts repeat consistently across sessions? Which passage needs normal editorial freedom? A content model should help people maintain those distinctions rather than turning every sentence in the mock-up into a separate field.

Give a proposed field a purpose card

For each candidate, complete a small card:

  • Purpose: what question does this content answer?
  • Example: one representative value, with its source or approval status.
  • Use: where will it appear or be used?
  • Ownership: who can establish and maintain its meaning?
  • Absence: may it be missing, and what should that mean?
  • Relationship: does it duplicate, summarise or refer to another piece of content?

A useful example is: “Card summary; helps a visitor distinguish this workshop in a listing; ‘Practise repairing a simple fabric tear using supplied samples’; used in the workshop archive; programme editor owns it; missing-summary treatment still needs agreement.” That card makes the unanswered part visible instead of burying it in an editor control.

Decide whether the information needs its own field

Ask why this information must be stored separately. A duration may need consistent display in several places. A card summary may be intentionally written for a listing. A paragraph that varies freely between workshops may belong in the main content rather than a new rigid slot.

Do not separate information merely because the first design places it in a coloured box. Conversely, do not hide a consistently structured fact in free text if the actual project needs to maintain or use it separately. The decision should come from the content’s job and the supported implementation, not from a preference for either more fields or fewer.

Resolve duplication before it becomes a maintenance habit

Suppose “intro” and “overview” both describe the same opening explanation. Ask whether they are two genuine editorial outputs or two names for one source. If the listing needs a shorter summary, agree whether it is independently written or derived through the site’s actual behaviour. Do not assume the software keeps two inputs synchronised.

Walk through a change: the workshop now requires prior experience. Which facts and explanations must the editor revise? If the answer depends on remembering several nearly identical fields, clarify the model. Record the dependency even when the team deliberately chooses separate copy for different contexts.

Check types and validation against real examples

Only after the purpose is clear should you choose the supported storage and editing approach. A short string, a number and a relationship to another record have different requirements. ACF’s Text documentation, for instance, describes a single-string input; that description does not make it a substitute for every content structure.

Bring one ordinary example, one allowed omission and one awkward but legitimate value to the discussion. Ask what the editor can enter and what the rendered page should do. Treat these as proposed checks, not evidence that a field provider or generator supports the entire model.

Leave a small model people can explain

Record the agreed field cards and unresolved decisions beside the representative entry. Ask the editor to explain which source they would update for one typical change. Revise the model where the answer still requires the developer’s memory. You can expand it later when a new content requirement is established; more empty slots are not themselves evidence of a more useful structure.

Write a representative entry with the editor before expanding the schema. That entry can later guide how you populate a demonstration of the dynamic layout.

For related preparation, see A Dynamic Template Needs a Small Test-Content Matrix and Replace Demo Content Without Losing the Decisions Behind the Layout.

0

Discussion 0

What did this article make you think about?

Join the conversation

Your email address will not be published. Required fields are marked *

Saved articles

Saved in this browser.