You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: 16/umbraco-cms/customizing/extending-overview/extension-types/header-apps.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -13,7 +13,7 @@ Extension authors can create header apps that link to resource both inside and o
13
13
14
14
To create a link-style header app, define a `headerApp` extension in the `umbraco-package.json` file. Be sure to include `meta.label` and `meta.icon` so that your header app appears when you reload the backoffice.
15
15
16
-
If `meta.href` is defined, the header app will function as a link. The link will open in a new tab if the href value is a full url (complete with a protocol scheme, ex: https://), otherwise it will open in the same tab.
16
+
If `meta.href` is defined, the header app will function as a link. Links will open in the same tab, unless the href property includes a protocol scheme (ex: `https://`).
17
17
18
18
Header Apps can also be created using TypeScript. Examples of both approaches are shown below.
Extension authors can also create header apps that have more interactivity than a simple link.
73
+
Extension authors can also create header apps that have more interactivity than a link.
74
74
75
75
By creating a custom component, extension authors can control how the button renders itself and how it behaves when clicked. This allows header apps to control navigation, open modals, or perform other actions.
76
76
@@ -102,7 +102,7 @@ In order for a header app to have some functionality, extension authors will nee
102
102
{% endcode %}
103
103
{% endtab %}
104
104
{% tab title="TypeScript" %}
105
-
*This example assumes that the extension author has transpiled the above TypeScript code into a JavaScript file. The name and location of this file should match the `element` property in the manifest.*
105
+
This example assumes that the extension author has transpiled the above TypeScript code into a JavaScript file. The name and location of the transpiled file should match the `element` property in the package manifest.
0 commit comments