Sync all changes in Customizing section

Author: sofietoft

15/umbraco-cms/customizing/development-flow/vite-package-setup.md

@@ -171,7 +171,7 @@ export default class MyElement extends LitElement {
 ```
 {% endhint %}
 
-Learn more about the abilities of the manifest file in the [Umbraco Package Manifest](../package-manifest.md) article.
+Learn more about the abilities of the manifest file in the [Umbraco Package Manifest](../../customize-the-backoffice/umbraco-package.md) article.
 
 #### Testing your package
 

15/umbraco-cms/customizing/extending-overview/README.md

@@ -4,6 +4,12 @@ description: Getting started with backoffice setup and configurations
 
 # Extension Overview
 
+The Backoffice architecture is based on Extensions, making different UI parts extendable. Enabling you to append, replace, or remove parts.
+
+You are not limited to any specific tech stack. UI Elements are based on Web Components and the Backoffice APIs are based on native code.
+
+<figure><img src="../../.gitbook/assets/backoffice-overview-customizations.png" alt=""><figcaption></figcaption></figure>
+
 In this section you can find the common terms, concepts and guides used to extend the Umbraco backoffice.
 
 {% hint style="warning" %}

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

@@ -6,15 +6,15 @@ This page is a work in progress and may undergo further revisions, updates, or a
 
 Most of BackOffice is based on Extensions making it crucial to understand how to register your own extensions. This introduction will give you an outline of the abilities of the extension registry.
 
-## [Extension Registration](./extension-registry.md) <a href="#registration" id="registration"></a>
+## [Extension Registration](extension-registry.md) <a href="#registration" id="registration"></a>
 
 The extension registry is a global registry that can be accessed and changed at anytime while Backoffice is running.
 
-## [Extension Manifest](./extension-manifest.md)
+## [Extension Manifest](extension-manifest.md)
 
 Each Extension Manifest has to declare its type, this is used to determine where it hooks into the system. It also looks at what data is required to declare within it.
 
-## [Extension Types](../extension-types/README.md)
+## [Extension Types](../extension-types/)
 
 ### [Extension Conditions](../extension-types/condition.md) <a href="#conditions" id="conditions"></a>
 
@@ -28,10 +28,10 @@ The kinds feature enables you to base your extension registration on a preset. A
 import { umbExtensionsRegistry } from '@umbraco-cms/backoffice/extension-registry';
 ```
 
-### [Entry Point](../extension-types/entry-point.md) <a href="#entry-point" id="entry-point"></a>
+### [Entry Point](../extension-types/backoffice-entry-point.md) <a href="#entry-point" id="entry-point"></a>
 
 The Entry Point manifest type is used to register an entry point for the backoffice. An entry point is a single JavaScript file that is loaded when the backoffice is initialized. This file can be used to do anything, this enables more complex logic to take place on startup.
 
-### [Bundle](../extension-types/bundle.md) <a href="#bundle-manifest" id="package-manifest"></a>
+### [Bundle](../extension-types/bundle.md) <a href="#package-manifest" id="package-manifest"></a>
 
 The `bundle` extension type enables you to gather many extension manifests into one.

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

@@ -4,18 +4,15 @@
 This page is a work in progress and may undergo further revisions, updates, or amendments. The information contained herein is subject to change without notice.
 {% endhint %}
 
-The extension registry is the center piece of the Backoffice UI.
-It holds information about most of the Backoffice UI, as most are extensions. This includes the built-in UI.
-The registry can be manipulated at any time, meaning you can add or remove extensions at runtime.
+The extension registry is the center piece of the Backoffice UI. It holds information about most of the Backoffice UI, as most are extensions. This includes the built-in UI. The registry can be manipulated at any time, meaning you can add or remove extensions at runtime.
 
 To provide new UI to the backoffice, you must register them via an extension manifest. This has to be initiated via an Umbraco Package JSON file on the server. This will be your starting point, which enables you to register one or more extensions.
 
-Declaring a new extension is done by declaring an [extension manifest](./extension-manifest.md). This can be done in one of two ways:
+Declaring a new extension is done by declaring an [extension manifest](extension-manifest.md). This can be done in one of two ways:
 
 1. Via a manifest JSON file on the server.
 2. In a JavaScript/TypeScript file.
 
 These two options can be combined as you like.
 
-A typical use case of such is achieved by registering a single extension manifest in your Umbraco Package JSON file. This manifest would then load a JS file, that registers the rest of your extensions.
-Learn more about these abilities in the [bundle](../extension-types/bundle.md) or [backoffice entry point](../extension-types/entry-point.md) articles.
+A typical use case of such is achieved by registering a single extension manifest in your Umbraco Package JSON file. This manifest would then load a JS file, that registers the rest of your extensions. Learn more about these abilities in the [bundle](../extension-types/bundle.md) or [backoffice entry point](../extension-types/backoffice-entry-point.md) articles.

15/umbraco-cms/customizing/extending-overview/extension-types/backoffice-entry-point.md

@@ -1,4 +1,4 @@
-# Backoffice Entry Point
+# Entry Point
 
 {% hint style="warning" %}
 This page is a work in progress and may undergo further revisions, updates, or amendments. The information contained herein is subject to change without notice.
@@ -15,14 +15,14 @@ The Entry Point manifest type is used to register an entry point for the backoff
 
 ```json
 {
-  "name": "Name of your package",
-  "extensions: [
-      {
-        "type": "backofficeEntryPoint",
-        "alias": "My.EntryPoint",
-        "js": "/App_Plugins/YourFolder/index.js"
-      }
-  ]
+    "name": "Name of your package",
+    "extensions: [
+        {
+         "type": "backofficeEntryPoint",
+         "alias": "My.EntryPoint",
+         "js": "/App_Plugins/YourFolder/index.js"
+        }
+    ]
 }
 ```
 

15/umbraco-cms/customizing/foundation/README.md

@@ -4,28 +4,32 @@ description: Getting started with backoffice setup and configurations
 
 # Foundation
 
-In this section you can find the common terms, concepts and guides used to extend the Umbraco backoffice.
+In this section, you can find the common terms, concepts, and guides used to extend the Umbraco backoffice.
 
 {% hint style="warning" %}
 This page is a work in progress and may undergo further revisions, updates, or amendments. The information contained herein is subject to change without notice.
 {% endhint %}
 
-## [Working with Data](./working-with-data/README.md)
+## [Working with Bellissima](https://github.com/umbraco/Umbraco.Packages/tree/main/bellissima)
+
+An overview of community articles related to the New backoffice "Bellissima".
+
+## [Working with Data](working-with-data/)
 
 An overview of concepts on how to work with data when extending the backoffice.
 
-## [Contexts](./contexts/README.md)
+## [Contexts](contexts/)
 
 An overview of concepts on how to work with contexts when extending the backoffice.
 
-## [Umbraco Element](./umbraco-element/README.md)
+## [Umbraco Element](umbraco-element/)
 
 An overview of concepts on how to work with Umbraco element when extending the backoffice.
 
-## [Sorting](./sorting.md)
+## [Sorting](sorting.md)
 
 An overview of concepts on how to work with sorting when extending the backoffice.
 
-## [Routes](./routes.md)
+## [Routes](routes.md)
 
 An overview of concepts on how to work with routes when extending the backoffice.

15/umbraco-cms/customizing/foundation/contexts/README.md

@@ -10,10 +10,6 @@ This page is a work in progress and may undergo further revisions, updates, or a
 
 Below you can find some articles on how you can work with different contexts:
 
-## [Global Context](global-context.md)
-
-A global context manages the logic code from your Lit Element controllers.
-
-## [Property Dataset Context](variant-context.md)
+## [Property Dataset Context](../../../customize-the-backoffice/foundation/contexts/property-dataset-context.md)
 
 A Dataset Context is the connection point between a Property Editor and a Workspace and covers a set of properties.

15/umbraco-cms/customizing/foundation/routes.md

@@ -12,13 +12,13 @@ This page is a work in progress and may undergo further revisions, updates, or a
 
 The routing in the backoffice is flexible and customizable. In this article, you can find a couple of starting points for routing.
 
-The overall **divider** is the [Section](../section-trees/sections/) which is a `ManifestSection` extension type. It is also used internally by the following sections: Content, Media, Settings, Members, and so on.
+The overall **divider** is the [Section](../../customize-the-backoffice/extending-overview/extension-types/section.md) which is a `ManifestSection` extension type. It is also used internally by the following sections: Content, Media, Settings, Members, and so on.
 
 Depending on which section you are working on, there are different options:
 
-* **SectionView**: The [Section View](../section-trees/sections/section-view.md) is a view in a section and one of the automatic router extension types. It can be an entry point to a section. If a section has multiple views defined (or both dashboards and views) then the tabs and icons will be rendered. As some examples, you can check the **Packages** and **Member** sections.
-* **Dashboard**: The [Dashboard](../dashboards.md) is an entry point to a section. If there is more than one section view or dashboard then the defined tabs and icons will be rendered to make it possible to navigate.
-* **Workspace**: The [Workspace](../workspaces/) concept has built-in features to facilitate editing of an entity of a certain entity type. It is used by many entities in the backoffice like content, media, content types, data types, dictionaries and so on.
+* **SectionView**: The [Section View](../../customize-the-backoffice/extending-overview/extension-types/section-view.md) is a view in a section and one of the automatic router extension types. It can be an entry point to a section. If a section has multiple views defined (or both dashboards and views) then the tabs and icons will be rendered. As some examples, you can check the **Packages** and **Member** sections.
+* **Dashboard**: The [Dashboard](../../customize-the-backoffice/extending-overview/extension-types/dashboard.md) is an entry point to a section. If there is more than one section view or dashboard then the defined tabs and icons will be rendered to make it possible to navigate.
+* **Workspace**: The [Workspace](../../customize-the-backoffice/workspaces.md) concept has built-in features to facilitate editing of an entity of a certain entity type. It is used by many entities in the backoffice like content, media, content types, data types, dictionaries and so on.
 * **Custom element**: A [Custom Element](umbraco-element/) is a section that can be configured to use any web component as the **entry point**. The `element()` can be configured in the manifest. By doing this we'll disable the possibility of using dashboards and section views for the section since they will not be automatically routed/rendered. This option should be used only when necessary.
 
 ### Building routing

15/umbraco-cms/customizing/foundation/working-with-data/context-api.md

@@ -129,7 +129,7 @@ The consumption of the Additional API will never happen as the token uses the sa
 This is only relevant if you are going to make multiple context API for the same context. Discriminator only gives value for consumption of Context APIs that have a varying interface. The backoffice uses this for the different types of Workspace Contexts.
 {% endhint %}
 
-In some cases, it is needed to have different APIs for the same context. For example, the [Workspace Contexts](../../workspaces/workspace-context.md).
+In some cases, it is needed to have different APIs for the same context. For example, the [Workspace Contexts](../../../customize-the-backoffice/extending-overview/extension-types/workspace-context.md).
 
 If someone wants the workspace name, they might not care about the specific API of the Workspace Context. These implementations can use a standard Context Token with a type of generic Workspace Context.
 

15/umbraco-cms/customizing/project-bellissima.md

@@ -6,18 +6,10 @@ description: >-
 
 # Project Bellissima
 
-"Bellissima", the code name for the frontend code of the backoffice, is a re-creation of the backoffice of Umbraco. While replacing the deprecated angular code with [Vite](https://vitejs.dev/), [Lit](https://lit.dev/), and [TypeScript](https://www.typescriptlang.org/), you can customize and extend everything in the backoffice.
+"Bellissima", the code name for the frontend code of the backoffice, is a re-creation of the backoffice of Umbraco. While replacing the deprecated angular code with [Lit](https://lit.dev/) and [TypeScript](https://www.typescriptlang.org/), you can customize and extend everything in the backoffice.
 
 <figure><img src="../.gitbook/assets/backoffice-overview-customizations.png" alt=""><figcaption><p>An overview of all the customizable sections and elements in the Umbraco CMS backoffice.</p></figcaption></figure>
 
 Each block is an extension point that can be extended, customized, replaced, or removed.
 
 You are not limited to the mentioned frameworks. You can use any other framework or library of your choice.
-
-## Resources
-
-{% hint style="info" %}
-You can find a list of other resources related to the new backoffice of Umbraco in the [Umbraco v14 "Bellissima" Resources](https://github.com/umbraco/Umbraco.Packages/tree/main/bellissima) article.
-{% endhint %}
-
-<table data-view="cards"><thead><tr><th></th><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></td><td><a href="development-flow/"><strong>Setup Your Development Environment</strong></a></td><td>Discover how to get started with the new backoffice.</td><td><a href="../.gitbook/assets/Documentations Icons_Umbraco_CMS_Fundamentals_Setup (1).png">Documentations Icons_Umbraco_CMS_Fundamentals_Setup (1).png</a></td><td><a href="development-flow/">development-flow</a></td></tr><tr><td></td><td><a href="ui-documentation.md"><strong>UI Documentation</strong></a></td><td>Discover how to extend the backoffice using the Umbraco UI Library, UI API and Storybook.</td><td><a href="../.gitbook/assets/Documentations Icons_Umbraco_CMS_Fundamentals_Design.png">Documentations Icons_Umbraco_CMS_Fundamentals_Design.png</a></td><td><a href="ui-documentation.md">ui-documentation.md</a></td></tr><tr><td></td><td><a href="../tutorials/overview.md"><strong>Tutorials</strong></a></td><td><a href="../tutorials/creating-your-first-extension.md">Creating your first extension</a><br><br><a href="../tutorials/creating-a-custom-dashboard/">Creating a custom dashboard</a><br><br><a href="../tutorials/creating-a-property-editor/">Creating a property editor</a></td><td><a href="../.gitbook/assets/Documentations Icons_Umbraco_CMS_Tutorials_the_Starter_Kit (1).png">Documentations Icons_Umbraco_CMS_Tutorials_the_Starter_Kit (1).png</a></td><td></td></tr></tbody></table>