Merge pull request #7564 from umbraco/broken-links-cms

eshanrnh · web-flow · commit 54e2daba6ed3 · 2025-10-31T11:07:29.000+01:00
Fixed broken links
diff --git a/16/umbraco-cms/customizing/extending-overview/extension-types/backoffice-entry-point.md b/16/umbraco-cms/customizing/extending-overview/extension-types/backoffice-entry-point.md
@@ -125,7 +125,7 @@ import '/App_Plugins/YourFolder/global.css';
 
 It is recommended to make use of the Type intellisense that we provide.
 
-When writing your Manifest in TypeScript, you should use the `UmbExtensionManifest` type. Read the [TypeScript setup](broken-reference/) article to make sure you have Types correctly configured.
+When writing your Manifest in TypeScript, you should use the `UmbExtensionManifest` type. Read the [TypeScript setup](../../../customizing/development-flow/README.md#typescript-setup) article to make sure you have Types correctly configured.
 
 {% code title="index.ts" %}
 ```typescript
diff --git a/16/umbraco-cms/extending/packages/creating-a-package.md b/16/umbraco-cms/extending/packages/creating-a-package.md
@@ -112,7 +112,7 @@ Additionally, the `.csproj` file is configured to support NuGet packaging, allow
 Since the `umbraco-extension` template does not generate an `App_Plugins` folder by default, you will need to manually create it.
 
 1. Create an `App_Plugins` folder in the downloaded package folder.
-2. Go to the `welcome-dashboard` folder created in the [Creating a Custom Dashboard Tutorial](../../tutorials/creating-a-custom-dashboard/#setting-up-a-package).
+2. Go to the `welcome-dashboard` folder created in the [Creating a Custom Dashboard Tutorial](../../tutorials/creating-a-custom-dashboard/README.md#setting-up-a-package).
 3. Transfer or copy the `welcome-dashboard` folder in the `App_Plugins` folder.
 
 ![App\_Plugins with dashboard files](images/app-plugins-content.png)
diff --git a/16/umbraco-cms/fundamentals/backoffice/property-editors/README.md b/16/umbraco-cms/fundamentals/backoffice/property-editors/README.md
@@ -16,7 +16,7 @@ The following Property Editors have been removed with the release of Umbraco 14:
 * Grid Layout
 * Nested content
 
-We recommend using the [Block Editor](built-in-umbraco-property-editors/block-editor/) or the [Rich Text Editor Blocks](broken-reference) instead.
+We recommend using the [Block Editor](built-in-umbraco-property-editors/block-editor/README.md) or the [Rich Text Editor Blocks](built-in-umbraco-property-editors/rich-text-editor/README.md) instead.
 {% endhint %}
 
 When creating a Data Type, specify the property editor for the Data Type to use by selecting from the "Property editor" list (as shown below).
diff --git a/16/umbraco-cms/fundamentals/backoffice/property-editors/built-in-umbraco-property-editors/block-editor/block-grid-editor.md b/16/umbraco-cms/fundamentals/backoffice/property-editors/built-in-umbraco-property-editors/block-editor/block-grid-editor.md
@@ -51,7 +51,7 @@ The Data Type editor allows you to configure the following properties:
 
 ## Setup Block Types
 
-Block Types are based on [**Element Types**](../../../../data/defining-content/#element-types). These can be created beforehand or while setting up your Block Types.
+Block Types are based on [**Element Types**](../../../../data/defining-content/default-document-types.md#element-type). These can be created beforehand or while setting up your Block Types.
 
 Once you have added an Element Type as a Block Type on your Block Grid Data Type you have the option to configure it.
 
@@ -197,8 +197,8 @@ The Block is resized using a click-and-drag feature. Moving the mouse will chang
 
 Rendering the stored value of your **Block Grid** property editor can be done in two ways:
 
-1. [Default rendering](block-grid-editor.md#1-default-rendering)
-2. [Build your own rendering](block-grid-editor.md#2-build-your-own-rendering)
+1. [Default rendering](#1-default-rendering)
+2. [Build your own rendering](#2-build-custom-rendering)
 
 ### 1. Default rendering
 
diff --git a/16/umbraco-cms/fundamentals/backoffice/property-editors/built-in-umbraco-property-editors/block-editor/block-list-editor.md b/16/umbraco-cms/fundamentals/backoffice/property-editors/built-in-umbraco-property-editors/block-editor/block-list-editor.md
@@ -10,7 +10,7 @@
 This article is a work in progress and may undergo further revisions, updates, or amendments. The information contained herein is subject to change without notice.
 {% endhint %}
 
-**Block List** is a list editing property editor, using [Element Types](../../../../data/defining-content/#element-types) to define the list item schema.
+**Block List** is a list editing property editor, using [Element Types](../../../../data/defining-content/default-document-types.md#element-type) to define the list item schema.
 
 {% hint style="info" %}
 The _Block List_ replaces the obsolete _Nested Content_ editor.
diff --git a/16/umbraco-cms/fundamentals/data/content-version-cleanup.md b/16/umbraco-cms/fundamentals/data/content-version-cleanup.md
@@ -39,7 +39,7 @@ The feature can be configured in the `appSettings.json`:
 }
 ```
 
-For sites with stricter requirements, it is possible to opt-out of both options globally, see [ContentSettings](../../reference/configuration/contentsettings.md#contentversioncleanuppolicy) and by Document Type.
+For sites with stricter requirements, it is possible to opt-out of both options globally, see [ContentSettings](../../reference/configuration/contentsettings.md#content-version-cleanup-policy) and by Document Type.
 
 Additionally, it is possible to keep the feature enabled but mark specific versions to keep forever.
 
diff --git a/16/umbraco-cms/fundamentals/data/creating-media/README.md b/16/umbraco-cms/fundamentals/data/creating-media/README.md
@@ -19,15 +19,15 @@ Media in Umbraco CMS is handled the same way as content. You define **Media Type
 The default Media Types aim to cover most needs for media on a website. You do not need to define your Media Types to start using the Media section. The tools for organizing and uploading the media are already in place.
 
 {% hint style="info" %}
-If you have upgraded from an older version than 8.14 the Media Types listed above are not added automatically. You can add those types manually yourselves by following the steps below ['Creating a new Media Type'](./#creating-a-media-type). On the [default media types page](default-media-types.md), you will find a detailed overview of all Media Types.
+If you have upgraded from an older version than 8.14 the Media Types listed above are not added automatically. You can add those types manually yourselves by following the steps below ['Creating a new Media Type'](./README.md#creating-a-media-type). On the [default media types page](default-media-types.md), you will find a detailed overview of all Media Types.
 {% endhint %}
 
 ## Uploading Media
 
 You can upload media in two different ways:
 
-* [Through the Media section](./#add-media-through-the-media-section) and
-* [Through the Content section](./#add-media-through-the-content-section)
+* [Through the Media section](#add-media-through-the-media-section) and
+* [Through the Content section](#add-media-through-the-content-section)
 
 ### Add media through the Media section
 
diff --git a/16/umbraco-cms/fundamentals/data/dictionary-items.md b/16/umbraco-cms/fundamentals/data/dictionary-items.md
@@ -51,7 +51,7 @@ To edit a dictionary item, follow these steps:
 {% hint style="info" %}
 It will only be possible to edit the language(s) that the given user has access to. The value of the remaining languages will be _read-only_.
 
-Which language a user has access to is determined by the "Language permissions" set on the User Group. Learn more about this feature in the [Users](users/#creating-a-user-group) article.
+Which language a user has access to is determined by the "Language permissions" set on the User Group. Learn more about this feature in the [Users](users/README.md#creating-a-user-group) article.
 {% endhint %}
 
 ## Fetching Dictionary Values in the Template
diff --git a/16/umbraco-cms/fundamentals/design/rendering-content.md b/16/umbraco-cms/fundamentals/design/rendering-content.md
@@ -4,7 +4,7 @@ _The primary task of any template is to render the values of the current page or
 
 ## Display a value in your template view
 
-Each property in your [Document Type](../data/defining-content/#what-is-a-document-type) has an alias, this is used to specify where in the template view to display the value.
+Each property in your [Document Type](../data/defining-content/README.md#what-is-a-document-type) has an alias, this is used to specify where in the template view to display the value.
 
 ```html
 <h1>@Model.Value("pageTitle")</h1>
diff --git a/16/umbraco-cms/fundamentals/design/rendering-media.md b/16/umbraco-cms/fundamentals/design/rendering-media.md
@@ -144,4 +144,4 @@ If you want the original, uncropped image, you can ignore the GetCropUrl extensi
 
 * [Media Picker](../backoffice/property-editors/built-in-umbraco-property-editors/media-picker-3.md)
 * [Image Cropper](../backoffice/property-editors/built-in-umbraco-property-editors/image-cropper.md)
-* [Creating a Media Type](../data/creating-media/#creating-a-media-type)
+* [Creating a Media Type](../data/creating-media/README.md#creating-a-media-type)
diff --git a/16/umbraco-cms/fundamentals/design/stylesheets-javascript.md b/16/umbraco-cms/fundamentals/design/stylesheets-javascript.md
@@ -46,7 +46,7 @@ or
 
 With the stylesheet referenced, you will be able to style the template file with the rules and classes defined in the stylesheet.
 
-Your stylesheets can be used in Rich Text Editors (datatype) as well - please see the [Rich Text Editor](../backoffice/property-editors/built-in-umbraco-property-editors/rich-text-editor/#rte-styles) documentation for more information.
+Your stylesheets can be used in Rich Text Editors (datatype) as well. See the [Rich Text Editor](../backoffice/property-editors/built-in-umbraco-property-editors/rich-text-editor/css-properties.md) documentation for more information.
 
 {% hint style="info" %}
 If your RTE is styled differently on the frontend of the site, the backoffice styling might be getting overwritten by other stylesheets you have included.
diff --git a/16/umbraco-cms/fundamentals/setup/install/unattended-install.md b/16/umbraco-cms/fundamentals/setup/install/unattended-install.md
@@ -8,7 +8,7 @@ This article will give you the details you need to install Umbraco unattended.
 
 ## Get clean install of Umbraco
 
-In order to get a clean instance of Umbraco, follow our installation guide for how to [Install an Umbraco project template](install-umbraco-with-templates.md#install-umbraco-with-net-cli).
+In order to get a clean instance of Umbraco, follow our installation guide for how to [Install an Umbraco project template](install-umbraco-with-templates.md#install-using-net-cli).
 
 ## Configure your database
 
diff --git a/16/umbraco-cms/fundamentals/setup/install/visual-studio.md b/16/umbraco-cms/fundamentals/setup/install/visual-studio.md
@@ -12,7 +12,7 @@ description: A guide to install Umbraco CMS using Visual Studio.
 
 ## Quick Start
 
-This is an abbreviated version of the installation steps. Jump to the [Create a new project](visual-studio.md#new-project) section for a more thorough guide.
+This is an abbreviated version of the installation steps. Jump to the [Create a new project](#create-a-new-umbraco-project) section for a more thorough guide.
 
 * Open Visual Studio.
 * Go to `File` > `New` > `Project`, search for **Umbraco**.
@@ -29,9 +29,10 @@ How to install Umbraco using NuGet and Visual Studio
 
 ## Create a new Umbraco project
 
-To install Umbraco we first need to install Umbraco's dotnet new templates.
+To install Umbraco, follow these steps:
 
-For more information check the first 2 steps of [Install Umbraco with .NET CLI](install-umbraco-with-templates.md#install-the-template).
+1. Install the latest [.NET SDK](https://dotnet.microsoft.com/download).
+2. Run `dotnet new install Umbraco.Templates` to install the project templates.
 
 ### Create the Visual Studio project
 
diff --git a/16/umbraco-cms/fundamentals/setup/server-setup/load-balancing/README.md b/16/umbraco-cms/fundamentals/setup/server-setup/load-balancing/README.md
@@ -133,7 +133,7 @@ Ensure to analyze logs from all servers and check for any warnings and errors.
 
 When upgrading it is possible to run the upgrades unattended.
 
-Find steps on how to enable the feature for a load balanced setup in the [General Upgrades](../../upgrading/#unattended-upgrades-in-a-load-balanced-setup) article.
+Find steps on how to enable the feature for a load balanced setup in the [General Upgrades](../../upgrading/upgrade-unattended.md#unattended-upgrades-in-a-load-balanced-setup) article.
 
 ## FAQs
 
diff --git a/16/umbraco-cms/fundamentals/setup/upgrading/upgrade-unattended.md b/16/umbraco-cms/fundamentals/setup/upgrading/upgrade-unattended.md
@@ -10,7 +10,7 @@ When upgrading your Umbraco project, you can enable the upgrade to run unattende
 
 Are you running a load-balanced setup with multiple servers and environments?
 
-Check out the section about [Unattended upgrades in a load-balanced setup](#unattended-upgrades-in-a-load-balanced-setup).
+Check out the section about [Unattended upgrades in a load-balanced setup](../upgrading/upgrade-unattended.md#unattended-upgrades-in-a-load-balanced-setup).
 
 {% endhint %}
 
diff --git a/16/umbraco-cms/fundamentals/setup/upgrading/version-specific/minor-upgrades-for-umbraco-7.md b/16/umbraco-cms/fundamentals/setup/upgrading/version-specific/minor-upgrades-for-umbraco-7.md
@@ -34,7 +34,7 @@ The upgrade will run through all the files and make sure you have the latest cha
 
 ### Upgrades to versions lower than 7.2.0
 
-If you're not upgrading to 7.2.0 or higher then you should follow these extra instructions. If you are upgrading to 7.2.0+ then you can skip this and go to [Merge UI.xml and language](minor-upgrades-for-umbraco-7.md#merge-ui-xml-and-language).
+If you're not upgrading to 7.2.0 or higher then you should follow these extra instructions. If you are upgrading to 7.2.0+ then you can skip this and go to [Merge UI.xml and language](minor-upgrades-for-umbraco-7.md#merge-uixml-and-language).
 
 You will be asked to overwrite your web.config file and the files in /config, make sure to answer **No** to those questions.
 
diff --git a/16/umbraco-cms/fundamentals/setup/upgrading/version-specific/minor-upgrades-for-umbraco-8.md b/16/umbraco-cms/fundamentals/setup/upgrading/version-specific/minor-upgrades-for-umbraco-8.md
@@ -83,7 +83,7 @@ Below you will find the steps you need to take in order to upgrade your project
 {% hint style="info" %}
 Are you running a load balanced setup with multiple servers and environments?
 
-Check out the section about [Unattended upgrades in a load balanced setup](#unattended-upgrades-in-a-load-balanced-setup).
+Check out the section about [Unattended upgrades in a load balanced setup](../upgrade-unattended.md#unattended-upgrades-in-a-load-balanced-setup).
 {% endhint %}
 
 ### Enable the feature
diff --git a/16/umbraco-cms/reference/routing/README.md b/16/umbraco-cms/reference/routing/README.md
@@ -6,32 +6,40 @@ description: >-
 
 # Routing & Controllers
 
-All about Umbraco's routing pipeline & the types of Controllers used in Umbraco, how they work, and what they are used for.
+Learn about Umbraco’s routing pipeline and the different types of controllers used in Umbraco, how they work, and what they’re used for.
 
-## [Request Pipeline](request-pipeline/)
+## [Custom Controllers (hijacking routes)](custom-controllers.md)
 
-Explains how Umbraco builds its URLs and how the URLs are mapped back to content items.
+Create custom controllers to override Umbraco’s default rendering behavior, a technique known as “hijacking routes.”
 
-## [Routing Properties](routing-properties.md)
+## [Custom Routes](custom-routes.md)
 
-Describes the Umbraco special/reserved Property Type aliases that can be used to directly manipulate Umbraco's default routing pipeline. These special Property Type aliases can be useful when creating an Umbraco website.
+Define your own MVC routes in your Umbraco application.
 
-## [Surface Controllers](surface-controllers/)
+## [Custom Middleware](custom-middleware.md)
+
+Learn how to add custom middleware to Umbraco’s ASP.NET Core pipeline.
+
+## [URL Rewrites in Umbraco](iisrewriterules.md)
 
-What is a Surface Controller and how to use it?
+Explains how to configure IIS rewrite rules for your Umbraco site.
 
-## [Custom Controllers (hijacking routes)](./#custom-controllers-hijacking-routes)
+## [Special Property Type aliases for routing](routing-properties.md)
 
-Creating custom controllers to have 100% full control over how your pages are rendered. Also known as: Hijacking Umbraco Routes
+Describes the reserved property type aliases that influence Umbraco’s routing behavior, such as URL aliases and redirects.
 
-## [Custom Routes](../../implementation/custom-routing/)
+## [URL Redirect Management](url-tracking.md)
 
-How to specify your own custom MVC routes in your Umbraco application?
+Understand how Umbraco automatically creates redirects when content is moved or renamed.
 
-## [Routes & Authentication](./#routes-and-authentication)
+## [Routing in Umbraco](request-pipeline/)
+
+Explains how Umbraco builds and resolves URLs, maps them back to content items, and determines how requests are rendered.
+
+## [Surface Controllers](surface-controllers/)
 
-Routing requirements for authenticated controllers for both the front end and the backoffice.
+Learn what Surface Controllers are and how to use them to handle form submissions or render partial views.
 
-## [URL Tracking](url-tracking.md)
+## [Umbraco API Controllers](umbraco-api-controllers/)
 
-Moving and renaming Umbraco documents will lead to URL redirects being created.
+Describes how to create and use Umbraco API Controllers to expose custom Web API endpoints from your Umbraco application.
diff --git a/16/umbraco-cms/tutorials/creating-a-custom-dashboard/README.md b/16/umbraco-cms/tutorials/creating-a-custom-dashboard/README.md
@@ -8,8 +8,8 @@ description: A guide to creating a custom dashboard in Umbraco
 
 This guide outlines the steps to set up a custom dashboard in Umbraco. Part one covers:
 
-1. [Setting up a Package](./#setting-up-a-package)
-2. [Creating the Dashboard Web Component](./#creating-the-dashboard-web-component)
+1. [Setting up a Package](./README.md#setting-up-a-package)
+2. [Creating the Dashboard Web Component](./README.md#creating-the-dashboard-web-component)
 
 ### What is a Dashboard?
 
diff --git a/16/umbraco-cms/tutorials/creating-custom-views-for-blocklist.md b/16/umbraco-cms/tutorials/creating-custom-views-for-blocklist.md
@@ -247,4 +247,4 @@ export default ExampleBlockCustomView;
 
 ## Rendering the Block List Content
 
-To render the stored value of your Block List editor on the frontend, see the [Rendering Block List Content](../fundamentals/backoffice/property-editors/built-in-umbraco-property-editors/block-editor/#block-list) section.
+To render the stored value of your Block List editor on the frontend, see the [Rendering Block List Content](../fundamentals/backoffice/property-editors/built-in-umbraco-property-editors/block-editor/block-list-editor.md) section.
diff --git a/16/umbraco-cms/tutorials/custom-error-page.md b/16/umbraco-cms/tutorials/custom-error-page.md
@@ -16,8 +16,8 @@ In Umbraco, in-code error page handling refers to managing and displaying custom
 
 This article contains guides on how to create custom error pages for the most common scenarios:
 
-* [404 Errors ("Page not found")](custom-error-page.md#id-404-errors)
-* [500 Errors ("Internal Server Error")](custom-error-page.md#id-500-errors)
+* [404 Errors ("Page not found")](custom-error-page.md#404-errors)
+* [500 Errors ("Internal Server Error")](custom-error-page.md#500-errors)
 * [Boot Failed Errors](custom-error-page.md#boot-failed-errors)
 
 {% hint style="info" %}
diff --git a/16/umbraco-cms/tutorials/editors-manual/media-management/cropping-images.md b/16/umbraco-cms/tutorials/editors-manual/media-management/cropping-images.md
@@ -6,7 +6,7 @@ If your system administrator has set up cropping for your images, you will see a
 
 The circle in the middle of the image is the default focal point. The focal point defines the primary area or focus of the image which will be the center point of any image re-sizing. You can move the focal point by clicking and dragging it to the desired part of the image.
 
-Next to the image, you may see specific crops of the image depending on your setup. In the above example, you can see that 2 crops have been set-up. To add or update the image crops, see [Adding properties](../../../fundamentals/data/creating-media/#adding-properties) section in the [Creating media](../../../fundamentals/data/creating-media/) article.
+Next to the image, you may see specific crops of the image depending on your setup. In the above example, you can see that 2 crops have been set-up. To add or update the image crops, see [Adding properties](../../../fundamentals/data/creating-media/README.md#adding-properties) section in the [Creating media](../../../fundamentals/data/creating-media/) article.
 
 To manually alter the pre-defined crops:
 
diff --git a/17/umbraco-cms/.gitbook/assets/umbraco-docs-data-type-property-editor-data-source.png b/17/umbraco-cms/.gitbook/assets/umbraco-docs-data-type-property-editor-data-source.png
diff --git a/umbraco-cloud/begin-your-cloud-journey/creating-a-cloud-project/migrate-to-umbraco-cloud.md b/umbraco-cloud/begin-your-cloud-journey/creating-a-cloud-project/migrate-to-umbraco-cloud.md
@@ -160,7 +160,7 @@ The Umbraco Cloud project is now ready for the next step where the two projects
 
 To continue the migration the next step is to clone down the Umbraco Cloud environment to merge it with the Umbraco CMS project.
 
-Follow the steps outlined in the [Working with a Local Clone](../../build-and-customize-your-solution/handle-deployments-and-environments/working-locally/#cloning-an-umbraco-cloud-project) article to clone down the Development environment on the project.
+Follow the steps outlined in the [Working with a Local Clone](../../build-and-customize-your-solution/handle-deployments-and-environments/working-locally/README.md#cloning-an-umbraco-cloud-project) article to clone down the Development environment on the project.
 
 {% hint style="info" %}
 Do not run the project after cloning it down.
@@ -253,7 +253,7 @@ Verifying the migration by cloning the Development environment to your local mac
 
 This needs to be **a new clone**. The clone used throughout the migration steps can be deleted.
 
-Follow the steps outlined in the [Working with a Local Clone](../../build-and-customize-your-solution/handle-deployments-and-environments/working-locally/#cloning-an-umbraco-cloud-project) article to clone down, restore, and run the **Development environment** locally.
+Follow the steps outlined in the [Working with a Local Clone](../../build-and-customize-your-solution/handle-deployments-and-environments/working-locally/README.md#cloning-an-umbraco-cloud-project) article to clone down, restore, and run the **Development environment** locally.
 
 {% hint style="info" %}
 You might need to do a **Workspace restore** from the **Media** section in the Umbraco backoffice to restore the media files.
diff --git a/umbraco-cloud/build-and-customize-your-solution/handle-deployments-and-environments/umbraco-cicd/samplecicdpipeline/azure-devops-v1.md b/umbraco-cloud/build-and-customize-your-solution/handle-deployments-and-environments/umbraco-cicd/samplecicdpipeline/azure-devops-v1.md
diff --git a/umbraco-cloud/build-and-customize-your-solution/handle-deployments-and-environments/umbraco-cicd/samplecicdpipeline/azure-devops.md b/umbraco-cloud/build-and-customize-your-solution/handle-deployments-and-environments/umbraco-cicd/samplecicdpipeline/azure-devops.md
diff --git a/umbraco-cloud/build-and-customize-your-solution/handle-deployments-and-environments/umbraco-cicd/samplecicdpipeline/github-actions-v1.md b/umbraco-cloud/build-and-customize-your-solution/handle-deployments-and-environments/umbraco-cicd/samplecicdpipeline/github-actions-v1.md
diff --git a/umbraco-cloud/build-and-customize-your-solution/handle-deployments-and-environments/umbraco-cicd/samplecicdpipeline/github-actions.md b/umbraco-cloud/build-and-customize-your-solution/handle-deployments-and-environments/umbraco-cicd/samplecicdpipeline/github-actions.md
diff --git a/umbraco-cloud/build-and-customize-your-solution/handle-deployments-and-environments/umbraco-cicd/samplecicdpipeline/migrate.md b/umbraco-cloud/build-and-customize-your-solution/handle-deployments-and-environments/umbraco-cicd/samplecicdpipeline/migrate.md

Original file line number	Diff line number	Diff line change
@@ -39,7 +39,7 @@ The feature can be configured in the `appSettings.json`:
`39`	`39`	`}`
`40`	`40`	```
`41`	`41`
`42`		`-For sites with stricter requirements, it is possible to opt-out of both options globally, see [ContentSettings](../../reference/configuration/contentsettings.md#contentversioncleanuppolicy) and by Document Type.`
	`42`	`+For sites with stricter requirements, it is possible to opt-out of both options globally, see [ContentSettings](../../reference/configuration/contentsettings.md#content-version-cleanup-policy) and by Document Type.`
`43`	`43`
`44`	`44`	`Additionally, it is possible to keep the feature enabled but mark specific versions to keep forever.`
`45`	`45`