# article (/docs/showcase/templates/article)

> Long reading under a page head: services, install notes, terms and the page after a form.



Use `article` for a page a reader reads rather than scans: services explained, install notes, terms, an about page, and the short page a form lands on. A `page-head` or the article's own head names it; the body stays inside the article Markdown subset.

## Sections in order

**Slot rules.**

Required and optional slots are not in 7.0.0-alpha.0. `PageSchema` accepts `"template": "article"` and checks no slot; the order above is read from the records.

## Fields that matter

<details className="mx-sc-details">
<summary>Every field of page-head</summary>

</details>

<details className="mx-sc-details">
<summary>Every field of article</summary>

</details>

## Starter record

**Using an agent? Paste this prompt**

```text
Read https://next.mdxui.dev/docs/showcase/templates/article.md, then fetch https://next.mdxui.dev/pages/vanroster/security.json, a article page that parses.
Run pnpm add @mdxui/site@7.0.0-alpha.0.
Rewrite its strings for my Business. Keep its Section types in their order; drop one only when my Business has nothing to say there.
Parse it with PageSchema.safeParse. When it refuses, shorten the content at the path it names, never the bound.
Render it with renderPage and save the HTML file.
```

## Other Templates