Merge pull request #6024 from klm-b/main

alina-tincas · web-flow · commit 732495b352c8 · 2024-04-15T08:29:13.000+02:00
Fix broken links
diff --git a/10/umbraco-cms/implementation/controllers.md b/10/umbraco-cms/implementation/controllers.md
@@ -56,7 +56,7 @@ The Umbraco Authorized controllers and attributes for Backoffice Users are:
     - `[Authorize(Policy = AuthorizationPolicies.BackOfficeAccess)]`: Uses .NET authorization using the BackOfficeAccess policy. We recommend adding extra custom authorization policies for your endpoints.
     - `[DisableBrowserCache]`: Tells the browser to not cache the result.
 
-    Remember to [add a route](../reference/routing/authorized/defining-a-route) for your controller.
+    Remember to [add a route](../reference/routing/authorized.md#defining-a-route) for your controller.
 
     #### Example custom authorized backoffice MVC Controller
     ```csharp
diff --git a/12/umbraco-cms/implementation/controllers.md b/12/umbraco-cms/implementation/controllers.md
@@ -50,7 +50,7 @@ The Umbraco Authorized controllers and attributes for Backoffice Users are:
     - `[Authorize(Policy = AuthorizationPolicies.BackOfficeAccess)]`: Uses .NET authorization using the BackOfficeAccess policy. We recommend adding extra custom authorization policies for your endpoints.
     - `[DisableBrowserCache]`: Tells the browser to not cache the result.
 
-    Remember to [add a route](../reference/routing/authorized/defining-a-route) for your controller.
+    Remember to [add a route](../reference/routing/authorized.md#defining-a-route) for your controller.
 
     #### Example custom authorized backoffice MVC Controller
     ```csharp
diff --git a/13/umbraco-cms/implementation/controllers.md b/13/umbraco-cms/implementation/controllers.md
@@ -50,7 +50,7 @@ The Umbraco Authorized controllers and attributes for Backoffice Users are:
     - `[Authorize(Policy = AuthorizationPolicies.BackOfficeAccess)]`: Uses .NET authorization using the BackOfficeAccess policy. We recommend adding extra custom authorization policies for your endpoints.
     - `[DisableBrowserCache]`: Tells the browser to not cache the result.
 
-    Remember to [add a route](../reference/routing/authorized/defining-a-route) for your controller.
+    Remember to [add a route](../reference/routing/authorized.md#defining-a-route) for your controller.
 
     #### Example custom authorized backoffice MVC Controller
     ```csharp
diff --git a/14/umbraco-cms/implementation/controllers.md b/14/umbraco-cms/implementation/controllers.md
@@ -50,7 +50,7 @@ The Umbraco Authorized controllers and attributes for Backoffice Users are:
     - `[Authorize(Policy = AuthorizationPolicies.BackOfficeAccess)]`: Uses .NET authorization using the BackOfficeAccess policy. We recommend adding extra custom authorization policies for your endpoints.
     - `[DisableBrowserCache]`: Tells the browser to not cache the result.
 
-    Remember to [add a route](../reference/routing/authorized/defining-a-route) for your controller.
+    Remember to [add a route](../reference/routing/authorized.md#defining-a-route) for your controller.
 
     #### Example custom authorized backoffice MVC Controller
     ```csharp
diff --git a/umbraco-heartcore/README.md b/umbraco-heartcore/README.md
@@ -2,7 +2,7 @@
 
 Umbraco Heartcore is a headless Software As A Service (SAAS) offered by Umbraco. The service enables you to create and manage content and media in the Umbraco backoffice and make it available to any platforms, devices, channels and so forth.
 
-<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-cover data-type="files"></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Getting started</strong></td><td>Get started working with Umbraco Heartcore</td><td><a href="../generic/images/headless.png">headless.png</a></td><td><a href="api-documentation/content-delivery/content.md">content.md</a></td></tr><tr><td><strong>Umbraco Heartcore APIs</strong></td><td>See the different APIs available in Umbraco Heartcore</td><td><a href="../generic/images/code (1) (1) (1).png">code (1) (1) (1).png</a></td><td><a href="broken-reference">Broken link</a></td></tr><tr><td><strong>Client libraries</strong></td><td>Test out your Umbraco Heartcore project with the pre-made client libraries</td><td><a href="../generic/images/devices.png">devices.png</a></td><td><a href="https://docs.umbraco.com/umbraco-heartcore/client-libraries/client-libraries">https://docs.umbraco.com/umbraco-heartcore/client-libraries/client-libraries</a></td></tr></tbody></table>
+<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-cover data-type="files"></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Getting started</strong></td><td>Get started working with Umbraco Heartcore</td><td><a href="../generic/images/headless.png">headless.png</a></td><td><a href="api-documentation/content-delivery/content.md">content.md</a></td></tr><tr><td><strong>Umbraco Heartcore APIs</strong></td><td>See the different APIs available in Umbraco Heartcore</td><td><a href="../generic/images/code (1) (1) (1).png">code (1) (1) (1).png</a></td><td><a href="api-documentation/">api-documentation/</a></td></tr><tr><td><strong>Client libraries</strong></td><td>Test out your Umbraco Heartcore project with the pre-made client libraries</td><td><a href="../generic/images/devices.png">devices.png</a></td><td><a href="client-libraries/">client-libraries/</a></td></tr></tbody></table>
 
 {% embed url="https://www.youtube.com/embed/Rujaw1VWUaQ?rel=0" %}
 How to create a Heartcore Trial
diff --git a/umbraco-heartcore/api-documentation/content-management/media/README.md b/umbraco-heartcore/api-documentation/content-management/media/README.md
@@ -482,7 +482,7 @@ Media can be created by sending a POST request to the media endpoint. The reques
 The `umbracoFile.src` property in the first `MultipartBoundary`'s JSON body defines the name of the file to be uploaded. The `fileName` in the second `MultipartBoundary` must match the `umbracoFile.src` property's value.
 
 {% hint style="info" %}
-Different media property editors will require different request body formats.The File Upload property editor has the file name as the value `"umbracoFile": FILE_NAME`, and the Image Cropper property editor expects a JSON value `"umbracoFile": { "src": FILE_NAME }`. To verify the JSON structure you can manually upload the media file via the backoffice and fetch the data. It can then be used for reference. (See how in the [Creating Content with Media](../../../tutorials/management-api/creating-content-with-media.md) tutorial.)
+Different media property editors will require different request body formats.The File Upload property editor has the file name as the value `"umbracoFile": FILE_NAME`, and the Image Cropper property editor expects a JSON value `"umbracoFile": { "src": FILE_NAME }`. To verify the JSON structure you can manually upload the media file via the backoffice and fetch the data. It can then be used for reference. (See how in the [Creating Content with Media](../../../tutorials/creating-content-with-media.md) tutorial.)
 {% endhint %}
 
 **URL**: `/media`
diff --git a/umbraco-heartcore/tutorials/creating-content-with-media.md b/umbraco-heartcore/tutorials/creating-content-with-media.md
@@ -74,7 +74,7 @@ To use the Management API, you need an API key. You can get your API key by foll
 1. Go to the `Users` section in the backoffice and click the `API Keys` tab in the editor window.
 2. Click show on the API key you want to use.
 
-If you do not have an API key yet, you can create one under `Users > Your User > API Keys > Create API Key`. See the [Getting Started](broken-reference) section for more information on how to do this.
+If you do not have an API key yet, you can create one under `Users > Your User > API Keys > Create API Key`. See the [Getting Started](../getting-started/backoffice-users-and-api-keys.md) section for more information on how to do this.
 
 ### Getting the content node ID
 
