GITBOOK-87: No subject

Author: eshanrnh

umbraco-cloud/SUMMARY.md

@@ -14,6 +14,8 @@
   * [Sustainability Dashboard](getting-started/the-umbraco-cloud-portal/sustainability-dashboard.md)
 * [Project Overview](getting-started/project-overview.md)
 * [Environments](getting-started/environments.md)
+* [Flexible Environments (beta)](getting-started/flexible-environments/README.md)
+  * [Docs Strategy incl. notes](getting-started/flexible-environments/docs-strategy-incl.-notes.md)
 * [Baselines](getting-started/baselines/README.md)
   * [Baseline Merge Conflicts](getting-started/baselines/baseline-merge-conflicts.md)
   * [Break Reference between Baseline and Child Project](getting-started/baselines/break-baseline.md)

umbraco-cloud/getting-started/flexible-environments/README.md

@@ -0,0 +1,51 @@
+---
+description: >-
+  Use flexible environments to create a separate workflow along side the
+  left-to-right deployment approach in Umbraco Cloud.
+---
+
+# Flexible Environments (beta)
+
+{% hint style="warning" %}
+Beta feature: Some features might not be fully available.
+{% endhint %}
+
+Flexible Environments allow users to create and manage an unlimited number of environments. This enhancement provides greater flexibility in orchestrating both code and content workflows, empowering developers and content editors to work in a way that best suits their needs.
+
+{% hint style="info" %}
+Current limitations
+
+* Only one flexible environment is available.
+* Flexible environments are only available to Projects paid with Invoices or Credits.
+* CI/CD Pipelines are not supported.
+{% endhint %}
+
+With Flexible Environments, teams can create as many environments as needed, allowing for more efficient and tailored workflows.
+
+This feature enables:
+
+* **Parallel development and testing**: Developers can create isolated environments for different features, bug fixes, or client-specific work without impacting the main development branch.
+* **Custom workflow orchestration**: Teams can define custom flows of code and content deployment rather than being restricted to a linear left-to-right approach.
+* **Easier hotfixes and feature releases**: Urgent fixes can be deployed directly without being blocked by unfinished work in other environments.
+
+Improved Content Management: Content editors can create, test, and validate content changes without depending on the Development environment.
+
+***
+
+## On this page:
+
+### Key concepts (??)
+
+## Plan/Availability
+
+This should be added on Umbraco.com, and not be part of the documentation. We can always link to Umbraco.com.
+
+We should at least not be adding information about pricing - this is not relevant for documentation.
+
+## How to deploy between your flexible environment and the mainline environment
+
+This is a guide and should contain information about both directions.
+
+## Creating a new mainline/flexible environment
+
+These should eventually replace the other articles we have about creating environments.

umbraco-cloud/getting-started/flexible-environments/docs-strategy-incl.-notes.md

@@ -0,0 +1,41 @@
+# Docs Strategy incl. notes
+
+## Docs strategy
+
+### Stage 1: Preparation for Public beta (April 11th)
+
+* [ ] Write a new article explaining the concept and how it works, including limitations.
+
+### Stage 2: Public beta starts
+
+* [ ] Publish new Flexible environments article
+* [ ] Consider whether the article should be _hidden_.
+
+### Stage 3: Preparations for the official launch (TBD)
+
+* [ ] All references to Dev, Stage, and Live environments are replaced.
+* [ ] All articles that mention environments and deployments are revised and rewritten if necessary.
+* [ ] Content from the Flexible Environments (beta) articles is split into:
+  * [ ] Feature article containing information and high-overview.
+  * [ ] Guide(s) containing steps and how to use the new feature.
+
+### State 4: Official launch of the feature
+
+* [ ] Publish the changes made in Stage 3.
+
+## List of articles that need to be changed/updated/removed:
+
+| Article                                                                 | Action          |
+| ----------------------------------------------------------------------- | --------------- |
+| [environments.md](../environments.md "mention")                         | Rewrite/Replace |
+| [manage-environments.md](../../set-up/manage-environments.md "mention") | Rewrite         |
+| [cloud-to-cloud.md](../../deployment/cloud-to-cloud.md "mention")       | Rewrite         |
+| [deployment](../../deployment/ "mention")                               | Rewrite         |
+| [project-overview.md](../project-overview.md "mention")                 | Rewrite         |
+| [hotfixes](../../deployment/hotfixes/ "mention")                        | Remove/Rewrite  |
+
+This list does not include all articles that reference environments. This list can be found [here](https://docs.google.com/spreadsheets/d/14pMRjz2QGPU8o5C1iHbha2DtM9tUdxEq/edit?usp=sharing\&ouid=111948135078114796259\&rtpof=true\&sd=true).
+
+## Troubleshooting
+
+If we can avoid it, let's not for a NEW feature, publish docs that include a troubleshooting section. This sends the wrong message.