creating-plugins

You can scaffold a complete EmDash plugin by defining the descriptor shape and exports, then implementing content lifecycle hooks, data storage schemas, API routes, admin UI, and Portable Text block types end-to-end.

The standard EmDash plugin architecture requires a descriptor shape, entrypoints, and exports. It combines content lifecycle hooks, storage access, admin UI, API routes, and Portable Text blocks under trusted or sandboxed execution models.

Yes, you can extend an existing EmDash plugin by adding new Portable Text block types. The scaffolding process supports extending current plugins with additional capabilities like custom blocks, API routes, or admin UI pages.

Yes, EmDash plugin development supports both trusted and sandboxed execution environments. The architecture provides specific guidance for storage access and publishing workflows within these execution boundaries.

The best way to add admin UI pages and REST endpoints is to scaffold them using the standard EmDash plugin format. This ensures proper integration with the plugin's hooks, storage schemas, and overall architecture.

You need the native format when your EmDash plugin requires specific execution constraints or integrations not covered by the standard format. The scaffolding process provides clear guidance for choosing between standard and native formats.