Skip to content

Commit 0af7332

Browse files
Luuk PetersLuuk Peters
authored andcommitted
Fixed a link
1 parent a9f2cdb commit 0af7332

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -14,7 +14,7 @@ An Extension Manifest declares a single backoffice extension along with its conf
1414
Some extensions need extra assets, such as a JavaScript file with a Web Component.
1515

1616
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.
17-
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. You can learn more about this when [registering an extension](extension-registry).
17+
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. You can learn more about this when [registering an extension](register-extensions.md).
1818
### Required Manifest properties
1919
A minimal Extension Manifest looks like this:
2020

0 commit comments

Comments
 (0)