First draft of extension manifest done

Author: Luuk Peters

16/umbraco-cms/.gitbook.yaml

@@ -145,3 +145,4 @@ redirects:
     extending/customize-backoffice: customizing/README.md
     extending/content-apps: customizing/extending-overview/extension-types/workspaces/workspace-views.md
     extending/backoffice-setup/extension-types: customizing/extending-overview/extension-types/README.md
+    customizing/extending-overview/extension-registry/extension-registry: customizing/extending-overview/extension-registry/register-extensions.md

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

@@ -5,17 +5,15 @@ description: >-
 ---
 
 # Extension Registry
+The Umbraco backoffice is build with extendability in mind. The backoffice without extensions is more or less a blank canvas that is build out using extensions. These extensions dictate how the backoffice functions and looks. All visual elements in an Umbraco installation, like the sections, menu's, trees and buttons, are extensions. But extensions also dictate behaviour and the editing experience. So everything in the backoffice is governed (and extendable) by extensions.
 
-The Extensions Registry is your entry to extend or customize the Backoffice. Therefore, it is crucial to understand the abilities of the Extension Registry.
+All extensions are registered in the extension registry. The registry can be manipulated at any time, meaning you can add or remove extensions at runtime. You as a developer have the same possibilities as an Umbraco HQ developer, which means what HQ can do, you can do. This also means that you can change almost everything that is by default present in Umbraco. You can see in the backoffice what extensions are registered by going to Settings > Extensions Insights.
 
-## [Extension Registration](extension-registry.md) <a href="#registration" id="registration"></a>
+## [Introduction to a Extension Manifest](extension-manifest.md)
+An Extension Manifest is a declaration on what you want to register in the Umbraco backoffice. This handles what an extension manifest looks like and what is required or not.
 
+## [Register an extension](extension-registry.md)
 The extension registry is a global registry that can be accessed and changed at any time while Backoffice is running.
 
-## [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.
-
-## [Replace, Exclude, or Unregister](replace-exclude-or-unregister.md)
-
+## [Change an existing extension](replace-exclude-or-unregister.md)
 Once you understand how to declare your own, you may want to replace or remove existing ones.

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

@@ -3,45 +3,52 @@ description: Learn about the different methods for declaring an Extension Manife
 ---
 
 # Extension Manifest
+This page explains how to author Extension Manifests for Umbraco backoffice extensions.
+It outlines the manifest structure, required fields, and optional features used across types.
 
-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/)
+## What is an Extension Manifest?
+An Extension Manifest declares a single backoffice extension and its configuration.
+Umbraco reads the manifest to register the extension in the Extension Registry.
+The chosen extension type determines required fields and available capabilities.
+Some extensions need extra assets, like a JavaScript file with a Web Component.
 
 ## Extension Manifest Format
+An Extension Manifest has a strict format where some properties are required and some depend on the Extension Type. An Extension Manifest can be written as a JavaScript or JSON Object. We'll dive deeper into that when [registering an extension](extension-registry).
 
-An Extension Manifest can be written as a JavaScript or JSON Object.
+The abilities of the extensions rely on the specific extension type. The Type sets the scene for what the extension can do and what it needs to be utilized. Some extension types can be made purely via the manifest, like a section or menu item. Other types require files, like a JavaScript file containing a Web Component, like a custom property editor.
 
-The abilities of the extensions rely on the specific extension type. The Type sets the scene for what the extension can do and what it needs to be utilized. Some extension types can be made purely via the manifest. Other types require files, like a JavaScript file containing a Web Component.
+### Required Manifest properties
+A minimal Extension Manifest looks like this (in JSON formatting):
 
-```typescript
+```json
 {
-    type: '...',
-    alias: 'my.customization',
-    name: 'My customization'
-    ...
-};
+    "type": "...",
+    "alias": "my.customization",
+    "name": "My customization"
+}
 ```
 
-The required fields of any Extension Manifest are:
+These fields are all required and have the following meaning:
 
-* `type` — The type defines the purpose of the extension. It is used to determine where the extension will be used.
-* `alias` — This is a unique identifier for this manifest. Prefix it with something that makes your extension unique. Example: `mfc.Dashboard.Overview` .
-* `name` — This is a representational name of this manifest; It does not need to be unique, but this can be beneficial when debugging extensions. Example: `My Fictive Company Overview Dashboar` .
-
-### Additional Manifest features
+* `type` — The type defines the purpose of the extension. Umbraco has many [extension types](../extension-types) available.
+* `alias` — This is a unique identifier for this manifest. Prefix it with something that makes your extension unique. For example: _FictiveCompany.MyProject.Dashboard.Overview_.
+* `name` — This is a representational name of this manifest; It does not need to be unique, but this can be beneficial when debugging extensions. This name also shows up in the Extensions Insights in the backoffice of Umbraco. For example: _My Fictive Company Overview Dashboard_.
 
+### Additional Manifest properties
 Most extension types support the use of the following generic features for their Manifest:
 
-* `weight` - Define a weight to determine the importance or visual order of this extension. A higher weight gives a more prominent position.
-* `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.md).
-* `kind` - Define a kind-alias of which this manifest should be based upon. Kind acts like a preset for your manifest. [Extension Kinds](../extension-kind.md).
+* `weight` - Define a weight to determine the importance or visual order of this extension. A higher weight gives a more prominent position. For instance, for a dashboard it determines it's order between other dashboards.
+* `overwrites` - If replacing an existing extension, this define one or more Extension Aliases that this extension should replace. Read more in [Replace, Exclude or Unregister extensions](replace-exclude-or-unregister.md).
+* `conditions` - Define one or more conditions that must pass for the extension to become available. For instance, don't show a section if you don't have the proper rights. Read more in [Extension Conditions](../extension-conditions.md). 
+* `kind` - Some extension types can reference a predefined Kind. By specifying a Kind, the manifest inherits the Kind's properties. This allows for reuse of predefined settings. See [Extension Kind](../extension-kind.md).
+* `meta` - Many Extension Types require additional information declared as part of a `meta` field. It depends on the extension what is required. For instance label and icon of a menu item.
 
-Many of the Extension Types require additional information declared as part of a `meta` field.
+For more information, see an overview of all possible [Extension Types](../extension-types/) and their requirements.
 
-## Type intellisense
 
+---- Below should be moved or removed, because it requires too much context for this file -----
+
+## Type intellisense
 It is recommended to make use of the Type IntelliSense that we provide.
 
 When writing your Manifest in TypeScript, you should use the Type `UmbExtensionManifest`. See the article on [Development Setup](../../development-flow/) to ensure you have Types correctly configured.

16/umbraco-cms/customizing/extending-overview/extension-registry/extension-registry.md renamed to 16/umbraco-cms/customizing/extending-overview/extension-registry/register-extensions.md

@@ -4,7 +4,7 @@ description: >-
   registering an Extension via an Extension Manifest.
 ---
 
-# Register an Extension
+# Register extensions
 
 Whether you're looking to make a single correction or a package, it is done via a file on the server that we call Umbraco Package JSON. This will be your starting point.