CONTENT MODEL WORKSHEET
Purpose: model a small website before configuring the CMS.
Use: list real items, propose fields and relationships, then try three varied examples per type.
Fictional community workshop:
Service: ID, title, summary, eligibility, booking route, contact reference.
Staff profile: ID, name, role, biography, portrait asset.
News item: ID, title, publication date, body, related service.
Contact: ID, team name, email, telephone.
SVC-001 and SVC-002 reference CONTACT-01. SVC-003 uses CONTACT-02.
Change CONTACT-01's email and verify both dependent public pages after release.
The third service should keep its own contact.

Your model:
Type / reader task:
Example items (three):
Field / data type / required at publication? / allowed values:
Shared relationship / target ID / reason for sharing:
Asset / rights or source / alternative text:
Fact owner / reviewer / publisher:
Public URL:
Optional field display rule:
Publishing dependency and cache/rebuild behavior:
Success evidence:

Publishing path:
Author -> typed content item -> factual review -> template preview
       -> approved release -> render/build -> navigation/search -> public check
An asset supplies a file; metadata describes an item; a template presents fields.
A changed shared fact may require release/rebuild of dependent pages.
Test long titles, absent optional fields and unusual but valid records.
Record unresolved questions before importing the whole library.

Source guide: https://yenra.com/web-content/
Prepared October 4, 2026.