umbraco-dynamic-root

Umbraco dynamic root origins allow content pickers to start from context-derived nodes like the current page or site root instead of fixed nodes. You configure them via TypeScript manifests and map the originAlias to a C# backend implementation that resolves the starting node at runtime.

Dynamic root query steps are navigation rules applied after selecting an origin in Umbraco content pickers, such as finding the nearest ancestor of a type or traversing children. They are defined via TypeScript manifests and executed by matching queryStepAlias implementations in C#.

You implement a custom dynamic root origin and query step by defining the required TypeScript manifest types for the backoffice and providing corresponding C# backend classes that resolve the picker origin and execute the query based on the current editing context.

Yes, C# backend classes are required for Umbraco dynamic root configurations to map the originAlias and queryStepAlias so the picker configuration resolves correctly and executes the context-aware navigation rules at runtime.

Use dynamic root origins instead of fixed content picker starting points when editors need pickers to start and traverse content based on the current editing context, page context, or site structure rather than rigid, predefined nodes.