pom://theme/content-model-guide: design a complete POM content model

This resource is for coordinated custom post type, taxonomy, field, template, and assignment work. It prevents a client from creating isolated schema pieces that cannot render together.

Model as one system

Before writing, define:

• the custom post type identity and public behavior;
• associated taxonomies and whether they have public archives;
• custom fields, value types, and realistic empty states;
• the archive page shell;
• the single-item presentation;
• the feed card used inside listings;
• template assignments and representative test content.

Archive, single, and feed templates are separate contracts. An archive template owns the archive shell and must provide the results insertion point. A feed template owns each result card. A single template owns one content item.

Safe implementation order

1. Read this guide and all three template resources.
2. Inspect the current model and relevant live schemas.
3. Obtain the permitted merge tags for each context.
4. Draft and validate every template before changing the model.
5. Run pom_theme_configure_content_model with dry_run: true.
6. Review every reported operation and conflict.
7. Apply only after confirmation.
8. Create draft test content, terms, fields, and media.
9. Verify archive, single, and feed output with populated and empty values.

The content-model operation coordinates several changes but is not transactional. A failure can leave earlier operations applied, so inspect current state before retrying.

Do not invent merge tags from field labels. Use the live catalogs and exact stored field names. Keep test content in draft until assignments and public output have been reviewed.

Related guides: create a POM content model, content-model tool, and template resources.