​

Help Center article runbook

​

Before editing

1. Fetch the latest main and branch from it.
2. Name the branch MMDD-short-topic (Lillian’s style). Lowercase letters, numbers, and hyphens only. Example: 1026-mcp-tool-catalog.
3. Change only the articles named in the request. Do not add steps, screenshots, or tools the spec says to leave out.

​

Where articles live

​

Create an article

1. Add an MDX file with a title in the frontmatter.

---
title: "Article title"
---

2. Put screenshots in images/imgs/. Reference them from the article:

<div className="img-frame">
  <img src="/images/imgs/article-name-1.png" noZoom />
</div>

3. Add the page path, without .mdx, to the right nav group in both mint.json and docs.json. Keep the two files in the same order.
4. Link to other articles with site paths, such as /docs/article/auto-headline.

​

Update an article

1. Edit the existing MDX. Keep wording the spec says is already fine.
2. When replacing a screenshot, use a new filename so browsers do not keep the old image. Delete the old file if nothing else references it.
3. If a URL is going away, add a redirect. Do not leave the old page live.

​

Sunset an article

1. Delete the MDX file.
2. Add the same redirect to mint.json and docs.json:

{
  "source": "/docs/old-path",
  "destination": "/docs/article/current-article"
}

3. Delete images that only the retired page used.
4. Leave the replacement article in place.

​

Writing rules

• The style prop is a JSX object with camelCase keys: style={{ width: '100%' }}. Never a string.
• Images must be under 10MB. CI rejects anything larger, and it rejects a src that points at a missing file.
• Do not commit screenshots sitting in the repo root. Those are local leftovers.

​

Preview

​

Pull request

• One sentence on why, then a short point-form body. No extra commentary.
• Assign the reviewers named in the request.
• A merge to main publishes the site.