creating-widgets

StickerNest widget creation requires defining manifest fields (id, name, version, kind, entry, inputs/outputs), scaffolding HTML or TypeScript templates, and wiring Protocol v3.0 messaging for WidgetAPI communication before registering the widget in the built-in registry.

Inline HTML widgets are created directly in the src/widgets/builtin directory, while React component widgets are developed in dedicated subdirectories under src/widgets. Both approaches require manifest creation and registration in the built-in registry to function within the runtime.

Registering a custom widget in the StickerNest built-in registry requires completing the manifest with mandatory fields (id, name, version, kind, entry, inputs/outputs) and ensuring proper WidgetAPI communication via Protocol v3.0 before adding it to the runtime registry.

StickerNest widget development requires manifests containing id, name, version, kind, entry, and inputs/outputs fields. These fields define the widget's identity, type, and communication contract for proper Protocol v3.0 wiring and registry integration.

Yes, you can use TypeScript to build interactive StickerNest dashboard widgets by following the React component pattern in src/widgets subdirectories. This approach supports Protocol v3.0 messaging and WidgetAPI communication for reusable UI blocks.

WidgetAPI communication failures typically stem from incomplete manifest fields (id, name, version, kind, entry, inputs/outputs) or incorrect Protocol v3.0 wiring. Ensure the manifest is fully defined and the widget is properly registered in the built-in registry.