35 mins broken links

Author: sofietoft

15/umbraco-cms/customizing/extending-overview/extension-registry/extension-manifest.md

@@ -6,9 +6,9 @@ description: Learn about the different methods for declaring an Extension Manife
 
 The Extension Manifest is the first step for any extension. It is the declaration of what you want to register.
 
-In this section you will find all the Extension Types provided by the Backoffice. [See all Extension Types here.](../extension-types/)
+In this section you will find all the Extension Types provided by the Backoffice. [See all Extension Types here.](../extension-types/README.md)
 
-### Extension Manifest Format
+## Extension Manifest Format
 
 An Extension Manifest can be written as a JavaScript or JSON Object.
 
@@ -25,7 +25,7 @@ const manifest = {
 
 The `type` defines what it is declaring. The `alias` is a unique identifier for this manifest. It must be globally unique, so make sure to prefix it with something that makes your extension unique. The `name` is a representational name of this manifest, this does not need to be unique but such can be beneficial when debugging extensions.
 
-### Manifest Data
+## Manifest Data
 
 Each Extension Manifest has to declare its type. This is used to determine where it hooks into the system. It also determines what data is required of this manifest.
 
@@ -41,12 +41,12 @@ Additionally, many extensions support the use of the following fields:
 
 * `weight` - Define a weight, to determine the importance or visual order of this extension. The higher the weight, the higher in the list it will appear.
 * `overwrites` - Define one or more Extension Aliases that this extension should replace. Notice it only omits the listed Extensions when this is rendered in the same spot. [Read more in Replace, Exclude or Unregister](replace-exclude-or-unregister.md).
-* `conditions` - Define one or more conditions that must be permitted for the extension to become available. [Extension Conditions](../extension-conditions/extension-conditions.md).
+* `conditions` - Define one or more conditions that must be permitted for the extension to become available. [Extension Conditions](../extension-conditions.md).
 * `kind` - Define a kind-alias of which this manifest should be based upon. Kinds acts like a preset for your manifest. [Extension Kinds](../extension-kind.md).
 
 Many of the Extension Types require additional information declared as part of a `meta` field.
 
-### Registration
+## Registration
 
 An Extension Manifest can be registered in multiple ways.
 
@@ -58,15 +58,15 @@ This enables you to locate your Manifests in files together with the implementat
 
 A typical structure would be to declare one or more `Bundle` extensions in the Package Manifest. Each of the Bundles points to a `manifests.js` file which declares the Extensions of interest.
 
-#### The `bundle` extension type
+### The `bundle` extension type
 
 The Bundle extension type is used to declare multiple Extension Manifests from a single JavaScript file.
 
 The Bundle is loaded at startup. All the Extension Manifests exported of the JavaScript file will be registered.
 
-Read more about the `bundle` extension type in the [Bundle](../../../extending/extending-overview/extension-registry/bundle.md)[ ](../extension-types/bundle.md)article.
+Read more about the `bundle` extension type in the [Bundle](../extension-types/bundle.md)article.
 
-#### The `backofficeEntryPoint` extension type
+### The `backofficeEntryPoint` extension type
 
 Run any JavaScript code when Backoffice startups, after the user is logged in. This can be used as an entry point for a package, registering more extensions or configuring your package.
 
@@ -76,7 +76,7 @@ The entry point declares a single JavaScript file that will be loaded and run wh
 
 Read more about the `backofficeEntryPoint` extension type in the [Entry Point](extension-manifest.md#the-backofficeentrypoint-extension-type) article.
 
-#### The `appEntryPoint` extension type
+### The `appEntryPoint` extension type
 
 Similar as `appEntryPoint` this runs as startup, the difference is that this runs before the user is logged in. Use this to initiate things before the user is logged in or to provide things for the Login screen.
 

15/umbraco-cms/customizing/extending-overview/extension-types/menu.md

@@ -33,7 +33,7 @@ We can create the manifest using JSON in the `umbraco-package.json`.
 
 The manifest can also be written in TypeScript.
 
-For this TypeScript example we used a [Backoffice Entry Point](../../extending-overview/extension-types/backoffice-entry-point) extension to register the manifests.
+For this TypeScript example we used a [Backoffice Entry Point](../../extending-overview/extension-types/backoffice-entry-point.md) extension to register the manifests.
 
 ```typescript
 import { ManifestMenu } from "@umbraco-cms/backoffice/extension-registry";

15/umbraco-cms/customizing/extending-overview/extension-types/sections/section-view.md

@@ -48,7 +48,7 @@ We can create the manifest using json in the `umbraco-package.json`.
 {% tab title="TypeScript" %}
 The manifest can also be written in TypeScript.
 
-For this TypeScript example we used a [Backoffice Entry Point](../backoffice-entry-point/) extension to register the manifests.
+For this TypeScript example we used a [Backoffice Entry Point](../backoffice-entry-point.md) extension to register the manifests.
 
 ```typescript
 import { ManifestSectionView } from "@umbraco-cms/backoffice/extension-registry";

15/umbraco-cms/extending/build-on-umbraco-functionality.md

@@ -11,7 +11,7 @@ One of the biggest strengths of the Umbraco CMS is its flexibility. It is possib
 {% hint style="info" %}
 Are you looking to **customize and build extensions for the Umbraco backoffice?**
 
-All articles related to customizing and extending the Umbraco backoffice have been moved to the [Customize the Backoffice](broken-reference) section.
+All articles related to customizing and extending the Umbraco backoffice have been moved to the [Customize the Backoffice](../customizing/overview.md) section.
 {% endhint %}
 
 In this section, you can find resources to build and extend Umbraco CMS functionality.

15/umbraco-cms/extending/embedded-media-providers.md

@@ -121,7 +121,7 @@ If your third-party media provider lacks OEmbed support or requires custom HTML
 
 ### Custom Embed Provider Example
 
-Azure Media Services [(https://azure.microsoft.com/en-gb/services/media-services/)](https://azure.microsoft.com/en-gb/services/media-services/) provides 'broadcast-quality' video streaming services. You can embed the Azure Media Player into your site to play a video [using an IFrame](https://ampdemo.azureedge.net/azuremediaplayer.html).
+Azure Media Services [(https://azure.microsoft.com/en-gb/services/media-services/)](https://azure.microsoft.com/en-gb/services/media-services/) provides 'broadcast-quality' video streaming services. You can embed the Azure Media Player into your site to play a video using an IFrame.
 
 You can create a custom `EmbedProvider` to embed an IFrame video player in your content. This can be done by taking the Media asset URL and writing out the required markup.
 

15/umbraco-cms/extending/packages/good-practice-and-defaults.md

@@ -12,7 +12,7 @@ This document provides guides and notes on package development. It includes good
 
 To extend the Umbraco backoffice, a package can provide files such as `umbraco-package.json` and TypeScript/JavaScript files that should be stored within the `App_Plugins` folder. It's recommended to put all files in a subfolder with a unique name, preferably using the package name, like `App_Plugins\MyPackage`.
 
-For more information on how to extend the Umbraco backoffice, have a look at the [customizing the backoffice documentation](../../customizing/extend-and-customize-editing-experience.md)
+For more information on how to extend the Umbraco backoffice, have a look at the [customizing the backoffice documentation](../../customizing/overview.md)
 
 Files in the `App_Plugins` folder will be publicly available on the website even though they are not in the `wwwroot` folder. You should not store sensitive information in the `App_Plugins` folder.
 

15/umbraco-cms/fundamentals/backoffice/property-editors/built-in-umbraco-property-editors/block-editor/block-level-variance.md

@@ -18,9 +18,9 @@ This is known as Block Level Variance:
 
 Block Level Variance is achieved when:
 
-* The [Document Type](../../../../data/defining-content/default-document-types#document-type) is configured for variance, and
+* The [Document Type](../../../../data/defining-content/default-document-types.md#document-type) is configured for variance, and
 * The Block Editor property is _not_ configured for variance, and
-* The Block Editor property editor is configured to use [Element Types](../../../../data/defining-content/default-document-types#element-type) that _do_ vary.
+* The Block Editor property editor is configured to use [Element Types](../../../../data/defining-content/default-document-types.md#element-type) that _do_ vary.
 
 ## The "unexposed" Block state
 

15/umbraco-cms/fundamentals/backoffice/property-editors/built-in-umbraco-property-editors/tags.md

@@ -10,7 +10,7 @@ The Tags property editor allows you to add multiple tags to a node.
 
 ## Data Type Definition Example
 
-![Tags Data Type Definition Example](/14/umbraco-cms/fundamentals/backoffice/property-editors/built-in-umbraco-property-editors/images/tags-DataType.png)
+![Tags Data Type Definition Example](images/tags-DataType.png)
 
 ### Tag group
 
@@ -26,17 +26,17 @@ There are built-in property value converters, which means you don't need to worr
 
 ### CSV tags
 
-![CSV tags example](../../../../../../10/umbraco-cms/fundamentals/backoffice/property-editors/built-in-property-editors/images/Csv-example-v8.png)
+![CSV tags example](../built-in-property-editors/images/Csv-example-v8.png)
 
 ### JSON tags
 
-![JSON tags example](../../../../../../10/umbraco-cms/fundamentals/backoffice/property-editors/built-in-property-editors/images/Json-example-v8.png)
+![JSON tags example](../built-in-property-editors/images/Json-example-v8.png)
 
 ### Tags typeahead
 
 Whenever a tag has been added it will be visible in the typeahead when you start typing on other pages.
 
-![Tags typeahead example](../../../../../../10/umbraco-cms/fundamentals/backoffice/property-editors/built-in-property-editors/images/Typeahead-v8.png)
+![Tags typeahead example](../built-in-property-editors/images/Typeahead-v8.png)
 
 ## MVC View Example - displays a list of tags
 

15/umbraco-cms/fundamentals/backoffice/sections.md

@@ -75,7 +75,7 @@ For more information, see the [Packages](../../extending/packages/) article.
 
 The Users section allows administrators to manage user accounts, assign permissions, set user roles, and monitor user activity within the backoffice. It provides control over who can access and modify content, media, and settings in the CMS.
 
-For more information, see the [Users](../data/users.md) article.
+For more information, see the [Users](../data/users/README.md) article.
 
 ## Members
 

15/umbraco-cms/fundamentals/backoffice/settings-dashboards.md

@@ -14,7 +14,7 @@ The **Settings** section of the Umbraco backoffice has its own set of default da
 
 The Welcome dashboard is the first dashboard in the Settings section. Like all dashboards, it has a customizable view and links to different resources for developing your Umbraco website.
 
-For more information about creating custom dashboards, see the [Dashboards](../../customizing/dashboards.md) article.
+For more information about creating custom dashboards, see the [Dashboards](../../customizing/extending-overview/extension-types/dashboard.md) article.
 
 </details>