Files
coder/docs/about/screenshots.md
T
Nick Vigilante bc77c40296 docs: add front-matter titles to mechanical and no-H1 pages (Phase 3) (#28030)
## Summary

**Batch A of Phase 3** of the H1 → front-matter migration (`DOCS-484`;
parent `DOCS-477`). Adds a front-matter `title` to every navigable docs
page whose title can be migrated **mechanically**, with no editorial
judgment.

This is the content step that Phase 1 (renderers prefer front-matter
title, `DOCS-482`) and Phase 2 (tooling + generators front-matter-aware,
`DOCS-483`) unblocked. Both are merged; coder.com #964/#974 are merged
and live.

**Rendered no-op.** The renderers already resolve the page title from
the manifest and hide the leading body H1 (Phase 1), so no page changes
visually. This just moves the title into front matter where Fumadocs and
the migrated tooling can read it.

## What's in this batch

Dry-run on `main` (464 navigable pages) splits into:

| category | count | this PR |
|----------|-------|---------|
| already has front-matter title (Reference, from Phase 2 generators) |
196 | skipped (idempotent) |
| **mechanical** — leading body H1 equals the manifest label | 138 | ✅
add front-matter `title`, drop the duplicate H1 |
| **no body H1** — renders under the manifest label only | 4 | ✅ add
front-matter `title` only |
| **mismatch** — body H1 differs from the manifest label | 126 | ⏭️
deferred (needs an editorial decision, see below) |

142 files changed, all under `docs/`.

## Deliberately out of scope: the 126 mismatches

Pages where the body H1 is richer than the short sidebar label (e.g.
label **Modules** / H1 *Contributing modules*, label **Install** / H1
*Installing Coder*) need a canonical-title decision, not a script. A few
even look like the body H1 is the redundant one (`install/cli.md` and
`install/index.md` both carry the H1 *Installing Coder*). These will
land in follow-up batches **by nav section** once the policy is set, so
each gets real review.

## Verification

AI was the primary author of this PR (see disclosure below); per the [AI
Contribution
Guidelines](https://coder.com/docs/about/contributing/AI_CONTRIBUTING)
here is the manual verification.

- Every added front-matter block parses as YAML and its `title`
round-trips to the manifest label (checked programmatically across all
142 files).
- Every removed line is a leading `# H1` that equalled the manifest
title; no body prose was reflowed. Front matter is correctly hoisted
above pre-existing `<!-- markdownlint-disable -->` comments on the two
pages that had them.
- `pnpm check-docs` (markdownlint-cli2 + table formatter) passes on the
changed set: `Summary: 0 error(s)`. `MD041` stays off (re-enabled in
Phase 4); `MD025` is not tripped because the duplicate body H1s are
removed.

```
$ pnpm exec markdownlint-cli2 $(git diff --name-only origin/main)
Linting: 142 file(s)
Summary: 0 error(s)
```

Linear: DOCS-484

> This PR was created with AI assistance (Coder Agents).
2026-08-27 12:34:13 -04:00

3.1 KiB
Raw Blame History

title
title
Screenshots

Log in

Install Coder in your cloud or air-gapped on-premises. Developers simply log in via their browser to access their Workspaces.

Install Coder in your cloud or air-gapped on-premises. Developers simply log in via their browser to access their Workspaces.

Templates

Developers provision their own ephemeral Workspaces in minutes using pre-defined Templates that include approved tooling and infrastructure.

Developers provision their own ephemeral Workspaces in minutes using pre-defined Templates that include approved tooling and infrastructure.

Template administrators create templates using the template builder, which guides them through selecting base infrastructure and adding modules.

Template administrators create templates using the template builder, which guides them through selecting base infrastructure and adding modules. Templates can also be created from scratch or uploaded directly.

Templates define the underlying infrastructure that Coder Workspaces run on.

Template administrators build Templates using Terraform. Templates define the underlying infrastructure that Coder Workspaces run on.

Workspaces

Developers create and delete their own workspaces. Coder administrators can easily enforce Workspace scheduling and autostop policies to ensure idle Workspaces don’t burn unnecessary cloud budget.

Developers create and delete their own workspaces. Coder administrators can easily enforce Workspace scheduling and autostop policies to ensure idle Workspaces don’t burn unnecessary cloud budget.

Developers launch their favorite web-based or desktop IDE, browse files, or access their Workspace’s Terminal.

Developers launch their favorite web-based or desktop IDE, browse files, or access their Workspace’s Terminal.

Administration

Coder administrators can access Template usage insights to understand which Templates are most popular and how well they perform for developers.

Coder administrators can access Template usage insights to understand which Templates are most popular and how well they perform for developers.

Coder administrators can control every aspect of their Coder deployment.

Coder administrators can control every aspect of their Coder deployment.

Coder administrators and auditor roles can review how users are interacting with their Coder Workspaces and Templates.

Coder administrators and auditor roles can review how users are interacting with their Coder Workspaces and Templates.

Coder administrators can monitor the health of their Coder deployment, including database latency, active provisioners, and more.

Coder administrators can monitor the health of their Coder deployment, including database latency, active provisioners, and more.