Draft publishing workflow documentation#605
Open
alvarosabu wants to merge 10 commits into
Open
Conversation
Update content versioning terminology and clarify reserved keys in documentation - Changed references from "main" to "published" for consistency across versioning concepts. - Added clarification on reserved version keys and their usage in API queries. - Updated examples and instructions to reflect the new terminology and ensure accurate guidance for users.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Enhance content versioning guide with information on required fields (#599) Added a note clarifying that versions can be saved with empty required fields, deferring validation to allow for partial drafts. Updated the promotion process to include validation error handling for empty fields before finalizing a version.
) * Enhance content versioning guide with information on required fields (#599) Added a note clarifying that versions can be saved with empty required fields, deferring validation to allow for partial drafts. Updated the promotion process to include validation error handling for empty fields before finalizing a version. * Add draft item creation process to content versioning guide
Merged
3 tasks
Update content versioning guide to clarify terminology and processes
…625) Add draft browsing and management features to content versioning guide - Introduced a section on browsing draft versions from the collection page, detailing the functionality of the **Published/Draft** selector. - Explained draft mode behavior, including disabled actions and the ability to batch delete drafts without affecting published items. - Updated the content versioning guide to reflect these new features for improved user experience.
…de (#619) * Update content versioning guide to replace 'promote' terminology with 'publish' for clarity. Adjusted instructions and descriptions to reflect the new terminology and ensure consistency throughout the document. * Rename promote to publish in content versioning (#609) Update content versioning guide to clarify terminology and processes * docs: published view read-only and Edit button for versioned items (#616) Add new edit button on published items docs changes * docs: add collection-level draft browsing for versioned collections (#625) Add draft browsing and management features to content versioning guide - Introduced a section on browsing draft versions from the collection page, detailing the functionality of the **Published/Draft** selector. - Explained draft mode behavior, including disabled actions and the ability to batch delete drafts without affecting published items. - Updated the content versioning guide to reflect these new features for improved user experience.
JamesW1
reviewed
May 17, 2026
| - **Draft** — the global [draft version](/guides/content/content-versioning#working-with-the-draft-version), always available for collections with versioning enabled | ||
|
|
||
| If your website URL contains a version key that doesn't match "main" or "draft" (e.g. from a custom query parameter), it will also appear as a dynamic option in the dropdown. | ||
| If your website URL contains a version key that doesn't match "published", "main", or "draft" (e.g. from a custom query parameter), it will also appear as a dynamic option in the dropdown. |
Contributor
There was a problem hiding this comment.
Is the inclusion of main here again intentional (i.e. for backwards compatibility reasons)?
Contributor
There was a problem hiding this comment.
also @formfcw want to double check this is true beyond global versions (i.e. additional named local versions would appear in the visual studio dropdown)?
Contributor
There was a problem hiding this comment.
main I wouldn’t mention it, since it is deprecated. I think we could have a call-out somewhere that addresses this.
Since this text is about the visual editor, it is true, that local versions will appear in the dropdown.
| ## Browsing Draft Versions | ||
|
|
||
| When [content versioning](/guides/content/content-versioning) is enabled for a collection, a **Published/Draft** selector appears in the collection page header. Use it to switch between viewing published items and their draft versions. | ||
|
|
Contributor
There was a problem hiding this comment.
I feel like an image here showing the selector would be ideal
JamesW1
approved these changes
May 18, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Docs for Draft & Publishing Workflow feat