Our.Umbraco.ContentDashboard 18.0.0

Content Dashboard for Umbraco

Who is responsible for which pages, and what is about to change.

On a site with more than a couple of editors, two questions come up constantly and Umbraco answers neither directly: which pages am I responsible for? and who looked after all of this before they left? Content Dashboard adds three tabs to the Content section that answer both.

Every page you own, newest edits first. Administrators get the Owner filter as well, so they can look at anyone's list — or select rows and hand them over.

Anything with a pending publish or unpublish date, soonest first, so a release never arrives unnoticed.

Requirements

• Umbraco 18.x (this package is deliberately pinned to [18.2.0,19.0.0))
• .NET 10

Versions

The package major follows the Umbraco major, so the version tells you which one you need.

1.0.0 was the first Umbraco 18 release, before this scheme; 18.0.0 is the same package.

Install

dotnet add package Our.Umbraco.ContentDashboard

On Umbraco 17, ask for the 17.x line explicitly - a plain install picks the newest version, which targets Umbraco 18:

dotnet add package Our.Umbraco.ContentDashboard --version "17.*"

No configuration and nothing to register. Build, run, and open the Content section.

What you get

Administrators also get an Owner filter on the first two tabs, so they can look at anyone's list.

What "owner" means

Umbraco has no separate owner concept, so this package treats the built-in creator — the Created by field on a page's Info tab — as the owner. Transferring ownership rewrites that field, and the change is immediately visible in the standard Umbraco UI. There is no parallel bookkeeping to drift out of step.

Transfers deliberately do not touch the page's last edited date or its writer. Going through Umbraco's normal save would stamp both, which would make every transferred page look freshly edited and destroy the "how stale is this page?" signal that the My Content tab exists to show. So a transfer changes ownership and nothing else.

Every transfer is written to the Umbraco audit log.

Known limitations

• Load balancing. After a transfer, the cache clear is local to the server that handled the request. Other servers keep showing the previous owner until their cache expires or the app recycles.
• Ownership is the creator field. If your editorial process already means something different by "created by", this package will mean that too.
• The package is consume-only — it has no configuration and no extension points.

Localization

The whole UI is localized and ships with English and Dutch. Adding a language is one TypeScript file: see docs/architecture.md. Dates and counts follow the backoffice language, not the browser's.

Documentation

• Development setup — clone, run, and work on the package
• How it works — the design decisions behind it
• Changelog

License

MIT. See LICENSE.