# Content Model

Use this file to decide what kind of page to create before writing HTML. Pair it with `docs/FOUNDATION-IA.md`, `docs/CONTENT-INVENTORY.md`, and `docs/EDITORIAL-ROADMAP.md`.

## Foundation Page

Purpose: explain one building block before introducing the full Design Harness.

Template: `article-template.html`

Best sources:

- `docs/FOUNDATION-IA.md`
- `docs/FOUNDATION-GLOSSARY.md`
- `docs/FOUNDATION-LESSONS.md`
- current `AGENTS.md`
- current `DESIGN.md`
- `docs/design-system/*`
- `docs/HARNESS-ROADMAP.md`
- `designer-ai-articles/claude-design-agents.md`
- PM skills pack taxonomy as format reference

Recommended structure:

1. What this thing is
2. Why designers should care
3. What problem it solves
4. What format it uses
5. How it fits into orchestration
6. Example from Planark or this site
7. How it leads into the Design Harness

Done means:

- the page explains the concept in designer language, not tool jargon
- it includes a concrete file, format, or workflow example
- it points to the next foundation page or the Harness overview

## Workflow Page

Purpose: teach a repeatable design ops loop.

Template: `article-template.html`

Best sources:

- `planark-build-book/03-html-mockups.md`
- `planark-build-book/05-debugging-evidence.md`
- `planark-product-book/05-real-data.md`
- `designer-ai-articles/claude-design-agents.md`

Recommended structure:

1. Problem
2. When to use it
3. Inputs
4. Context the agent needs
5. Prompt or task pattern
6. Human review step
7. Validation step
8. Saved output
9. Example from real work

Done means:

- the workflow has an input, process, review step, and validation step
- the page includes one reusable artifact: checklist, prompt, table, terminal/file tree, or reference group
- the page links back to Harness or Reference

## Harness Page

Purpose: explain a reusable, downloadable system.

Template: `article-template.html`

Best sources:

- `docs/HARNESS-ROADMAP.md`
- `planark-build-book/02-tool-stack.md`
- PM skills pack taxonomy
- existing `AGENTS.md`, `DESIGN.md`, and design-system docs

Recommended structure:

1. What it gives you
2. Who it is for
3. Folder structure
4. Files included
5. Setup instructions
6. Example workflow
7. How to adapt it
8. Download or placeholder CTA

Done means:

- the page makes the harness feel ownable, not abstract
- the file structure is explicit
- the user understands what to copy, edit, and validate

## Case Study Page

Purpose: prove the workflows through real product work.

Template: choose based on purpose.

- Use `editorial-template.html` for product stories and arguments.
- Use `article-template.html` for artifact-heavy case studies with process diagrams, source tables, and reusable lessons.

Best sources:

- `planark-product-book/01-origin.md`
- `planark-product-book/02-not-a-chatbot.md`
- `planark-product-book/03-regional-discovery.md`
- `planark-product-book/04-trip-builder.md`

Recommended structure:

1. Product context
2. Design/product problem
3. Workflow used
4. AI role
5. Human judgment role
6. Artifacts
7. Validation
8. Lessons

Done means:

- the case study distinguishes AI role from human judgment
- the proof comes from real Planark decisions, not generic claims
- the page links to one related workflow

## Field Note

Purpose: share personal experience and judgment.

Template: `editorial-template.html`

Best sources:

- `planark-build-book/01-designer-builder.md`
- `planark-build-book/04-api-security.md`
- `planark-build-book/06-ai-product-judgment.md`
- `planark-product-book/01-origin.md`

Recommended structure:

1. Concrete moment
2. What changed
3. What AI helped with
4. What AI did not solve
5. Lesson
6. Reusable takeaway

Done means:

- the piece starts from a concrete moment
- it does not become a generic AI opinion essay
- it ends with a practical takeaway the reader can reuse

## Reference Page

Purpose: define tools, files, terms, and patterns without turning the site into a directory.

Template: `article-template.html`

Best sources:

- `designer-ai-articles/claude-design-agents.md`
- PM skills pack README and GUIDE
- current `AGENTS.md`, `DESIGN.md`, and Harness docs
- design-system docs

Recommended structure:

1. What this reference explains
2. When it matters
3. Definitions
4. Comparison table
5. Example
6. Related workflows

Done means:

- every reference item says what it is for and when to use it
- no tool is listed without a workflow reason
- the page links to one practical workflow

## Index Page

Purpose: help readers choose the next page.

Template: normal site page, not an article template unless the page needs long-form structure.

Required elements:

1. clear section promise
2. 3-6 featured links
3. source or status labels
4. next-step CTA

## Derivative Content

Purpose: adapt a source chapter into distribution and course material.

Canonical flow:

```text
site/course chapter -> LinkedIn article -> LinkedIn post -> email lesson
```

Locations:

- source chapters: `docs/chapters/`
- LinkedIn articles: `docs/social/linkedin-articles/`
- LinkedIn posts: `docs/social/linkedin-posts/`
- email lessons: `docs/email/`
- system rules: `docs/content-system/README.md`

Rules:

- The chapter is the source of truth.
- LinkedIn articles can later become Medium or Substack posts.
- LinkedIn posts test the hook and invite conversation.
- Emails teach one lesson, one action, and one artifact.
- Do not create a new argument for every derivative. Adapt the same idea to the format.