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

# Writing and publishing articles

> The editor, draft state, authorship and SEO.

An article needs three things to exist at all: a title, content, and an author. Everything else — category, position, translations, SEO fields — sits on top of that minimum.

## Writing

The content editor is the same rich-text editor used elsewhere in the dashboard, not a separate Markdown dialect to learn. Formatting, links and images work the way they already do when you're composing a reply.

Every new article is created as a draft, regardless of what status you try to set on creation — publishing is always a separate, deliberate second step.

## States

| State | Visible publicly | Agent can answer from it |
| - | - | - |
| `draft` | No | No |
| `published` | Yes | Yes |
| `archived` | No | No |

<Warning>
  **Draft and archived look the same from the outside, but they mean opposite things.** Draft is "not ready yet." Archived is "was ready, isn't anymore." Both are invisible to readers and to your AI agent — there's no separate publish step for the agent to catch up on, and no lag between what a customer sees and what the agent can cite. The moment you archive, that content stops being answerable.
</Warning>

## Authorship

Every article belongs to a `User` — an agent on your team — and that field is required, not decorative. You can't save an article with no author, and reassigning one later is an explicit edit, not a side effect of someone else touching the content.

## SEO fields

Separate from the content itself, an article carries a small properties panel backed by a single `meta`
field: `meta.title`, `meta.description`, and `meta.tags` — one JSON column, not three separate database
columns. These feed the page's title and description for search engines and link previews — they don't
change anything a reader sees on the page itself.

## Ordering and search

Articles carry a position for manual ordering within a category, and can be reordered as a batch. Outside of a specific category view, the default list order is most-recently-updated first.

Search covers title, description and content together, weighted so a match in the title ranks above the same match buried in the body — and long articles don't win just by repeating a term more often.

## Next

<CardGroup cols={2}>
  <Card title="Categories and structure" icon="folder-tree" href="/help-center/categories">
    Where an article's locale and position come from.
  </Card>

  <Card title="Locales and translations" icon="languages" href="/help-center/locales">
    Turning one article into several language versions.
  </Card>

  <Card title="AI agents" icon="bot" href="/agents">
    Pointing an agent at what you just published.
  </Card>

  <Card title="Inserting articles into replies" icon="book-marked" href="/inbox/insert-article">
    Human agents using the same content in the inbox.
  </Card>
</CardGroup>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.