This checklist defines how Pages and Posts are used within the content system. Its purpose is to eliminate ambiguity by clearly assigning responsibilities to each content type before any content is created.
Decisions made here determine how content is organized, linked, maintained, and scaled over time.
Checklist Objective
Establish a clear, documented model for how Pages and Posts are used, including what each is responsible for and what it is not.
Preconditions
- Planning 01 — Site Purpose & Scope Definition is completed and approved
Checklist Steps — Post/Page Structure
1. Define the purpose of Pages
- Identify Pages as authoritative, long‑lived content
- Use Pages to define systems, policies, and stable reference material
- Confirm Pages are not used for frequent updates or procedural steps
- Confirm Pages are not used as content feeds or streams
2. Define the purpose of Posts
- Identify Posts as checklist‑driven or procedural content
- Use Posts for items that may be updated, expanded, or retired over time
- Confirm Posts support Pages rather than replace them
- Confirm Posts do not define new systems or scope
3. Identify landing pages
- List top‑level entry pages that represent major systems
- Confirm each landing page has a single, clear responsibility
- Confirm landing pages route to checklists or runbooks, not content
4. Define post usage rules
- Confirm Posts are atomic and executable
- Confirm Posts are written as checklists or runbooks
- Confirm Posts do not embed system‑level decisions
5. Confirm excluded content patterns
- No hybrid Page/Post usage
- No Pages used as frequently updated logs
- No Posts used as permanent reference pages
6. Review alignment with navigation planning
- Read Page and Post titles only
- Confirm the content model supports navigation structure
- If conflicts exist, pause and resolve before proceeding
Required Output
- Clear definition of what Pages are used for
- Clear definition of what Posts are used for
- List of landing pages and their responsibilities
- Explicit exclusions of unsupported content patterns
Pause & Lock
The Page/Post content model is now locked. All downstream formatting, image standards, and editorial workflows must follow this structure.
Proceed to: Content Systems — Formatting Rules