umbraco-manifest-picker
Use umb-input-manifest to pick registered extensions in Umbraco backoffice
What this skill does
# Umbraco Manifest Picker
## What is it?
The `<umb-input-manifest>` component provides a picker UI for selecting registered extensions from the Umbraco extension registry. It allows users to pick from any extension type (workspaces, dashboards, property editors, etc.) and returns the selected manifest. This is useful for configuration UIs where users need to reference other extensions.
## Documentation
Always fetch the latest docs before implementing:
- **Extension Registry**: https://docs.umbraco.com/umbraco-cms/customizing/extending-overview/extension-registry
- **Foundation**: https://docs.umbraco.com/umbraco-cms/customizing/foundation
## Reference Example
The Umbraco source includes a working example:
**Location**: `/Umbraco-CMS/src/Umbraco.Web.UI.Client/examples/manifest-picker/`
This example demonstrates a dashboard that lets users browse and select extensions by type.
## Related Foundation Skills
- **Extension Registry**: For understanding how extensions are registered
- Reference skill: `umbraco-extension-registry`
- **Umbraco Element**: For creating picker UIs
- Reference skill: `umbraco-umbraco-element`
## Workflow
1. **Fetch docs** - Use WebFetch on the URLs above
2. **Ask questions** - What extension types to pick? How to use selection?
3. **Generate files** - Create element with manifest picker
4. **Explain** - Show what was created and how selection works
---
## Basic Usage
```typescript
import { html, customElement, state } from '@umbraco-cms/backoffice/external/lit';
import { UmbLitElement } from '@umbraco-cms/backoffice/lit-element';
import type { UmbInputManifestElement } from '@umbraco-cms/backoffice/components';
@customElement('my-manifest-picker-example')
export class MyManifestPickerExampleElement extends UmbLitElement {
@state()
private _selectedManifest = '';
#onChange(event: { target: UmbInputManifestElement }) {
const selectedManifest = event.target.value;
this._selectedManifest = selectedManifest?.value ?? '';
}
override render() {
return html`
<uui-box>
<umb-property-layout label="Select a workspace">
<div slot="editor">
<umb-input-manifest
.extensionType=${'workspace'}
@change=${this.#onChange}
></umb-input-manifest>
</div>
</umb-property-layout>
${this._selectedManifest
? html`<p>Selected: <code>${this._selectedManifest}</code></p>`
: ''}
</uui-box>
`;
}
}
```
---
## Dynamic Extension Type Selection
```typescript
import { html, customElement, state, when, nothing } from '@umbraco-cms/backoffice/external/lit';
import { umbExtensionsRegistry } from '@umbraco-cms/backoffice/extension-registry';
import { UmbLitElement } from '@umbraco-cms/backoffice/lit-element';
import type { UmbInputManifestElement } from '@umbraco-cms/backoffice/components';
import type { UUISelectEvent } from '@umbraco-cms/backoffice/external/uui';
interface Option {
name: string;
value: string;
selected: boolean;
}
@customElement('my-extension-browser')
export class MyExtensionBrowserElement extends UmbLitElement {
#options: Option[] = [];
@state()
private _selectedExtensionType = 'dashboard';
@state()
private _selectedManifest = '';
constructor() {
super();
// Build list of available extension types from registry
this.observe(umbExtensionsRegistry.extensions, (extensions) => {
const types = [...new Set(extensions.map((x) => x.type))];
this.#options = types.sort().map((x) => ({
name: x,
value: x,
selected: x === this._selectedExtensionType,
}));
});
}
#onTypeSelect(event: UUISelectEvent) {
this._selectedManifest = '';
this._selectedExtensionType = event.target.value as string;
}
#onManifestChange(event: { target: UmbInputManifestElement }) {
const selectedManifest = event.target.value;
this._selectedManifest = selectedManifest?.value ?? '';
}
override render() {
return html`
<uui-box>
<umb-property-layout label="Extension Type">
<uui-select
slot="editor"
label="Select type"
placeholder="Select type..."
.options=${this.#options}
@change=${this.#onTypeSelect}
></uui-select>
</umb-property-layout>
${when(
this._selectedExtensionType,
() => html`
<umb-property-layout
label="Select Extension"
description="Pick a ${this._selectedExtensionType}"
>
<div slot="editor">
<umb-input-manifest
.extensionType=${this._selectedExtensionType}
@change=${this.#onManifestChange}
></umb-input-manifest>
</div>
</umb-property-layout>
`,
() => nothing
)}
${when(
this._selectedManifest,
() => html`
<umb-property-layout label="Selected Manifest">
<div slot="editor">
<code>${this._selectedManifest}</code>
</div>
</umb-property-layout>
`,
() => nothing
)}
</uui-box>
`;
}
}
```
---
## Getting All Extension Types
```typescript
import { umbExtensionsRegistry } from '@umbraco-cms/backoffice/extension-registry';
// In your element constructor
this.observe(umbExtensionsRegistry.extensions, (extensions) => {
// Get unique extension types
const types = [...new Set(extensions.map((x) => x.type))];
console.log('Available types:', types);
// Filter by type
const dashboards = extensions.filter((x) => x.type === 'dashboard');
console.log('Dashboards:', dashboards);
// Get extension by alias
const specific = extensions.find((x) => x.alias === 'Umb.Dashboard.Welcome');
console.log('Specific extension:', specific);
});
```
---
## Common Extension Types
| Type | Description |
|------|-------------|
| `dashboard` | Section dashboards |
| `workspace` | Entity workspaces |
| `workspaceView` | Views within workspaces |
| `workspaceAction` | Workspace action buttons |
| `propertyEditorUi` | Property editor UIs |
| `propertyEditorSchema` | Property editor schemas |
| `entityAction` | Context menu actions |
| `tree` | Navigation trees |
| `treeItem` | Tree item renderers |
| `section` | Backoffice sections |
| `sectionView` | Section views |
| `headerApp` | Header bar apps |
| `modal` | Modal dialogs |
| `condition` | Extension conditions |
---
## UmbInputManifest Properties
| Property | Type | Description |
|----------|------|-------------|
| `extensionType` | `string` | The type of extension to pick from |
| `value` | `ManifestBase \| undefined` | The selected manifest |
---
## Events
| Event | Detail | Description |
|-------|--------|-------------|
| `change` | `{ target: UmbInputManifestElement }` | Fired when selection changes |
---
## Accessing Selected Manifest Data
```typescript
#onManifestChange(event: { target: UmbInputManifestElement }) {
const manifest = event.target.value;
if (manifest) {
console.log('Alias:', manifest.alias);
console.log('Name:', manifest.name);
console.log('Type:', manifest.type);
console.log('Full manifest:', manifest);
}
}
```
---
## Use Cases
1. **Configuration screens** - Let users select which dashboard/workspace to show
2. **Extension management** - Browse and inspect registered extensions
3. **Dynamic routing** - Configure navigation targets
4. **Condition configuration** - Select conditions to apply
5. **Package development** - Test extension registration
---
## Best Practices
1. **Clear selectRelated in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.