Decide when to create a custom content model

A custom content model is useful when editors will create many entries with the same meaning, fields, classifications, and presentation. It is unnecessary overhead when the requirement is only a visual variation on one page.

Start with the visitor task

Write one sentence that describes what visitors need to do. For example:

Visitors need to browse instructors by specialty and open a page for each instructor.

That requirement suggests:

• A custom post type for instructors
• A taxonomy for specialties
• Custom fields for values such as professional title
• An archive or Faceted Search result template

Do not begin with field names. Begin with the collection, its public purpose, and the routes visitors need.

Choose the smallest suitable structure

Use an existing post or page when

• The content behaves like an article or a normal hierarchical page.
• It does not need a separate administration menu.
• Its differences can be expressed with the existing editor and template settings.

Add a taxonomy when

• Editors select from a shared vocabulary.
• Visitors benefit from archive pages for those terms.
• The same classification can apply to multiple entries or post types.

Do not replace a taxonomy with a free-text field when filtering and archive navigation matter.

Add a custom post type when

• The collection needs its own editor menu and public identity.
• Entries share the same fields and template.
• The collection needs its own archive, query, taxonomy, or permission behavior.

Add a custom field when

• The value describes one property of an entry.
• Editors should enter the value separately from the main content.
• A template, query, API consumer, or Faceted Search configuration will use it.

Test the decision

Before building, answer these questions:

1. Will the site contain at least several entries of this kind?
2. Will editors understand why the collection is separate?
3. Does each proposed field have a consumer?
4. Does every taxonomy represent a reusable classification?
5. Are single and archive URLs required?
6. Is a Page Builder layout insufficient on its own?

If most answers are no, keep the content in an existing post type. If they are yes, continue with the planning worksheet.