umbraco-preview-app-provider
Implement preview app providers in Umbraco backoffice using official docs
What this skill does
# Umbraco Preview App Provider
## What is it?
Preview App Providers add custom items to the preview window menu in Umbraco. When content editors preview their content, these apps appear in the preview menu allowing additional functionality like device simulation, accessibility checks, SEO analysis, or other preview-related tools.
## Documentation
Always fetch the latest docs before implementing:
- **Foundation**: https://docs.umbraco.com/umbraco-cms/customizing/foundation
- **Extension Registry**: https://docs.umbraco.com/umbraco-cms/customizing/extending-overview/extension-registry
- **Umbraco Element**: https://docs.umbraco.com/umbraco-cms/customizing/foundation/umbraco-element
## Related Foundation Skills
- **Umbraco Element**: Base class for creating UI components
- Reference skill: `umbraco-umbraco-element`
- **Context API**: When accessing preview state
- Reference skill: `umbraco-context-api`
## Workflow
1. **Fetch docs** - Use WebFetch on the URLs above
2. **Ask questions** - What preview functionality? What UI?
3. **Generate files** - Create manifest + element based on latest docs
4. **Explain** - Show what was created and how to test
## Minimal Examples
### Manifest (manifests.ts)
```typescript
import type { ManifestPreviewAppProvider } from '@umbraco-cms/backoffice/extension-registry';
export const manifests: Array<ManifestPreviewAppProvider> = [
{
type: 'previewApp',
alias: 'My.PreviewApp',
name: 'My Preview App',
element: () => import('./my-preview-app.element.js'),
},
];
```
### Element Implementation (my-preview-app.element.ts)
```typescript
import { html, customElement, state } from '@umbraco-cms/backoffice/external/lit';
import { UmbLitElement } from '@umbraco-cms/backoffice/lit-element';
@customElement('my-preview-app')
export class MyPreviewAppElement extends UmbLitElement {
@state()
private _isActive = false;
override render() {
return html`
<uui-box headline="My Preview Tool">
<p>Custom preview functionality</p>
<uui-button
look=${this._isActive ? 'primary' : 'default'}
@click=${this.#toggle}
>
${this._isActive ? 'Disable' : 'Enable'}
</uui-button>
</uui-box>
`;
}
#toggle() {
this._isActive = !this._isActive;
// Apply your preview functionality
this.#applyPreviewMode(this._isActive);
}
#applyPreviewMode(active: boolean) {
// Access the preview iframe or apply styles
const previewFrame = document.querySelector('iframe.preview-frame');
if (previewFrame && active) {
// Apply custom preview mode
}
}
}
export default MyPreviewAppElement;
```
### Device Simulator Example
```typescript
import { html, customElement, state } from '@umbraco-cms/backoffice/external/lit';
import { UmbLitElement } from '@umbraco-cms/backoffice/lit-element';
@customElement('device-preview-app')
export class DevicePreviewAppElement extends UmbLitElement {
@state()
private _selectedDevice = 'desktop';
private _devices = [
{ name: 'desktop', width: '100%', label: 'Desktop' },
{ name: 'tablet', width: '768px', label: 'Tablet' },
{ name: 'mobile', width: '375px', label: 'Mobile' },
];
override render() {
return html`
<uui-box headline="Device Preview">
${this._devices.map(
(device) => html`
<uui-button
look=${this._selectedDevice === device.name ? 'primary' : 'default'}
@click=${() => this.#selectDevice(device)}
>
${device.label}
</uui-button>
`
)}
</uui-box>
`;
}
#selectDevice(device: { name: string; width: string }) {
this._selectedDevice = device.name;
// Dispatch event to resize preview
this.dispatchEvent(
new CustomEvent('preview-resize', {
detail: { width: device.width },
bubbles: true,
composed: true,
})
);
}
}
export default DevicePreviewAppElement;
```
## Interface Reference
```typescript
interface ManifestPreviewAppProvider extends ManifestElement {
type: 'previewApp';
}
```
## Best Practices
- Keep the UI compact as it appears in a menu
- Provide clear enable/disable states
- Consider the preview context and available iframe
- Use appropriate icons for quick recognition
That's it! Always fetch fresh docs, keep examples minimal, generate complete working code.
Related 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.