diff --git a/10/umbraco-cms/extending/packages/packages-on-umbraco-cloud.md b/10/umbraco-cms/extending/packages/packages-on-umbraco-cloud.md index 25a1ac83ae4..328e112f049 100644 --- a/10/umbraco-cms/extending/packages/packages-on-umbraco-cloud.md +++ b/10/umbraco-cms/extending/packages/packages-on-umbraco-cloud.md @@ -27,16 +27,16 @@ A [migration](../database.md) is some code that you run as part of a migration p As migration runs are stored in the database of the site it also means that they will run on each environment you trigger them on. The most common way to trigger a migration is to include them in a [composer](../../implementation/composing.md), which will ensure they run on site startup. This means any commands you have in your migration will automatically run when the site starts up. When your package code is pushed to a new environment it will run them from the beginning on that environment as no ID is saved in the database. -This is normally a good thing. However if you generate any Umbraco schema then Umbraco Deploy will automatically create [UDA files](https://docs.umbraco.com/umbraco-cloud/setup/power-tools/generating-uda-files#generate-uda-files-manually) based on that schema, and commit them to source control. This means that when you deploy all your files to the next environment the migration will run again, create duplicates and generate duplicate UDA files, which could end up causing a lot of issues. +This is normally a good thing. However if you generate any Umbraco schema then Umbraco Deploy will automatically create [UDA files](https://docs.umbraco.com/umbraco-cloud/set-up/power-tools/generating-uda-files#generate-uda-files-manually) based on that schema, and commit them to source control. This means that when you deploy all your files to the next environment the migration will run again, create duplicates and generate duplicate UDA files, which could end up causing a lot of issues. You could consider creating Umbraco schema only during a package action, and then running things like creating database tables in migrations. Another good workaround could be to not run the migrations in a composer, but rather create a dashboard for the package where the user can choose which migrations to run themselves. The [Articulate package](https://github.com/Shazwazza/Articulate/blob/master/build/packageManifest.xml#L613) has an example of this. ### Creating files -You may sometimes choose to save data in a file. Could be a separate config file for your package or a [config transform file](https://docs.umbraco.com/umbraco-cloud/setup/config-transforms) to add an app setting to the web.config. If you do this be aware of two things: +You may sometimes choose to save data in a file. Could be a separate config file for your package or a [config transform file](https://docs.umbraco.com/umbraco-cloud/set-up/config-transforms) to add an app setting to the web.config. If you do this be aware of two things: 1. If these files are generated on a Cloud environment they will not be stored in source control, and will be overwritten on next deployment. They need to be installed locally, committed to source control and then pushed up to the Cloud environments. We have an [existing feature request](https://github.com/umbraco/Umbraco.Cloud.Issues/issues/33) on allowing package creators to commit their files directly on Cloud, and it is possible to do so currently but not in a supported way, and it may change suddenly. -2. If you need the content of the files to be different on the different environments you will need to use environment specific [config transforms](https://docs.umbraco.com/umbraco-cloud/setup/config-transforms). +2. If you need the content of the files to be different on the different environments you will need to use environment specific [config transforms](https://docs.umbraco.com/umbraco-cloud/set-up/config-transforms). ## ValueConnectors diff --git a/10/umbraco-cms/tutorials/add-google-authentication.md b/10/umbraco-cms/tutorials/add-google-authentication.md index 724a703260c..09aba4efd37 100644 --- a/10/umbraco-cms/tutorials/add-google-authentication.md +++ b/10/umbraco-cms/tutorials/add-google-authentication.md @@ -89,7 +89,7 @@ The **ClientId** and **ClientSecret** can always be accessed from the **Credenti ## Integrating Google Auth in Visual Studio -Now that you have the Google API set up, open your existing solution in Visual Studio. If you don't know how to clone down a Cloud site, see the [Working locally](https://docs.umbraco.com/umbraco-cloud/setup/working-locally) article. +Now that you have the Google API set up, open your existing solution in Visual Studio. If you don't know how to clone down a Cloud site, see the [Working locally](https://docs.umbraco.com/umbraco-cloud/set-up/working-locally) article. ### Installing a Nuget Package diff --git a/10/umbraco-cms/tutorials/multisite-setup.md b/10/umbraco-cms/tutorials/multisite-setup.md index e95e14cabf2..acdf3188c65 100644 --- a/10/umbraco-cms/tutorials/multisite-setup.md +++ b/10/umbraco-cms/tutorials/multisite-setup.md @@ -9,7 +9,7 @@ description: A guide to multisite setup in Umbraco This tutorial explains how to host multiple sites from one project/installation of Umbraco. For practical reasons, we recommend using [Baselines](https://docs.umbraco.com/umbraco-cloud/getting-started/baselines) on Umbraco Cloud projects. {% hint style="info" %} -When using Baselines on Umbraco Cloud for a multisite solution, you would not need to worry about [Usage](https://docs.umbraco.com/umbraco-cloud/setup/project-settings/usage) limits and could see better performance compared to having multiple websites in one project. +When using Baselines on Umbraco Cloud for a multisite solution, you would not need to worry about [Usage](https://docs.umbraco.com/umbraco-cloud/set-up/project-settings/usage) limits and could see better performance compared to having multiple websites in one project. {% endhint %} If you are planning to create a multilingual site, please take a look at the [Multilanguage Setup](multilanguage-setup.md) tutorial instead. diff --git a/12/umbraco-cms/extending/packages/packages-on-umbraco-cloud.md b/12/umbraco-cms/extending/packages/packages-on-umbraco-cloud.md index e1fc31db4b1..bebddc0ec75 100644 --- a/12/umbraco-cms/extending/packages/packages-on-umbraco-cloud.md +++ b/12/umbraco-cms/extending/packages/packages-on-umbraco-cloud.md @@ -23,16 +23,16 @@ A [migration](../database.md) is some code that you run as part of a migration p As migration runs are stored in the database of the site it also means that they will run on each environment you trigger them on. The most common way to trigger a migration is to include them in a [composer](../../implementation/composing.md), which will ensure they run on site startup. This means any commands you have in your migration will automatically run when the site starts up. When your package code is pushed to a new environment it will run them from the beginning on that environment as no ID is saved in the database. -This is normally a good thing. However if you generate any Umbraco schema then Umbraco Deploy will automatically create [UDA files](https://docs.umbraco.com/umbraco-cloud/setup/power-tools/generating-uda-files) based on that schema, and commit them to source control. This means that when you deploy all your files to the next environment the migration will run again, create duplicates and generate duplicate UDA files, which could end up causing a lot of issues. +This is normally a good thing. However if you generate any Umbraco schema then Umbraco Deploy will automatically create [UDA files](https://docs.umbraco.com/umbraco-cloud/set-up/power-tools/generating-uda-files) based on that schema, and commit them to source control. This means that when you deploy all your files to the next environment the migration will run again, create duplicates and generate duplicate UDA files, which could end up causing a lot of issues. You could consider creating Umbraco schema only during a package action, and then running things like creating database tables in migrations. Another good workaround could be to not run the migrations in a composer, but rather create a dashboard for the package where the user can choose which migrations to run themselves. The [Articulate package](https://github.com/Shazwazza/Articulate/blob/master/build/packageManifest.xml#L613) has an example of this. ### Creating files -You may sometimes choose to save data in a file. Could be a separate config file for your package or a [config transform file](https://docs.umbraco.com/umbraco-cloud/setup/config-transforms) to add an app setting to the web.config. If you do this be aware of two things: +You may sometimes choose to save data in a file. Could be a separate config file for your package or a [config transform file](https://docs.umbraco.com/umbraco-cloud/set-up/config-transforms) to add an app setting to the web.config. If you do this be aware of two things: 1. If these files are generated on a Cloud environment they will not be stored in source control, and will be overwritten on next deployment. They need to be installed locally, committed to source control and then pushed up to the Cloud environments. We have an [existing feature request](../../reference/mapping.md) on allowing package creators to commit their files directly on Cloud, and it is possible to do so currently but not in a supported way, and it may change suddenly. -2. If you need the content of the files to be different on the different environments you will need to use environment specific [config transforms](https://docs.umbraco.com/umbraco-cloud/setup/config-transforms). +2. If you need the content of the files to be different on the different environments you will need to use environment specific [config transforms](https://docs.umbraco.com/umbraco-cloud/set-up/config-transforms). ## ValueConnectors diff --git a/12/umbraco-cms/tutorials/add-google-authentication.md b/12/umbraco-cms/tutorials/add-google-authentication.md index 6ab15fa89bc..c92c6c65b44 100644 --- a/12/umbraco-cms/tutorials/add-google-authentication.md +++ b/12/umbraco-cms/tutorials/add-google-authentication.md @@ -110,7 +110,7 @@ The **ClientId** and **ClientSecret** can always be accessed from the **Credenti Once the Google API is set up it is time to install the Google Auth provider on the Umbraco project. -If you are working with a Cloud project, see the [Working locally](https://docs.umbraco.com/umbraco-cloud/setup/working-locally) article to complete this step. +If you are working with a Cloud project, see the [Working locally](https://docs.umbraco.com/umbraco-cloud/set-up/working-locally) article to complete this step. ### Installing a Nuget Package diff --git a/12/umbraco-cms/tutorials/multisite-setup.md b/12/umbraco-cms/tutorials/multisite-setup.md index 136dbba6e82..95f43e3bedd 100644 --- a/12/umbraco-cms/tutorials/multisite-setup.md +++ b/12/umbraco-cms/tutorials/multisite-setup.md @@ -7,7 +7,7 @@ description: A guide to multisite setup in Umbraco This tutorial explains how to host multiple sites from one project/installation of Umbraco. For practical reasons, we recommend using [Baselines](https://docs.umbraco.com/umbraco-cloud/getting-started/baselines) on Umbraco Cloud projects. {% hint style="info" %} -When using Baselines on Umbraco Cloud for a multisite solution, you would not need to worry about [Usage](https://docs.umbraco.com/umbraco-cloud/setup/project-settings/usage) limits, and could see better performance compared to having multiple websites in one project. +When using Baselines on Umbraco Cloud for a multisite solution, you would not need to worry about [Usage](https://docs.umbraco.com/umbraco-cloud/set-up/project-settings/usage) limits, and could see better performance compared to having multiple websites in one project. {% endhint %} If you are planning to create a multilingual site, please take a look at the [Multilanguage Setup](multilanguage-setup.md) tutorial instead. diff --git a/13/umbraco-cms/extending/packages/packages-on-umbraco-cloud.md b/13/umbraco-cms/extending/packages/packages-on-umbraco-cloud.md index e1fc31db4b1..bebddc0ec75 100644 --- a/13/umbraco-cms/extending/packages/packages-on-umbraco-cloud.md +++ b/13/umbraco-cms/extending/packages/packages-on-umbraco-cloud.md @@ -23,16 +23,16 @@ A [migration](../database.md) is some code that you run as part of a migration p As migration runs are stored in the database of the site it also means that they will run on each environment you trigger them on. The most common way to trigger a migration is to include them in a [composer](../../implementation/composing.md), which will ensure they run on site startup. This means any commands you have in your migration will automatically run when the site starts up. When your package code is pushed to a new environment it will run them from the beginning on that environment as no ID is saved in the database. -This is normally a good thing. However if you generate any Umbraco schema then Umbraco Deploy will automatically create [UDA files](https://docs.umbraco.com/umbraco-cloud/setup/power-tools/generating-uda-files) based on that schema, and commit them to source control. This means that when you deploy all your files to the next environment the migration will run again, create duplicates and generate duplicate UDA files, which could end up causing a lot of issues. +This is normally a good thing. However if you generate any Umbraco schema then Umbraco Deploy will automatically create [UDA files](https://docs.umbraco.com/umbraco-cloud/set-up/power-tools/generating-uda-files) based on that schema, and commit them to source control. This means that when you deploy all your files to the next environment the migration will run again, create duplicates and generate duplicate UDA files, which could end up causing a lot of issues. You could consider creating Umbraco schema only during a package action, and then running things like creating database tables in migrations. Another good workaround could be to not run the migrations in a composer, but rather create a dashboard for the package where the user can choose which migrations to run themselves. The [Articulate package](https://github.com/Shazwazza/Articulate/blob/master/build/packageManifest.xml#L613) has an example of this. ### Creating files -You may sometimes choose to save data in a file. Could be a separate config file for your package or a [config transform file](https://docs.umbraco.com/umbraco-cloud/setup/config-transforms) to add an app setting to the web.config. If you do this be aware of two things: +You may sometimes choose to save data in a file. Could be a separate config file for your package or a [config transform file](https://docs.umbraco.com/umbraco-cloud/set-up/config-transforms) to add an app setting to the web.config. If you do this be aware of two things: 1. If these files are generated on a Cloud environment they will not be stored in source control, and will be overwritten on next deployment. They need to be installed locally, committed to source control and then pushed up to the Cloud environments. We have an [existing feature request](../../reference/mapping.md) on allowing package creators to commit their files directly on Cloud, and it is possible to do so currently but not in a supported way, and it may change suddenly. -2. If you need the content of the files to be different on the different environments you will need to use environment specific [config transforms](https://docs.umbraco.com/umbraco-cloud/setup/config-transforms). +2. If you need the content of the files to be different on the different environments you will need to use environment specific [config transforms](https://docs.umbraco.com/umbraco-cloud/set-up/config-transforms). ## ValueConnectors diff --git a/13/umbraco-cms/tutorials/add-google-authentication.md b/13/umbraco-cms/tutorials/add-google-authentication.md index 59dd650ecb0..87157718662 100644 --- a/13/umbraco-cms/tutorials/add-google-authentication.md +++ b/13/umbraco-cms/tutorials/add-google-authentication.md @@ -110,7 +110,7 @@ The **ClientId** and **ClientSecret** can always be accessed from the **Credenti Once the Google API is set up it is time to install the Google Auth provider on the Umbraco project. -If you are working with a Cloud project, see the [Working locally](https://docs.umbraco.com/umbraco-cloud/setup/working-locally) article to complete this step. +If you are working with a Cloud project, see the [Working locally](https://docs.umbraco.com/umbraco-cloud/set-up/working-locally) article to complete this step. ### Installing a Nuget Package diff --git a/13/umbraco-cms/tutorials/multisite-setup.md b/13/umbraco-cms/tutorials/multisite-setup.md index 136dbba6e82..95f43e3bedd 100644 --- a/13/umbraco-cms/tutorials/multisite-setup.md +++ b/13/umbraco-cms/tutorials/multisite-setup.md @@ -7,7 +7,7 @@ description: A guide to multisite setup in Umbraco This tutorial explains how to host multiple sites from one project/installation of Umbraco. For practical reasons, we recommend using [Baselines](https://docs.umbraco.com/umbraco-cloud/getting-started/baselines) on Umbraco Cloud projects. {% hint style="info" %} -When using Baselines on Umbraco Cloud for a multisite solution, you would not need to worry about [Usage](https://docs.umbraco.com/umbraco-cloud/setup/project-settings/usage) limits, and could see better performance compared to having multiple websites in one project. +When using Baselines on Umbraco Cloud for a multisite solution, you would not need to worry about [Usage](https://docs.umbraco.com/umbraco-cloud/set-up/project-settings/usage) limits, and could see better performance compared to having multiple websites in one project. {% endhint %} If you are planning to create a multilingual site, please take a look at the [Multilanguage Setup](multilanguage-setup.md) tutorial instead. diff --git a/sustainability-best-practices/backend/cache-responses.md b/sustainability-best-practices/backend/cache-responses.md index 746a3a784aa..1f17316b719 100644 --- a/sustainability-best-practices/backend/cache-responses.md +++ b/sustainability-best-practices/backend/cache-responses.md @@ -6,4 +6,4 @@ This efficiency optimization aligns with the principles of sustainable design by By mitigating unnecessary resource usage and enhancing overall system responsiveness, caching contributes to a more sustainable software ecosystem. The result will be software ecosystem that operates efficiently and conserves resources, while still delivering high-quality user experiences. -With Umbraco's Delivery API it is possible to use output caching to increase a website's performance. You can read more about this in the [Output caching](https://docs.umbraco.com/umbraco-cms/v/13.latest-rc/reference/content-delivery-api/output-caching) article. +With Umbraco's Delivery API it is possible to use output caching to increase a website's performance. You can read more about this in the [Output caching](https://docs.umbraco.com/umbraco-cms/reference/content-delivery-api/output-caching) article. diff --git a/umbraco-cloud/product-upgrades/version-specific-upgrades/migrate-from-umbraco-7-to-8.md b/umbraco-cloud/product-upgrades/version-specific-upgrades/migrate-from-umbraco-7-to-8.md index 414a0577305..88e74ea18f0 100644 --- a/umbraco-cloud/product-upgrades/version-specific-upgrades/migrate-from-umbraco-7-to-8.md +++ b/umbraco-cloud/product-upgrades/version-specific-upgrades/migrate-from-umbraco-7-to-8.md @@ -163,7 +163,7 @@ Once the migration is complete, and the Live environment is running without erro ## Related information -* [Content Migration for Umbraco CMS - 7 to 8](https://docs.umbraco.com/umbraco-cms/fundamentals/setup/upgrading/version-specific/migrate-content-to-umbraco-8.md) +* [Content Migration for Umbraco CMS - 7 to 8](https://docs.umbraco.com/umbraco-cms/fundamentals/setup/upgrading/version-specific/migrate-content-to-umbraco-8) * [Issue tracker for known issues with Content Migration](https://github.com/umbraco/UmbracoDocs/issues) * [Forms on Umbraco Cloud](../../deployment/umbraco-forms-on-cloud.md) * [Working locally with Umbraco Cloud](../../set-up/working-locally.md) diff --git a/umbraco-cloud/release-notes/overview-2023/2023-02-releasenotes.md b/umbraco-cloud/release-notes/overview-2023/2023-02-releasenotes.md index e0518beb6d1..d66e78c3778 100644 --- a/umbraco-cloud/release-notes/overview-2023/2023-02-releasenotes.md +++ b/umbraco-cloud/release-notes/overview-2023/2023-02-releasenotes.md @@ -20,7 +20,7 @@ This organization-enforced MFA feature is easy to set up and manage and can help ## New Project Creation Flow -We are continuously migrating the pages of Umbraco Cloud Portal to a new front end stack. Lately, we have updated the [hostnames](https://docs.umbraco.com/umbraco-cloud/setup/project-settings/manage-hostnames) page and the project creation flow. In particular, for the latter, you will notice some significant improvements compared to the previous version. +We are continuously migrating the pages of Umbraco Cloud Portal to a new front end stack. Lately, we have updated the [hostnames](https://docs.umbraco.com/umbraco-cloud/set-up/project-settings/manage-hostnames) page and the project creation flow. In particular, for the latter, you will notice some significant improvements compared to the previous version. The new flow has a **more modern and visually appealing design**, which makes it more engaging and user-friendly. It features a **step-by-step guide** that leads users through the process of creating a new project, ensuring that they don't miss any important details. diff --git a/umbraco-cloud/set-up/manage-subscriptions/new-shop/subscription-migration-information-and-faq.md b/umbraco-cloud/set-up/manage-subscriptions/new-shop/subscription-migration-information-and-faq.md index a5b1655057f..0a81e5ba755 100644 --- a/umbraco-cloud/set-up/manage-subscriptions/new-shop/subscription-migration-information-and-faq.md +++ b/umbraco-cloud/set-up/manage-subscriptions/new-shop/subscription-migration-information-and-faq.md @@ -11,7 +11,7 @@ The migration of Umbraco Cloud subscriptions from shop.umbraco.com to the new su The process will be handled automatically, no action is required on your end. -You can find documentation on how the new subscription and billing engine works in the [Organizations documentation](https://docs.umbraco.com/umbraco-cloud/getting-started/the-umbraco-cloud-portal/organizations) and [Payments documentation](https://docs.umbraco.com/umbraco-cloud/\~/changes/I0HSeJqJ3Xoz7dFWrfy5/set-up/manage-subscriptions/new-shop). +You can find documentation on how the new subscription and billing engine works in the [Organizations documentation](https://docs.umbraco.com/umbraco-cloud/getting-started/the-umbraco-cloud-portal/organizations) and [Payments documentation](https://docs.umbraco.com/umbraco-cloud/set-up/manage-subscriptions/new-shop). ### Frequently Asked Questions