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

# Create an Article

> Turn a Content Opportunity or your own topic into a reviewable Article.

**Content Studio** holds Content Gaps, Planner, Articles, and Published Content. You can use Sira to create an Article from a Content Opportunity or start with a topic of your own. The result still needs editorial review.

## Create and review

<Steps>
  <Step title="Choose the work">
    In **Content Studio → Content Gaps**, open an Opportunity and read its Content Brief. You can also start from your own topic.
  </Step>

  <Step title="Create an Article">
    Use the available creation action. If the Brief is still preparing, wait for it or return later before asking Sira to draft from that evidence.
  </Step>

  <Step title="Review the draft">
    Open **Articles**. Read the full Article before opening the publishing dialog. Check claims, examples, links, Brand voice, and whether it answers the intended reader question. Ask Sira for a specific revision or edit directly.
  </Step>

  <Step title="Choose delivery">
    Open the publishing dialog and select the intended connected destination. The **Publish** action can make an Article live. WordPress also offers **Save as WordPress draft** for review in WordPress before it goes live. Review the destination and mode before confirming.
  </Step>

  <Step title="Verify the result">
    Check the publishing result and, when live, the Published URL. Use **Published Content** to review confirmed live work.
  </Step>
</Steps>

## Editorial checklist

* Confirm factual claims and current product details against trusted sources.
* Check that the Article fits the selected Market and intended audience. Verify any translated or localized wording with a reviewer who knows that audience.
* Check the destination and publication mode before pressing **Publish**.
* Make sure the title, links, images, and formatting work in the destination.
* Review generated metadata in the destination; do not assume every field or markup type is supplied automatically.
* Ask the person who owns publication to approve the Article before using a live **Publish** action. For a WordPress review queue, use **Save as WordPress draft** and finish approval in WordPress.
* If someone publishes outside a connected workflow, confirm the live URL in Content Studio where that option is offered.

## What to expect afterward

A live Article may be available for future AI responses, but a later mention or Citation is not guaranteed. Compare later Analyses and inspect the actual responses rather than promising a fixed time to improvement.

<CardGroup cols={2}>
  <Card title="Publish a blog post" icon="pencil" href="/how-to/publish-a-blog-post">
    Walk through the full review and delivery flow.
  </Card>

  <Card title="Content opportunities" icon="lightbulb" href="/features/content-gaps">
    Select a gap using its evidence and Brief.
  </Card>
</CardGroup>


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