What you will see in this video
We've been rebuilding the dotCMS administration screens on a single shared front-end foundation — Angular 22 with PrimeNG 21 — one screen at a time. Several are now complete and in the product. This video walks through what changed in the recent set of screens we released: Tags and Categories, the two screens most content teams touch daily, and the four diagnostic and administrative tools — ES Search, the Query Tool, Velocity Playground, and Plugins, as well as the Publishing Queue tool.
You'll see server-side paging and persistent selection in Tags, inline editing that saves without a page reload in Categories, a Monaco-based split-pane editor with shareable query links and cURL/fetch export in ES Search and the Query Tool, Velocity syntax highlighting and script history in the Playground, and a Plugins table that updates from platform events rather than polling. Along the way, we cover why interface consistency is a measurable cost rather than a matter of taste, and what these rebuilds are meant to produce: shorter orientation time on unfamiliar screens, lower training cost for new team members, and fewer errors where errors carry consequences.
No action required — there's no migration to run and no configuration to change. The rebuilt screens are already in the product.