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
description: Example how to work with extension registry
2
+
description: Place single-purpose extensions in the top-level navigation bar, next to the user profile avatar.
3
3
---
4
4
5
5
# Header Apps
6
6
7
-
{% hint style="warning" %}
8
-
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.
9
-
{% endhint %}
10
-
11
-
A header app appears next to the user profile and global search icon on the top-right corner of Umbraco's backoffice.
12
-
13
-
In this article, you can find an example of an extension registry. This example details the creation of a Header App in two ways, similar to how the extension registry can be created:
14
-
15
-
1.[Using a manifest file](header-apps.md#button-header-app-with-manifest).
16
-
2.[Using the JavaScript/TypeScript file](header-apps.md#button-header-app-with-js-ts).
7
+
Header App extensions appear next to the user profile and the global search icon in the top right of Umbraco’s Backoffice. Extension authors can create custom header apps to add globally accessible functionality to the Backoffice.
Extension authors can create header apps that link to resource both inside and outside the backoffice. Header apps can be created using a manifest or using TypeScript.
21
13
22
-
Below you can find an example of how to setup a Header App using the manifest file.
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.
23
15
24
-
1. Follow the [Vite Package Setup](../../development-flow/vite-package-setup.md) to create a header app and name it "`header-app`" when using the guide.
25
-
2. Create a manifest file named `umbraco-package.json` at the root of the `header-app` folder. Here we define and configure our dashboard.
26
-
3. Add the following code to `umbraco-package.json`:
16
+
If `meta.href` is defined, the header app will function as a link. Links will open in the same tab.
* First we define the type which is a `headerApp`. Then we add a unique alias and a name to define the extension UI.
53
-
* Then we can define what kind of extension it is, where in this case we can use a pre-defined element called button.
54
-
* The button requires some metadata: an icon, label of the button (name of the button) and a link which opens once clicked.
64
+
umbExtensionsRegistry.register(manifest);
65
+
```
66
+
{% endcode %}
67
+
{% endtab %}
68
+
{% endtabs %}
55
69
56
-
4. In the `header-app` folder run `npm run build` and then run the project. Then in the backoffice you will see our new Header App extension with **heart icon**:
70
+
## Button Header Apps with deeper interactivity
57
71
58
-
<figure><imgsrc="../../../.gitbook/assets/header-app-example.png"alt=""><figcaption><p>Header App in the Backoffice registered via Manifest File</p></figcaption></figure>
72
+
Extension authors can also create header apps that have more interactivity than a link.
59
73
60
-
## **Button Header App with JS/TS**
74
+
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.
61
75
62
-
Below you can find an example of how to setup a Header App using the TypeScript file.
76
+
For example, this is how the current user header app is able to present a modal when clicked.
63
77
64
-
This is a continuation of the above steps from the **Button Header App with Manifest** example. We will register a new Header App directly from the .ts file.
78
+
<figure><imgsrc="../../../.gitbook/assets/header-apps-custom.png"alt=""><figcaption><p>The current user modal is presented from a header app</p></figcaption></figure>
65
79
66
-
1. Add a reference to the .js file. Update the `umbraco-package.json` with the following:
80
+
In order for a header app to have some functionality, extension authors will need to define behavior by creating a JavaScript or TypeScript component. Once the component has been created, it will need to be registered in the header app's `element` property.
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.
headline: "Would you like to disable all Server Services?",
117
+
content:
118
+
"This action can be undone, but only after all services have stopped.",
119
+
color: "danger",
120
+
confirmLabel: "Disable all services",
121
+
},
122
+
})
123
+
.then(() => {
124
+
console.log("User has approved");
125
+
})
126
+
.catch(() => {
127
+
console.log("User has rejected");
128
+
});
129
+
}
97
130
98
-
const manifest:UmbExtensionManifest= {
99
-
type: "headerApp",
100
-
alias: "My.HeaderApp.Documentation",
101
-
name: "My Header App Documentation",
102
-
kind: "button",
103
-
meta: {
104
-
label: "Hello Documentation",
105
-
icon: "icon-addressbook",
106
-
href: "https://docs.umbraco.com/"
131
+
override render() {
132
+
returnhtml`
133
+
<uui-button
134
+
@click=${this.#handleUserClick}
135
+
look="primary"
136
+
label="Server Services"
137
+
compact
138
+
>
139
+
<uui-icon name="icon-server"></uui-icon>
140
+
</uui-button>
141
+
`;
107
142
}
108
-
};
143
+
}
109
144
110
-
umbExtensionsRegistry.register(manifest);
145
+
{ MyServerServicesHeaderAppElementaselement };
111
146
```
112
147
{% endcode %}
113
-
114
-
3. In the `header-app` folder run `npm run build` and then run the project. Then in the backoffice you will see our new Header App extension with **address book****icon**:
115
-
116
-
<figure><imgsrc="../../../.gitbook/assets/header-app-example-ts.png"alt=""><figcaption><p>Header App in Backoffice registered via ts File</p></figcaption></figure>
0 commit comments