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

# Content lifecycle

> Read, import, review, update, preview, and deploy article content.

## Recommended external-agent path

```bash theme={null}
aeo agent context
aeo strategy show
aeo visibility show
aeo metrics overview
```

Write the article in your own environment. Then import:

```bash theme={null}
aeo content import \
  --title "The runner's guide to no-white-cast sunscreen sticks" \
  --body-file ./draft.md
```

`content import` does not accept `--status`; a full imported draft is created in review state.

Review:

```bash theme={null}
aeo content review <content_id>
```

Apply edits:

```bash theme={null}
aeo content update <content_id> --body-file ./draft.revised.md
```

Preview:

```bash theme={null}
aeo content preview <content_id>
```

`content preview` creates or reuses a public, unauthenticated preview URL. Avoid pasting private preview URLs into public logs, tickets, or chat transcripts.

Deploy after explicit user approval:

```bash theme={null}
aeo content deploy <content_id>
```

Deploy requires `approved` status:

```bash theme={null}
aeo content update <content_id> --status approved
aeo content deploy <content_id>
```

## Server-side generation

Use this only when the user asks Aeolo to generate the article:

```bash theme={null}
aeo content generate --prompt "best sunscreen stick for runners"
aeo content jobs
```

Server-side generation creates a background writing job and consumes credits. The current CLI does not support `--wait` for content generation; use `aeo content jobs`, then `aeo content list` or `aeo content get <content_id>` after completion. For coding agents, direct writing plus `content import` is usually better because the agent can use its own local drafting loop.

## Updating existing content

Use `content update` for concrete revisions only:

```bash theme={null}
aeo content update <content_id> --title "New title"
aeo content update <content_id> --status approved
aeo content update <content_id> --body-file ./article.md
```

Do not rewrite user-owned published content without approval.