Workflow 16 feature docs

16/umbraco-workflow/SUMMARY.md

@@ -38,6 +38,14 @@
 
 * [Advanced Search dashboard](advanced-search/advanced-search-dashboard.md)
 
+## Alternate Versions
+
+* [Alternate Versions](alternate-versions/alternate-versions.md)
+
+## Release Sets
+
+* [Release Sets](release-sets/release-sets.md)
+
 ## Data Generator
 
 * [Data Generator](data-generator/data-generator.md)

16/umbraco-workflow/alternate-versions/alternate-versions.md

@@ -0,0 +1,46 @@
+---
+description: >-
+  Create additional draft versions of documents without impacting the 'main' draft version.
+---
+
+# Alternate Versions
+
+{% hint style="info" %}
+This feature requires a license. Learn more about [Workflow's licensing model](https://umbraco.com/products/umbraco-workflow).
+{% endhint %}
+
+Alternate Versions enables the creation of additional draft versions of documents. These can be created and updated without impacting the editing or publishing of the 'main' draft version.
+
+Versions are managed from the **Versions** workspace view on a document and inherit workflow permissions from the host document. Permissions to create, update, promote, and delete versions can be set per User Group.
+
+## Working with Alternate Versions
+
+- Ensure the User Group permissions are set to allow appropriate access.
+![Alternate Version permissions](images/alternate-version-permissions.png)
+- Navigate to the **Versions** Workspace View on a content item.
+![Versions Workspace View](images/versions-workspace-view.png)
+- Click the `Create` button to open a workspace modal containing a copy of the current draft.
+![Version workspace](images/version-workspace-editor.png)
+- Update and save the new version.
+- The new version appears in the collection view.
+![Versions collection](images/versions-collection.png)
+
+Editors can create multiple versions of a document and update these independently.
+
+An alternate version is not published directly. Instead, it is set as the current draft version.
+
+If the host document has an approval workflow configured, versions must be approved via the same workflow before being set to current.
+
+If the host has no workflow configured, versions can be set to current by any user with the `Promote` permission.
+
+When a version is promoted to be the current draft, it can be further edited before being published. Publishing can be via workflow approval or directly, depending on configuration and permissions.
+
+## Variant versions
+
+Alternate versions can vary by culture or segment. 
+
+To create a variant version:
+- Select the desired variant using the document variant selector.
+- Create a new version as outlined above.
+
+The collection in the workspace view will show only versions matching the current document variant.

16/umbraco-workflow/release-sets/release-sets.md

@@ -0,0 +1,66 @@
+---
+description: >-
+    Create collections of content to publish according to multi-stage scheduling rules.
+---
+
+# Release Sets
+
+{% hint style="info" %}
+This feature requires a license. Learn more about [Workflow's licensing model](https://umbraco.com/products/umbraco-workflow).
+{% endhint %}
+
+Release Sets are collections of [Alternate Versions](../alternate-versions/alternate-versions.md), where each version can be scheduled independently. Release Sets provides a holistic overview of scheduled content and enables building and managing content schedules to drive digital campaigns.
+
+Release Sets is currently (v16.0.0) available behind a feature flag. To enable the feature, add the following to the `appsettings.json` file:
+
+```json
+"Umbraco": {
+    "Workflow": {
+        ... // other settings
+        "FeatureFlags": ["ReleaseSets"]
+    }
+}
+```
+
+## Working with Release Sets
+
+-   Ensure the User Group permissions are set to allow appropriate access.
+    ![Release Set permissions](images/release-set-permissions.png)
+-   Navigate to the **Release Sets** dashboard in the **Content** section.
+    ![Release Set dashboard view](images/release-sets-dashboard.png)
+-   Click the `Create` button to open a workspace modal to create a new set.
+    ![Version workspace](images/release-set-workspace-editor.png)
+
+A Release Set is comprised of document versions and (optionally) tasks. Tasks are like to-dos that should be tracked alongside the Release Set, but are not necessarily CMS activities.
+
+For example, a task might be to finalize digital advertising. It is not a CMS activity, but it is a requirement that must be met before publishing the Release Set.
+
+### Adding documents
+
+-   Click the **Add document** button.
+-   Select the document node from the picker.
+-   Add or create a new version of the selected document in the versions editor.
+![Version editor](images/versions-editor.png)
+-   Adding an existing version opens the version picker. Creating a new version opens the [Alternate Version](../alternate-versions/alternate-versions.md) workspace editor.
+![Version picker](images/version-picker.png)
+- After selecting or creating a version, it is displayed in the version editor.
+![Version editor](images/version-editor-2.png)
+- The selected version can then be scheduled.
+![Version scheduling](images/version-scheduling.png)
+- Multiple versions of the same document can be added and scheduled in sequence.
+![Multiple selected versions](images/version-editor-3.png)
+- After submitting the modal, the updated versions are displayed in the overlay. The documents list shows the selected documents, while the calendar shows the Release Set and its components.
+![Release Set overview](images/release-set-overview.png)
+- Selecting a day in the calendar displays the scheduled content changes for that date.
+![Calendar day](images/calendar-day.png)
+- The `Add` button in the calendar day dialog allows adding items to the Release Set, similar to the `Add document` button in the main overview.
+
+### Publishing a Release Set
+
+A Release Set can be published immediately or scheduled for future publication. To publish a Set, all assigned versions and tasks must be either `Ready to publish` (versions) or `Complete` (tasks). If all components in the Set are in the required status, it can be published by a user with the appropriate permission.
+
+Publishing content within the Release Set is managed by a recurring hosted service, similar to scheduled content publishing.
+
+As publishing progresses, each document version is promoted to be the current backoffice draft, and then published as normal. A version of the original backoffice draft is preserved as an Alternate Version and can be republished or edited in the future.
+
+When a Release Set has no further changes to publish, the status is updated to `Complete`. The Set can then be deleted, or updated and republished. Content published within the Set is preserved and can be further edited or included in a new Release Set.