umbraco-entry-point

To create an Umbraco backoffice entry point, you generate an umbraco-package.json manifest and an index.ts file using @umbraco-cms/backoffice/extension-api types to wire initialization logic.

Dynamic extension registration in the Umbraco backoffice allows you to register UI extensions at runtime during startup initialization via the extension registry, rather than statically defining them in the manifest.

You add cleanup logic for Umbraco backoffice startup initialization by implementing the onUnload lifecycle hook within your entry point TypeScript code to safely tear down features.

Yes, implementing Umbraco backoffice entry points uses TypeScript to map the correct JS entry and apply @umbraco-cms/backoffice/extension-api types for onInit and onUnload lifecycle hooks.

Yes, the workflow uses WebFetch to pull the latest official guidance for Umbraco backoffice entry points, Foundation concepts, and the Extension Registry before generating the manifest.

The onUnload hook handles teardown for Umbraco extensions, but you must ensure dynamic extension registration via the extension registry is properly managed to avoid lingering UI references during backoffice startup initialization.