Skip to content

Commit a2bd3f8

Browse files
authored
Updates for stable release of Releases Scheduling (#2061)
* Updates for stable * Update new release screenshot Wrong size * Hide experimental flags * Fix heading link No badges anymore
1 parent 3468ddf commit a2bd3f8

13 files changed

+19
-19
lines changed

Diff for: docusaurus/docs/dev-docs/configurations/features.md

+4-2
Original file line numberDiff line numberDiff line change
@@ -102,8 +102,10 @@ Developers can use the following APIs to interact with future flags:
102102

103103
## Available future flags
104104

105-
The following future flags are currently available and can be used in the `future` object of the `config/features` configuration file:
105+
There are currently no available future flags. This section will be updated once new experimental features are available for testing.
106+
107+
<!-- The following future flags are currently available and can be used in the `future` object of the `config/features` configuration file:
106108
107109
| Property name | Related feature | Suggested environment variable name |
108110
| ----------------- | -------------------------------------------- | ----------------------------------------- |
109-
| `contentReleasesScheduling` | [Releases Scheduling](/user-docs/releases/managing-a-release#scheduling-a-release-) | `STRAPI_FUTURE_CONTENT_RELEASES_SCHEDULING` |
111+
| `contentReleasesScheduling` | [Releases Scheduling](/user-docs/releases/managing-a-release#scheduling-a-release-) | `STRAPI_FUTURE_CONTENT_RELEASES_SCHEDULING` | -->

Diff for: docusaurus/docs/user-docs/content-manager/adding-content-to-releases.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -43,7 +43,7 @@ To add an entry to a release:
4343

4444
1. In the Releases box in the right sidebar, click the **+ Add to release** button.
4545
2. Select which release to add this entry to.
46-
3. Decide whether the entry will be published or unpublished when the release itself is published, then click **Continue**.
46+
3. Click on the **Publish** or **Unpublish** button depending on whether you want the entry to be published or unpublished when the release itself is published, then click **Continue**.
4747

4848
The Releases box in the right sidebar should show which release(s) the entry is included in.
4949

Diff for: docusaurus/docs/user-docs/releases/creating-a-release.md

+1-2
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,6 @@ description: Instructions to create a release from the admin panel
77

88
The ![Releases icon](/img/assets/icons/releases.svg) [Releases](/user-docs/releases/introduction) page allows creating new releases that will be used to organize entries.
99

10-
<!-- TODO: update screenshot to show scheduling -->
1110
<ThemedImage
1211
alt="Adding a new release"
1312
sources={{
@@ -22,7 +21,7 @@ To create a new release:
2221

2322
1. Click the **+ New Release** button in the upper right corner of the Releases page.
2423
2. Give the release a name.
25-
3. (_optional_) If you want to schedule the release publication instead of publishing the release manually, check the **Schedule release** checkbox and define the date, time, and timezone for publication. Scheduling is currently a <FutureBadge /> feature (see [scheduling a release](/user-docs/releases/managing-a-release#scheduling-a-release-) for details).
24+
3. Define the date, time, and timezone to schedule the release (see [scheduling a release](/user-docs/releases/managing-a-release#scheduling-a-release)). Alternatively, uncheck the **Schedule release** checkbox if you do not want to automatically publish the release and release it manually instead.
2625
4. Click the **Continue** button.
2726

2827
Adding entries to a release must be done from the Content Manager. You can add a single entry to a release while creating or editing the entry [in the edit view](/user-docs/content-manager/adding-content-to-releases).

Diff for: docusaurus/docs/user-docs/releases/introduction.md

+3-3
Original file line numberDiff line numberDiff line change
@@ -10,8 +10,8 @@ Releases enables content managers to organize entries into containers that can p
1010
<ThemedImage
1111
alt="List of Releases"
1212
sources={{
13-
light: '/img/assets/releases/releases-overview2.png',
14-
dark: '/img/assets/releases/releases-overview2_DARK.png',
13+
light: '/img/assets/releases/releases-overview.png',
14+
dark: '/img/assets/releases/releases-overview_DARK.png',
1515
}}
1616
/>
1717

@@ -21,5 +21,5 @@ From the Releases view, it is possible to:
2121

2222
- [create a new release](/user-docs/releases/creating-a-release),
2323
- view pending and done releases,
24-
- view which releases are [scheduled](/user-docs/releases/managing-a-release#scheduling-a-release-), and when they will be published (in the Pending tab) or have been published (in the Done tab),
24+
- view which releases are [scheduled](/user-docs/releases/managing-a-release#scheduling-a-release), and when they will be published (in the Pending tab) or have been published (in the Done tab),
2525
- and click on a release to [manage its content](/user-docs/releases/managing-a-release).

Diff for: docusaurus/docs/user-docs/releases/managing-a-release.md

+10-11
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,6 @@ description: Instructions on how to manage a Release from the admin panel
88

99
Adding entries to a [release](/user-docs/releases/introduction) allow viewing them altogether on a single page.
1010

11-
<!-- TODO: add actual screenshots for both light and dark modes -->
1211
<ThemedImage
1312
alt="Release details"
1413
sources={{
@@ -21,11 +20,11 @@ Adding entries to a [release](/user-docs/releases/introduction) allow viewing th
2120

2221
From a release page, you can:
2322

24-
- edit the name of the release, or delete the release,
25-
<!-- - [adjust the view](#choose-how-entries-are-grouped) to display entries grouped either by locale or by content-type, -->
26-
- decide whether an entry will be published or unpublished with the release,
27-
<!-- - edit a specific entry or [remove](#remove-entries-from-a-release) it from the release, -->
28-
- and publish the release.
23+
- edit the name of the release or delete the release (1)
24+
- manually publish the release (2),
25+
- adjust the view to display entries grouped either by locale, content-type, or action (publish/unpublish) (3),
26+
- decide whether individual items included to the releases will be published or unpublished with the release (4).
27+
- edit a specific entry or remove it from the release (5).
2928

3029
## Editing a release
3130

@@ -36,11 +35,7 @@ You can rename a release. To do so, while on a release page:
3635
3. In the modal, change the name of the release in the _Name_ field.
3736
4. Click **Continue** to save the change.
3837

39-
## Scheduling a release <FutureBadge /><BetaBadge />
40-
41-
:::callout 🚧 Experimental feature
42-
Scheduling a release is an experimental feature and currently requires enabling the proper `contentReleasesScheduling` future flag in your configuration file (see [Developer Docs](/dev-docs/configurations/features) for details).
43-
:::
38+
## Scheduling a release
4439

4540
Releases can be [published manually](#publishing-a-release) or scheduled to be automatically published at a given date and time, with the timezone of your choice.
4641

@@ -75,6 +70,10 @@ A release includes multiple entries. You can set the state of each entry with th
7570
Since publishing an entry with a release means turning a draft entry into a published entry, Releases will not work if [Draft & Publish](/user-docs/content-manager/saving-and-publishing-content) is disabled for the content-type.
7671
:::
7772

73+
## Editing an entry from a release
74+
75+
By clicking on the ![More icon](/img/assets/icons/more.svg) at the end of the line of an entry and select the **Edit entry** button, you will be redirected to this entry in the Content Manager so you can edit it.
76+
7877
## Removing entries from a release
7978

8079
Entries can be removed from a release. To do so, click the ![More icon](/img/assets/icons/more.svg) at the end of the line of an entry and select the **Remove from release** button.
-12.9 KB
Loading
26.2 KB
Loading
-534 Bytes
Loading
-3.13 KB
Loading
58.6 KB
Loading
-259 KB
Binary file not shown.
Binary file not shown.
Loading

0 commit comments

Comments
 (0)