strapi · Boegie19 · Sep 26, 2024 · Sep 27, 2024 · Sep 27, 2024 · Sep 27, 2024
@@ -56,4 +56,4 @@ jobs:
           algolia-app-id: ${{ secrets.ALGOLIA_APP_ID }}
           algolia-api-key: ${{ secrets.ALGOLIA_API_KEY }}
           site-url: 'https://docs.strapi.io'
-          crawler-name: 'strapiDocsNext'
+          crawler-name: 'v5-docs'
@@ -0,0 +1 @@
+.idea/
@@ -45,6 +45,8 @@ The Strapi Documentation team has created a complete style guide for you to make
 
 💁 While writing, please consider the [12 Rules of Technical Writing](https://handbook.strapi.io/user-success-manual/12-rules-of-technical-writing) that the Strapi Documentation team will use to assess the quality and consistency of the contribution. 😊
 
+⚠️ **Important: Please disable any linter or automatic formatting tool(s)** before saving and submitting your files. Not doing so could, at best, add unnecessary formatting changes to the submitted PR or, at worst, prevent Docusaurus from properly rendering some pages.
+
 ### Working locally: Set up the project
 
 To set up the Docusaurus project on your machine, perform the following steps from a terminal instance:
@@ -94,7 +96,7 @@ To submit your contribution for review:
 **⚠️ Important: Add the `flag: merge pending release` if the Strapi Documentation team should wait before merging the pull request.** Approved pull requests are usually merged immediately into the `main` branch, automatically triggering a deployment on docs.strapi.io. Please use the `flag: merge pending release` label if the pull request content should only be released publicly in sync with a product release (e.g., if you submit a pull request to document a contribution to the `strapi/strapi` repository).
 
 
-That’s it! 🥳 Once the pull request is [reviewed and approved](#review-and-management-of-pull-requests), the Strapi Documentation team will merge it, and the content will be live on [docs.strapi.io](http://docs.strapi.io) a few minutes later. 🚀
+That’s it! 🥳 Once the pull request is [reviewed and approved](#review-and-management-of-pull-requests), the Strapi Documentation team will merge it, and the content will be live on [docs.strapi.io](http://docs.strapi.io) a few minutes later. 🚀 Please note that the title of your PR might be rewritten to increase clarity for inclusion in the [release notes](docs.strapi.io/release-notes).
 
 
 ## Review and management of pull requests

@@ -1,10 +1,6 @@
 Copyright (c) 2015-present Strapi Solutions SAS
 
-Portions of the Strapi software are licensed as follows:
-
-* All software that resides under an "ee/" directory (the “EE Software”), if that directory exists, is licensed under the license defined in "ee/LICENSE".
-
-* All software outside of the above-mentioned directories or restrictions above is available under the "MIT Expat" license as set forth below.
+* All software is available under the "MIT Expat" license as set forth below.
 
 MIT Expat License
 

@@ -27,7 +27,7 @@ The main official Strapi documentation website is hosted at [docs.strapi.io](htt
 Additional official Strapi documentation websites cover different content:
 
 - Documentation for the older version 4 of Strapi is hosted at [docs-v4.strapi.io](https://docs-v4.strapi.io) and featured in the `v4` branch. This branch is not actively maintained by the Strapi Documentation team, but community contributions are most welcome!
-- Upcoming and/or experimental documentation is hosted at [docs-next.strapi.io](https://docs-next.strapi.io). Starting autumn/winter 2024, this website will include an all-new documentation — more info soon!
+- Upcoming, experimental documentation is hosted at [docs-next.strapi.io](https://docs-next.strapi.io). Starting autumn/winter 2024, this website will include an all-new documentation — more info soon!
 - Documentation for the older, unsupported version 3 of Strapi is hosted at [docs-v3.strapi.io](https://docs-v3.strapi.io).
 - Documentation for contributors, which include more in-depth and experimental content for developers who actively maintain and contribute to Strapi, is hosted at [contributor.strapi.io](https://contributor.strapi.io). This experimental documentation is maintained by Strapi engineers and any issue should be reported to the [`strapi/strapi`](https://github.com/strapi/strapi/issues/new/choose) repository.
 - Documentation for the Strapi Design System is hosted at [design-system.strapi.io](https://design-system.strapi.io/) and maintained by Strapi front-end engineers in its [dedicated repository](https://github.com/strapi/design-system/).

@@ -46,7 +46,8 @@ The *Payment method* section of the ![Billing icon](/img/assets/icons/CreditCard
 3. Click on the **Save** button.
 
 :::tip
-The first credit card to be added as payment method for the account will by default be the primary one. It is however possible to define another credit card as primary by clicking on the ![Menu icon](/img/assets/icons/more.svg) icon, then **Switch as primary**.
+- The first credit card to be added as payment method will be by default the primary card. You can change the role by clicking on the ![Menu icon](/img/assets/icons/more.svg) icon, then **Set as primary** on another card.
+- Be aware that you also have the possibility to use a dedicated card at projects-level. It will allow you to use different cards for different projects (see [Project Settings > Billing & Usage](/cloud/projects/settings#billing--usage)).
 :::
 
 ### Deleting a credit card

@@ -30,9 +30,12 @@ While it's possible to use an external database with Strapi Cloud, you should do
 - Strapi can't provide security or support with external databases used with Strapi Cloud.
 :::
 
-
 ## Configuration
 
+:::caution
+To ensure a smooth deployment, it is recommended to not change the names of the environment variables.
+:::
+
 The project `./config/database.js` or `./config/database.ts` file must match the configuration found in the [environment variables in database configurations](https://docs.strapi.io/dev-docs/configurations/database#environment-variables-in-database-configurations) section.
 
 Before pushing changes, add environment variables to the Strapi Cloud project:
@@ -54,10 +57,6 @@ Before pushing changes, add environment variables to the Strapi Cloud project:
 
 4.  Click **Save**.
 
-:::caution
-To ensure a smooth deployment, it is recommended to not change the names of the environment variables.
-:::
-
 ## Deployment
 
 To deploy the project and utilize the external database, push the changes from earlier. This will trigger a rebuild and new deployment of the Strapi Cloud project.

@@ -42,7 +42,11 @@ Using either `npm` or `yarn`, install the provider plugin in your local Strapi p
 
 ### Configure the Provider
 
-In your Strapi project, create a `./config/env/production/plugins.js` or `./config/env/production/plugins.ts` file with the following content:
+:::caution
+The file structure must match the below path **exactly**, or the configuration will not be applied to Strapi Cloud.
+:::
+
+To configure a 3rd-party email provider in your Strapi project, create or edit the plugins configuration file for your production environment `./config/env/production/plugins.js|ts` by adding upload configuration options as follows:
 
 <Tabs groupId="js-ts">
 <TabItem value="js" label="JavaScript">
@@ -84,10 +88,6 @@ export default ({ env }) => ({
 
 </Tabs>
 
-:::caution
-The file structure must match the above path exactly, or the configuration will not be applied to Strapi Cloud.
-:::
-
 Each provider will have different configuration settings available. Review the respective entry for that provider in the [Marketplace](https://market.strapi.io/providers).
 
 **Example:**

@@ -44,6 +44,10 @@ Using either `npm` or `yarn`, install the provider plugin in your local Strapi p
 
 ### Configure the Provider
 
+:::caution
+The file structure must match the below path **exactly**, or the configuration will not be applied to Strapi Cloud.
+:::
+
 To configure a 3rd-party upload provider in your Strapi project, create or edit the plugins configuration file for your production environment `./config/env/production/plugins.js|ts` by adding upload configuration options as follows:
 
 <Tabs groupId="js-ts">
@@ -85,10 +89,6 @@ upload: {
 </TabItem>
 </Tabs>
 
-:::caution
-The file structure must match the above path exactly, or the configuration will not be applied to Strapi Cloud.
-:::
-
 Each provider will have different configuration settings available. Review the respective entry for that provider in the [Marketplace](https://market.strapi.io/providers).
 
 **Example:**

@@ -9,7 +9,7 @@ tags:
 pagination_next: cloud/advanced/database
 ---
 
-# Command Line Interface (CLI) <NewBadge />
+# Command Line Interface (CLI) <UpdatedBadge />
 
 Strapi Cloud comes with a Command Line Interface (CLI) which allows you to log in and out, and to deploy a local project without it having to be hosted on a remote git repository. The CLI works with both the `yarn` and `npm` package managers.
 
@@ -41,34 +41,44 @@ Deploy a new local project (< 100MB) in Strapi Cloud.
 strapi deploy
 ```
 
-This command must be used after the `login` one. It deploys a local Strapi project on Strapi Cloud, without having to host it on a remote git repository beforehand. The terminal will inform you when the project is successfully deployed on Strapi Cloud.
+This command must be used after the `login` one. It deploys a local Strapi project on Strapi Cloud, without having to host it on a remote git repository beforehand.
 
-Once the project is first deployed on Strapi Cloud with the CLI, the `deploy` command can be reused to trigger a new deployment of the same project.
-
-:::caution
-The `deploy` command can only be used by new users who have never created a Strapi Cloud project, and for which the free trial is still available. Once a project is deployed with the CLI, it isn't possible to deploy another project on the same Strapi Cloud account with the CLI.
+:::note
+If you have any free trial available, the deploy command will create automatically a new project on Strapi Cloud, unless you previously link your local project to an existing project by using the `strapi link` command.
 :::
 
+When you use this command, you’ll be asked to select a target environment. To skip this prompt, you can either:
+- Use the `--env` flag (e.g., `strapi deploy --env <environment-name>`)
+- Set a default environment with `strapi cloud environment link` [command](#cloud-environment-link), so deployments automatically go to that environment.
+
+The terminal will inform you when the project is successfully deployed on Strapi Cloud.
+
+Once the project is first deployed on Strapi Cloud with the CLI, the `deploy` command can be reused to trigger a new deployment of the same project.
+
 :::note
 Once you deployed your project, if you visit the Strapi Cloud dashboard, you may see some limitations as well as impacts due to creating a Strapi Cloud project that is not in a remote repository and which was deployed with the CLI.
 
 - Some areas in the dashboard that are usually reserved to display information about the git provider will be blank.
 - Some buttons, such as the **Trigger deploy** button, will be greyed out and unclickable since, unless you have [connected a git repository to your Strapi Cloud project](/cloud/getting-started/deployment-cli#automatically-deploying-subsequent-changes).
 :::
 
-## strapi link <NewBadge />
+## strapi link
 
 **Alias:** `strapi cloud:link`
 
 Links project in current folder to an existing project in Strapi Cloud.
 
+:::note
+Linking a project to Strapi Cloud doesn't limit it to Strapi Cloud alone; you can still deploy and manage it in your own self-hosted environment as needed.
+:::
+
 ```bash
 strapi link
 ```
 
 This command connects your local project in the current directory with an existing project on your Strapi Cloud account. You will be prompted to select the project you wish to link from a list of available projects hosted on Strapi Cloud.
 
-## strapi projects <NewBadge />
+## strapi projects
 
 **Alias:** `strapi cloud:projects`
 
@@ -78,7 +88,34 @@ Lists all Strapi Cloud projects associated with your account.
 strapi projects
 ```
 
-This command retrieves and displays a list of all projects hosted on your Strapi Cloud account.
+
+```bash
+strapi link
+```
+
+This command connects your local project in the current directory with an existing project on your Strapi Cloud account. You will be prompted to select the project you wish to link from a list of available projects hosted on Strapi Cloud.
+
+## strapi cloud environments <NewBadge /> {#cloud-environments}
+
+**Alias:** `strapi cloud environment list`
+
+Lists all environments associated with your Strapi Cloud Project.
+
+```bash
+strapi cloud environments
+```
+
+This command retrieves and displays a list of all environments belonging to your Strapi Cloud project.
+
+## strapi cloud environment link <NewBadge /> {#cloud-environment-link}
+
+Links your local project to a specific environment in your Strapi Cloud project.
+
+```bash
+strapi cloud environment link
+```
+
+This command shows a list of all environments in your Strapi Cloud project and lets you choose one. The selected environment will then be the default for direct deployments.
 
 ## strapi logout
 

@@ -58,8 +58,8 @@ Before you can deploy your Strapi application on Strapi Cloud using the Cloud da
     <ThemedImage
     alt="Strapi Cloud project creation, step 1"
     sources={{
-        light: '/img/assets/cloud/project-creation-1.png',
-        dark: '/img/assets/cloud/project-creation-1_DARK.png',
+        light: '/img/assets/cloud/project-creation-1.1.png',
+        dark: '/img/assets/cloud/project-creation-1.1_DARK.png',
     }}
     />
 
@@ -144,10 +144,10 @@ Before you can deploy your Strapi application on Strapi Cloud using the Cloud da
 
     | Setting name | Instructions                                                                                            |
     |--------------|---------------------------------------------------------------------------------------------------------|
-    | Display name | Write the name of your Strapi app, this is fetched from the repository name but can be edited. It is automatically converted to slug format (`my-strapi-app`). |
+    | Display name | Write the name of your Strapi app, this is fetched from the repository name but can be edited.<br /> It is automatically converted to slug format (`my-strapi-app`). |
     | Git branch   | Choose from the drop-down the default branch to use for this deployment. This uses the default branch of the repository. |
     | Deploy on push | Check the box to automatically deploy the latest changes from the selected branch. When disabled, you will need to manually deploy the latest changes. |
-    | Region       | Choose the geographic location of the servers where your Strapi application is hosted. Selected region can either be New York in North America (default) or Amsterdam in Europe. |
+    | Region       | Choose the geographic location of the servers where your Strapi application is hosted. Selected region can either be New York in North America (default), Amsterdam in Europe, Singapore in Asia or Sydney in Oceania. |
 
     :::note
     The Git branch and "Deploy on push" settings can be modified afterwards through the project's setting, however the project name and hosting region setting can only be chosen during the creation of the project (see [Project Settings](/cloud/projects/settings)).

@@ -19,7 +19,7 @@ Strapi Cloud offers a free 14 days trial for all new accounts, and 3 paid plans:
 
 | Feature | Free Trial | Developer | Pro | Team |
 | --- | --- | --- | --- | --- |
-| **Seats** | 10 (up to 10 extra) | 1 (up to 3 extra) | 5 (up to 20 extra) | 10 (up to 50 extra) |
+| **Seats** | 10 | 1 (up to 2 extra) | 5 (up to 15 extra) | 10 (up to 40 extra) |
 | **Database Entries**  | 1,000 | 1,000 | 100,000 | 1,000,000 |
 | **Assets Storage** | 5GB | 15GB | 150GB | 500GB |
 | **Assets Bandwidth** | 50GB | 50GB per month | 500GB per month | 1,000GB per month |

@@ -50,17 +50,20 @@ From the *Projects* page, click on any project card to access is dashboard. It d
 />
 
 From the dashboard's header of a chosen project, you can:
-- use the **Share** button to invite users to collaborate on the project (see [Collaboration](/cloud/projects/collaboration)) and see the icons of those who have already been invited <ScreenshotNumberReference number="1" />,
-- use the ![Settings icon](/img/assets/icons/settings.svg) **Settings** button to access the settings of the project and its existing environments <ScreenshotNumberReference number="2" />,
-- choose which environment to visualise for the project <ScreenshotNumberReference number="3" />,
-- trigger a new deployment (see [Deployments management](/cloud/projects/deploys)) and visit your application <ScreenshotNumberReference number="4" />.
+- use the navigation path to navigate between your projects and environments <ScreenshotNumberReference number="1" />,
+- use the **Share** button to invite users to collaborate on the project (see [Collaboration](/cloud/projects/collaboration)) and see the icons of those who have already been invited <ScreenshotNumberReference number="2" />,
+- use the ![Settings icon](/img/assets/icons/settings.svg) **Settings** button to access the settings of the project and its existing environments <ScreenshotNumberReference number="3" />,
+- choose which environment to visualise for the project <ScreenshotNumberReference number="4" />,
+- trigger a new deployment (see [Deployments management](/cloud/projects/deploys)) and visit your application <ScreenshotNumberReference number="5" />.
 
 Your project's dashboard also displays:
-- the *Deployments* and *Runtime logs* tabs, to see the deployments history (more details in [Deploy history and logs](/cloud/projects/deploys-history)) and the runtime logs of the project (see [dedicated documentation page](/cloud/projects/runtime-logs)) <ScreenshotNumberReference number="5" />
-- the project and environment details in a box on the right of the interface <ScreenshotNumberReference number="6" />, including:
+- the *Deployments* and *Runtime logs* tabs, to see the deployments history (more details in [Deploy history and logs](/cloud/projects/deploys-history)) and the runtime logs of the project (see [dedicated documentation page](/cloud/projects/runtime-logs)) <ScreenshotNumberReference number="6" />
+- the project and environment details in a box on the right of the interface <ScreenshotNumberReference number="7" />, including:
+  - a Manage button to be redirected to the environment’s settings,
   - the number of API calls and database entries,
   - the current usage for assets bandwidth and storage,
-  - the name of the branch and a **Manage** button to be redirect to the branch settings (see [Modifying git repository & branch](/cloud/projects/settings#modifying-git-repository--branch)),
+  - the name of the branch,
   - the name of the base directory,
-  - the Strapi version number.
+  - the Strapi version number,
+  - the application url.
 
@@ -9,8 +9,6 @@ tags:
 - Strapi Cloud
 ---
 
-import NotV5 from '/docs/snippets/_not-updated-to-v5.md'
-
 # Runtime logs
 
 From a chosen project's dashboard, the *Runtime logs* tab displays the live logs of the project.