Skip to content

Commit 2fae8ed

Browse files
Update 16/umbraco-cms/customizing/extending-overview/extension-registry/README.md
Co-authored-by: Richard Jackson <[email protected]>
1 parent 65891de commit 2fae8ed

File tree

1 file changed

+1
-1
lines changed
  • 16/umbraco-cms/customizing/extending-overview/extension-registry

1 file changed

+1
-1
lines changed

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ description: >-
88
The Umbraco backoffice is built with extensibility 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, menus, 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.
99

1010
{% hint style="info" %}
11-
You can see in the backoffice what extensions are registered and to go to Settings > Extensions Insights.
11+
You can see which extensions are registered in the backoffice by going to Settings > Extensions Insights.
1212
{% endhint %}
1313

1414
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.

0 commit comments

Comments
 (0)