> ## Documentation Index
> Fetch the complete documentation index at: https://docs.open.cx/llms.txt
> Use this file to discover all available pages before exploring further.

# Articles

> Write, version, publish, and AI-generate help center articles that ship to your public site and train the AI at the same time.

Help Center articles are the long-form content customers read on your public site and the AI retrieves from at answer time. Every article lives in a category, supports every language you've enabled, and keeps a version history per language.

<Tip>
  Open an article from [**Help Center**](https://platform.open.cx/help-center) — click a category in the sidebar, then pick or create an article.
</Tip>

## Lifecycle

An article has a **source version** (the original-language content you write) and a **locale version** per enabled language (translations).

* **Draft** — a source version not yet published. The public site shows the previously published version (or hides the article if there's never been one). The AI does not train on drafts.
* **Published** — the source version is live on the public site and in the AI's training index.
* **Updated** — editing a published article creates a new draft source version. Publishing it supersedes the previous one; the old version stays in history so you can roll back.

Translations follow the same model: each language has its own published/draft state so you can ship an English update before translations are reviewed.

## Content format

Articles are written in Markdown, edited either visually or in source mode.

<Tabs>
  <Tab title="Visual editor">
    The default mode. Rich-text editor with toolbar for headings, lists, links, images, code blocks, callouts, and tables. It writes Markdown under the hood — nothing is locked to the visual editor.
  </Tab>

  <Tab title="Markdown source">
    Click the **source mode** toggle (top of the editor) to edit Markdown directly. Useful for paste-in content, bulk find-and-replace, or authoring in your own editor and pasting over. All standard Markdown is supported, including fenced code blocks, tables, and inline HTML.
  </Tab>
</Tabs>

### Metadata

Open the **SEO** dialog on any article (gear icon on the editor) to set the fields that control how the article appears publicly:

| Field                | What it controls                                                                                            |
| -------------------- | ----------------------------------------------------------------------------------------------------------- |
| **Title**            | The article headline. Shown on the public site and in search previews.                                      |
| **Description**      | A short summary. Fed to the AI for retrieval and shown in search results.                                   |
| **Slug**             | The URL segment — e.g. `reset-password`. Auto-generated from the title; override when you want stable URLs. |
| **Meta title**       | Overrides Title for `<title>` in HTML. Use when you want a different length or phrasing for SEO.            |
| **Meta description** | Overrides Description for the `<meta description>` tag.                                                     |

## Version history

Every publish writes an immutable source version. Each row in the history panel shows the version number, who published it, and when.

* **Open history** — the clock icon in the editor header. Shows versions across the primary language.
* **Roll back** — pick a version and click **Restore**. The content loads into your current draft; publish when you're ready.
* Rolling back does not delete newer versions — it's additive. Publishing the restored content creates yet another version on top.

## Generate from a resolved session

OpenCX can draft a new article from the transcript of a resolved conversation.

<Steps>
  <Step title="Open a resolved session">
    In [**Inbox**](https://platform.open.cx/inbox), open any resolved session. The right sidebar has a **Generate Help Center article** action.
  </Step>

  <Step title="Pick destination">
    Select the Help Center and the category the article should land in.
  </Step>

  <Step title="Review the draft">
    OpenCX writes a structured article — title, summary, body — and creates it as a draft in the category you chose. Nothing is published and nothing trains the AI yet.
  </Step>

  <Step title="Edit and publish">
    Open the article from the Help Center, edit as needed, run it through your content rules, and publish.
  </Step>
</Steps>

## Good to know

<AccordionGroup>
  <Accordion title="Publishing an article also trains the AI" icon="brain">
    Every published article is indexed for retrieval at answer time. There's no separate "sync to AI" toggle — publish is the trigger, unpublish is the removal.
  </Accordion>

  <Accordion title="Translations publish independently" icon="language">
    English and French versions of the same article have separate publish states. You can ship the English update today and wait on the French translation until tomorrow without blocking either. See [Translations](/help-center/translations).
  </Accordion>

  <Accordion title="Content rules run before publish" icon="shield-check">
    If you've set up [content rules](/help-center/content-validation) with **block on publish**, a failing `must` rule will prevent the publish action from succeeding. `Should` rules warn but don't block.
  </Accordion>

  <Accordion title="Delete is permanent" icon="trash">
    Deleting an article removes it from the public site, from the AI's training index, and from version history. Use unpublish if you want the article off the site without losing the content.
  </Accordion>
</AccordionGroup>

***

## Related Documentation

<CardGroup cols={2}>
  <Card title="Categories" icon="folder-tree" href="/help-center/categories">
    Group articles for navigation and bulk actions.
  </Card>

  <Card title="Translations" icon="language" href="/help-center/translations">
    Multi-language, glossary, manual-edit protection.
  </Card>

  <Card title="Content rules" icon="shield-check" href="/help-center/content-validation">
    Enforce tone and policy before publish.
  </Card>

  <Card title="Help Center overview" icon="book-open" href="/help-center/overview">
    Everything the Help Center does.
  </Card>
</CardGroup>