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

# Articles

> Write long-form articles in brand chat as versioned artifacts with search metadata.

Ask for an article in brand chat and daoco writes it, then saves it as a durable artifact: a title, a URL slug, the markdown body, search metadata, and a version history. It opens in an **Article** panel beside the chat that survives a refresh.

An article is not a social draft. Social drafts are shaped around platforms: one idea, a variant per channel, media, target accounts. An article is one body of markdown with one set of search metadata, so it lives in its own place with its own history.

<Note>
  Saving an article does not publish it. If your site content lives in a
  connected GitHub repository, you can separately ask daoco to propose the
  article as a pull request. You still review and merge that pull request.
</Note>

## Ask for an article

<Steps>
  <Step title="Ask for an article in brand chat">
    "Write an article about X", "write a blog post that beats this page", or
    paste a URL you want to write against.
  </Step>
</Steps>

## The Articles tab

Open **Home**, choose **Website**, and open the **Articles** tab. Every article the brand has is listed there with its title, when it was last updated, its word count, its version, and whether it is a **Draft**, **Published**, or **Archived**.

The first time you open it, the tab offers to bring in what you already have. Enter the page where your articles live, for example `yoursite.com/blog`, and choose **Bring in my existing articles**. daoco reads them and saves each one as an article here. **Draft a blog post** starts a new one instead.

Once the tab has articles, **Draft another** starts the next one. If the last run finished without producing anything, the tab says so and links you to that thread.

## Writing against a real page

Give daoco a URL and it reads the page before it outlines. It crawls the page and uses what is actually there (the real headings, the real length, whether the page has a comparison table or an FAQ, what schema it carries) to decide what your article has to match, where it can go deeper, and what page one is missing.

That is the difference between "write me a long article about email deliverability" and an article built to beat a specific page. Without a URL, daoco writes from your brand context and says so rather than implying research it did not do.

The panel lists the pages daoco reports auditing for the brief, under a heading that says exactly that. It is the writer's own account of what it read, not an independently verified record, and when nothing was reported the panel says so rather than leaving the space blank.

## What gets saved

<CardGroup cols={2}>
  <Card title="Title and slug">
    The headline plus a URL-safe slug, derived from the title unless you name
    one. Collisions inside a brand are resolved automatically.
  </Card>

  <Card title="Body">
    The full article rendered with its headings, lists, links, quotes, and code.
    Copy the original markdown out of the panel with one click.
  </Card>

  <Card title="Search metadata">
    Meta title, meta description, the single target query the article is written
    to win, and any secondary queries the outline genuinely covers.
  </Card>

  <Card title="Version history">
    Every revision appends a version with a one-line summary of what changed.
    Nothing is overwritten.
  </Card>
</CardGroup>

## Revising

Ask for changes in the same thread ("tighten the opening", "add a pricing section", "retarget this at b2b email deliverability") and daoco revises the article in place. Each content change appends a version; the panel shows the history.

Every article appears under **Website > Articles**, drafts included. The list labels imported live pages **Published** and opens their webpages in a new tab. Articles written in daoco stay **Draft**; select one to return to the chat thread where it was written, which is where editing happens.

Metadata-only edits are recorded as such, so "we rewrote it" and "we retitled it" are different entries.

## Archiving and restoring

Articles you no longer want are archived, not deleted. Use **Archive** in the article panel, or ask in chat. Archived articles stay queryable and can be restored from the same button.

## Current limits

* **No direct publishing.** Articles are saved in daoco. daoco can propose a reviewed article as a pull request to a [connected GitHub repository](/connections/mcp/github), but it does not merge the pull request or publish directly to WordPress or Webflow.
* **No keyword data yet.** daoco grounds a brief in the page it crawls, not in search volume or difficulty. This is true even when your workspace has keyword data and Search Console available to the SEO agent; the writing lane does not read them yet. It will tell you the target query is inferred rather than measured, and it will not invent numbers.
* **One article per piece.** Revise the article you have rather than asking for a second one on the same topic; the history is more useful than two drafts.