umbraco-backoffice

Umbraco backoffice extensions require combining specific extension types with correct conditions, meta, and entityType wiring to ensure proper UI placement. Using structured blueprints guides this combination to build reliable custom sections, menus, and workspaces.

Creating a custom section and hierarchical tree in Umbraco involves combining multiple backoffice extension types into a functional feature. Example-driven blueprints like tree-example demonstrate how to correctly connect these components into a working workspace.

Validating Umbraco extensions requires running npm run build for compile-time checks, spawning the umbraco-extension-reviewer for automated code review, and performing mandatory browser checks to confirm correct UI behavior.

Umbraco tree navigation issues often stem from missing or incorrect wiring between extension types. Enforcing pre-build planning and following mandatory development workflows prevents these errors by ensuring correct conditions and entityType mappings before compilation.

Full-stack CRUD operations within an Umbraco workspace are achievable when backoffice extensions are paired with controller APIs. Complete blueprints like notes-wiki demonstrate connecting workspace components to backend controllers for entity management.

A pre-build planning step is mandatory before developing Umbraco backoffice extensions. Reading PRE-BUILD-PLANNING.md ensures correct extension type selection and wiring strategy, preventing structural errors before code compilation begins.