umbraco-package-view

Package Views provide custom UI panels for installed packages in Umbraco. They appear in the Packages section and allow package developers to create dedicated configuration or information pages for their packages. When a user clicks on an installed package, the package view is displayed as a modal or panel.

Safety Notice

This listing is imported from skills.sh public index metadata. Review upstream SKILL.md and repository scripts before running.

Copy this and send it to your AI assistant to learn

Install skill "umbraco-package-view" with this command: npx skills add umbraco/umbraco-cms-backoffice-skills/umbraco-umbraco-cms-backoffice-skills-umbraco-package-view

Umbraco Package View

What is it?

Package Views provide custom UI panels for installed packages in Umbraco. They appear in the Packages section and allow package developers to create dedicated configuration or information pages for their packages. When a user clicks on an installed package, the package view is displayed as a modal or panel.

Documentation

Always fetch the latest docs before implementing:

Related Foundation Skills

Umbraco Element: Base class for creating UI components

  • Reference skill: umbraco-umbraco-element

Modals: Package views are displayed in modal context

  • Reference skill: umbraco-modals

Workflow

  • Fetch docs - Use WebFetch on the URLs above

  • Ask questions - What package? What configuration options?

  • Generate files - Create manifest + element based on latest docs

  • Explain - Show what was created and how to test

Minimal Examples

Manifest (manifests.ts)

import type { ManifestPackageView } from '@umbraco-cms/backoffice/packages';

export const manifests: Array<ManifestPackageView> = [ { type: 'packageView', alias: 'My.PackageView', name: 'My Package View', element: () => import('./my-package-view.element.js'), meta: { packageName: 'My Package', }, }, ];

Element Implementation with Lit (my-package-view.element.ts)

import { html, customElement } from '@umbraco-cms/backoffice/external/lit'; import { UmbLitElement } from '@umbraco-cms/backoffice/lit-element'; import { UmbModalBaseElement } from '@umbraco-cms/backoffice/modal';

@customElement('my-package-view') export class MyPackageViewElement extends UmbModalBaseElement { override render() { return html` <umb-body-layout headline="My Package"> <uui-box> <h2>Package Configuration</h2> <p>Configure your package settings here.</p>

      &#x3C;uui-form>
        &#x3C;uui-form-layout-item>
          &#x3C;uui-label slot="label">Setting 1&#x3C;/uui-label>
          &#x3C;uui-input>&#x3C;/uui-input>
        &#x3C;/uui-form-layout-item>
      &#x3C;/uui-form>
    &#x3C;/uui-box>

    &#x3C;div slot="actions">
      &#x3C;uui-button @click=${this.#onClose} label="Close">&#x3C;/uui-button>
      &#x3C;uui-button look="primary" @click=${this.#onSave} label="Save">&#x3C;/uui-button>
    &#x3C;/div>
  &#x3C;/umb-body-layout>
`;

}

#onClose() { this.modalContext?.reject(); }

#onSave() { // Save logic here this.modalContext?.submit(); } }

export default MyPackageViewElement;

Vanilla JS Element (my-package-view.js)

const template = document.createElement('template'); template.innerHTML = ` <umb-body-layout> <h1 slot="header">My Package</h1>

&#x3C;uui-box>
  &#x3C;p>Package information and settings&#x3C;/p>
&#x3C;/uui-box>

&#x3C;uui-action-bar slot="footer-info">
  &#x3C;uui-button look="primary" type="button">Close&#x3C;/uui-button>
&#x3C;/uui-action-bar>

</umb-body-layout> `;

export default class MyPackageViewElement extends HTMLElement { constructor() { super(); this.attachShadow({ mode: 'open' }); this.shadowRoot.appendChild(template.content.cloneNode(true));

this.shadowRoot.querySelector('uui-button').addEventListener('click', this.onClick.bind(this));

}

onClick() { this.modalContext.close(); } }

customElements.define('my-package-view', MyPackageViewElement);

Interface Reference

interface ManifestPackageView extends ManifestElement { type: 'packageView'; meta: MetaPackageView; }

interface MetaPackageView { packageName: string; // Must match the package name in umbraco-package.json }

Package Integration

The package view is linked by matching meta.packageName with your package's name in umbraco-package.json :

{ "$schema": "../../umbraco-package-schema.json", "name": "My Package", "version": "1.0.0", "extensions": [ { "type": "packageView", "alias": "My.PackageView", "name": "My Package View", "element": "/App_Plugins/MyPackage/my-package-view.js", "meta": { "packageName": "My Package" } } ] }

That's it! Always fetch fresh docs, keep examples minimal, generate complete working code.

Source Transparency

This detail page is rendered from real SKILL.md content. Trust labels are metadata-based hints, not a safety guarantee.

Related Skills

Related by shared tags or category signals.

Coding

umbraco-openapi-client

No summary provided by upstream source.

Repository SourceNeeds Review
Coding

umbraco-skill-code-analyzer

No summary provided by upstream source.

Repository SourceNeeds Review
General

umbraco-backoffice

No summary provided by upstream source.

Repository SourceNeeds Review
General

umbraco-dashboard

No summary provided by upstream source.

Repository SourceNeeds Review