Skip to content

docs: published view read-only and Edit button for versioned items #616

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
alvarosabu wants to merge 1 commit into
base: draft-publishing-workflow
Choose a base branch
from
+12 −1
Open

docs: published view read-only and Edit button for versioned items #616

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 12 additions & 1 deletion content/guides/02.content/6.content-versioning.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -27,6 +27,17 @@ The version field is a dynamic variable can be added to the live preview URL so

Navigate to **Settings** > **Data Model**, select the collection that you want to enable content versioning for, and scroll down to the content versioning section. Toggle "Enable Versions" and save your data model.

## Editing Versioned Items

When content versioning is enabled for a collection, the published view is **read-only**. Fields are disabled and no Save button is shown. This enforces a draft-first workflow — all edits go through a version before reaching the published item.

To start editing, click the **Edit** button in the item header (or press `⌘E` on Mac / `Ctrl+E` on Windows). Directus automatically switches you to the draft version, where you can make and save changes freely.

::callout{icon="material-symbols:info-outline"}
**Why read-only?**
Preventing direct edits to the published item ensures changes go through the versioning workflow. This keeps your published content stable and gives your team a review step before changes go live.
::

## Working with the Draft Version

When content versioning is enabled for a collection, a global draft version is automatically available for all items. This reserved version provides a safe workspace for preparing changes before publishing to your live content.
Expand Down Expand Up @@ -97,7 +108,7 @@ All new versions originate from the published item. This implies that the publis

![Editing a version](/img/versioning_update.png)

Open the item in the newly created version, and make the desired edits to the item's content.
Open the item and switch to the version you want to edit using the version dropdown. The published view is read-only — you must be in a version context (draft or any custom version) to make changes.

Upon saving the changes, you'll notice that the main item remains unaffected, while the changes are reflected only in the modified version.

Expand Down