What problem does it solve?
It solves the confusion and maintenance risk of mixing backoffice UI logic with direct data access by giving you a consistent repository/data-source structure.
Core Features & Use Cases
- Clean separation of concerns: isolate business operations in a repository while delegating actual I/O to a data source.
- Scalable integration patterns: plug repositories into server, offline, store, and Signal-R backed approaches without changing consumers.
- Auth-safe API access guidance: provides a hard rule to avoid raw fetch calls and use the generated OpenAPI client with Umbraco auth context.
Use case examples:
- Implement a CRUD repository for a custom backoffice feature that needs predictable data operations and small, context-window-friendly responses.
- Create a tree repository that exposes root items, children, and ancestors while hiding the underlying data mechanism.
- Coordinate repository + data source + store + context so UI components only observe state changes.
Quick Start
Use the umbraco-repository-pattern skill to design a repository, data source, and context for your custom backoffice data model, following the provided documentation links and the rule to use the generated OpenAPI client for authenticated calls.