> ## 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.

# Resume and update an Article

> Find your Article, verify a saved edit, and choose the right way to update or record its live page.

Use this playbook when returning to a draft, changing published content, or recording an Article you published outside Videntic.

## Find the Article and make one change

1. Open the correct Project, then **Content Studio → Articles**, and select the Article by title. Read its current content and publication status before editing.
2. Make a focused edit in the Article. To ask Sira for help, open Sira beside the Article and state the passage, audience and constraint: “Rewrite this introduction for first-time buyers. Keep the product facts and source links.” Review the proposed change in context.
3. Wait for the save to finish, then reopen the Article and check the actual passage. A Sira reply saying the work is done is not proof that the saved text changed.

An automatically generated Article may have no earlier Sira Conversation. You can start from the open Article without finding an old chat. If you need an earlier conversation you started yourself, look in Sira's conversation history in the same Project; not every Article has a conversation to reopen.

## Choose what happens to the live page

### The Article has not been published

Keep it as a draft until you have reviewed the claims, sources, images and links. Follow [Review publishing](https://docs.videntic.com/playbooks/content-studio/publish.md) when it is ready.

### Videntic is linked to its CMS item

Saving the Article does not by itself update the live post. In the Article editor, review **Update live post** before confirming the update, then open the public URL and check the changed passage.

An Article sent with **Save as WordPress draft** already has a CMS link, even if you later publish it in WordPress. **Mark as published** is not available for CMS-linked Articles. Use the CMS publishing or update flow; if Videntic and the CMS disagree about the status, inspect both and use [publication recovery](https://docs.videntic.com/troubleshooting/publishing.md) rather than duplicating the page to fix a label.

### You published it yourself, without a CMS link

Open the live page and confirm it is public. In the Article's **More actions**, choose **Mark as published** and enter the page address in **Live URL (optional)**. Although the field is optional, supplying the URL makes the intended page explicit. Confirm only after the page is actually live: this action records publication and does not upload content.

If the action is unavailable, ask a Workspace Admin to check your Content Studio permissions. It requires publishing-level access, not just permission to edit a draft.

Later edits saved in Videntic do not update a manually published page. Copy the approved version to your site yourself, then check the live URL. Use **Published content** to review the page after the next site scan; citations may still be absent.

## If your edit did not save

Keep a copy of your intended change before reloading. Reopen the Article and compare the passage. If it is still unchanged, stop repeating the same request and email [info@videntic.com](mailto:info@videntic.com) with the Project, Article title, approximate time, any error and the change you expected. Do not publish the old text while waiting for the edit to appear.

> [!NOTE]
>
> Deleting an Article from Videntic does not remove its live page. It stops tracking the Article. Do not use deletion as a way to unpublish content.

## Expected result

The saved Article contains the intended edit. If you updated the live page, you checked it separately. If you published manually, its publication record identifies the live page without implying that future edits sync automatically.


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