# Resource articles — OM1

Playbook for **standard resource articles** — blogs, case studies, publications, whitepapers, podcasts, and news items where the URL includes a **topic segment**.

## URL patterns

| Pattern | Examples |
|---------|----------|
| `/resources/{type}/{topic}/{slug}/` | `/resources/case-studies/ai/bringing-treatment-resistant-depression-to-light-ai-driven-patient-discovery-in-real-world-data/` |
| `/resources/{type}/{topic}/` | Tag listing index (taxonomy-driven) |
| `/resources/{type}/` | Article type landing (e.g. `/resources/publications/`) |

**Not in this playbook:** Ebooks at `/resources/ebooks/{slug}/` — use `ebook-pages` (no topic segment).

Primary topic comes from the article's **primary tag** — must match the URL segment (`ai`, `registries`, etc.).

## Typical content stack

Article detail pages use the article type template — do not duplicate hero blocks in `content` unless the template expects them.

| Region | Type | Role |
|--------|------|------|
| Template hero | **Article hero** (article-sourced) | Title, subtitle, authors, date, tags, featured image |
| Body | **Article rich text** | Main article copy |
| Optional blocks | **Quote**, **Callout**, **Linked visuals** | In-body components as needed |
| Related content | **Related articles** collection | Often auto-hydrated at template level |

**`content` should contain body components** — hero fields come from the article entry and template.

## Article type → clone reference

| Type slug | Clone when |
|-----------|------------|
| `case-studies` | `/resources/case-studies/ai/bringing-treatment-resistant-depression-to-light-ai-driven-patient-discovery-in-real-world-data/` |
| `blogs` | `/resources/blogs/registries/fda-draft-guidance-signals-a-new-era-for-post-approval-data-in-cell-gene-therapy/` |
| `publications` | Pick a recent publication from `cms-edit list --type article` |
| `whitepapers` | Gated download + summary pattern |
| `webinars-and-videos` | `/resources/webinars-and-videos/ai/behind-the-insights-ep-01-ai-in-dermatology-real-world-data-with-joseph-zabinski-phd-mem/` |
| `news-and-articles` | Press release pattern |
| `podcasts` | Episode layout with external listen link |

Fetch markdown: `https://www.om1.com/resources/case-studies/ai/bringing-treatment-resistant-depression-to-light-ai-driven-patient-discovery-in-real-world-data.md`

## Required / common fields

| Field | Guidance |
|-------|----------|
| `articleType` | Match intended URL family (`case-studies`, `blogs`, etc.) |
| `title` | Headline |
| `slug` | URL segment — lowercase, hyphenated |
| `date` | Publication date |
| `description` | Meta description |
| `authors` | Ordered Person links |
| `tags` | Topic tags — **primary tag drives URL segment** |
| `featuredImage` | Hero / OG image |
| `summary` | Teaser RTF where used on listings |
| `externalLink` | Optional — publications, webinars |

## Workflow

1. Read `cms-edit://customer/articles` for routing and tag rules
2. `cms-edit index sync` — resolve article types, tags, default featured image
3. `task-create-article` or `create from-json` with correct `articleTypeSlug`
4. Set primary tag to match intended URL topic (`ai`, `registries`, etc.)
5. Set `authors`, `featuredImage`, `description`
6. Add **Article rich text** (and optional in-body components) to `content`
7. `create from-json --dry-run --strict` before save
8. `preview urls` on staging → `diff` → `save` → `task-publish-handoff`

## Out of scope

- **Ebooks** — use `ebook-pages`
- **Events** — use `events-webinars-pages`
- **Books** (`/resources/books/...`) — multi-chapter; coordinate with engineering
- Changing tag listing page layout — edit tags or article type config

## Publish handoff

`save` creates drafts only — publish in Contentful UI when ready.

## Source packages

External briefs/assets: run **`task-source-readiness-review`** first. Structure faithfully — **do not rewrite source copy**. Body is typically a single **Article rich text** (do not invent SE multi-block Case study rich text stacks).