umbraco-collection

Build a custom Umbraco backoffice collection by implementing the collection context, element, repository, data source, and view components. This structure renders entity lists with built-in selection, pagination, filtering, and actions without reinventing the UI logic.

The repository pattern for Umbraco collections uses the UmbCollectionRepository contract with a dedicated data source. This data source fetches items from an HTTP API and returns both items and total counts to ensure proper paging behavior in the backoffice list view.

Register a table view and actions by defining extension manifests tied to your specific collection alias. You must register the collection, view, and action manifests together so the Umbraco backoffice can correctly render and operate the list UI.

Yes, you can use TypeScript and Lit to create custom list UIs in the Umbraco backoffice. The Skill guides you through building the collection element and view components using these technologies alongside the required extension manifests.

The best way to scale a repository-backed list UI is to align with official Umbraco documentation and study the built-in CMS repository example. This production pattern ensures your collection handles pagination and bulk actions consistently at scale.

Your Umbraco collection table view may not display items if the data source does not return the total count alongside the items array. Proper UmbCollectionRepository implementation requires both values to calculate and render pagination accurately.