> For the complete documentation index, see [llms.txt](https://docs.varbase.vardot.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.varbase.vardot.com/content-designers/content-management/modify-content.md).

# Modify Content

You will often update content that already exists: fix a typo, add a paragraph, replace an image. This page shows how to find the item, edit it, and use revisions to see or undo changes.

## Finding the Content

### From the Content List

1. Click **CMS** in the **Navigation** sidebar (`/admin/content`).
2. Type part of the title in **Title**, or choose a **Content type**, then click **Filter**.
3. Click **Edit** in the **Operations** column of the item.

<figure><img src="https://410909369-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzBcuWLZ87gvtX5vA2YGD%2Fuploads%2Fgit-blob-fcc22ba123d9e6f0f693ee2824994b698b2a9ddf%2Fcontent-management-modify-01-filter.png?alt=media" alt="The Content list filtered by a title, with the Edit button of the matching blog post highlighted in the Operations column"><figcaption><p>Finding an Item to Edit</p></figcaption></figure>

### From the Site

1. While logged in, open the item on the site.
2. Click **Edit** in the bar at the top of the page.

## Editing

1. Change the fields you need.
2. In **Change to**, choose the state to save in. To change a published item without showing the change yet, choose **Draft**; the published version stays live until you publish again. A published item offers **Draft**, **Published** and **Archived / Unpublished**.
3. Write a **Revision log message** that says what changed, for example "Updated the opening hours".
4. Click **Save**.

<figure><img src="https://410909369-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzBcuWLZ87gvtX5vA2YGD%2Fuploads%2Fgit-blob-f5ec77c2d658db4ca06c213598ddd53bae3254fa%2Fcontent-management-modify-02-change-to.png?alt=media" alt="The edit form sidebar showing Current state Published and the Change to list open with Draft, Published and Archived / Unpublished"><figcaption><p>Saving a Change as a Draft of a Published Item</p></figcaption></figure>

{% hint style="info" %}
While you have an item open, other editors cannot edit it; they see who is editing. Click **Save** or **Unlock** when you finish so the lock is released. See [Content Workflow](https://docs.varbase.vardot.com/content-designers/content-workflow.md#content-locking-and-autosave).

On a new site, every edit form opens with the message "This content is now locked against simultaneous editing." It confirms your own lock, not a problem; you can carry on editing.
{% endhint %}

## Revisions

Each save keeps the previous version. Open the item and click the **Revisions** tab to see the list, with the date, the author and the log message of each.

<figure><img src="https://410909369-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzBcuWLZ87gvtX5vA2YGD%2Fuploads%2Fgit-blob-8df0df8cf44e8b79daa6d6b6210157144b01df06%2Fcontent-management-modify-03-revisions.png?alt=media" alt="The Revisions tab of a blog post listing its revisions with dates, authors and log messages, and the Compare selected revisions button"><figcaption><p>The Revisions Tab</p></figcaption></figure>

### Comparing Two Revisions

1. On the **Revisions** tab, choose the two revisions with the radio buttons.
2. Click **Compare selected revisions**.

Varbase shows the two versions side by side with the changes marked.

### Going Back to an Earlier Revision

1. On the **Revisions** tab, click **Revert** next to the revision you want.
2. Confirm.

Varbase saves a new revision that copies the old one, so nothing is lost.

## Tips

* Keep log messages short and specific; your team reads them when something goes wrong.
* For a large change to a published item, save as **Draft**, ask a colleague to check, then publish.
* If someone else holds the lock on an item, ask them to finish rather than breaking the lock.
