Issue N^o 130

Seb bids a final bittersweet and proper farewell to our.umbraco.com after 15 years as its main maintainer, tracing its path from a Yahoo Group to YAF to the Our we all bookmarked first. It's part send-off and part community history lesson — Karmageddon, tabgate, and the final karma leaderboard all make an appearance!

Robert has shipped a Kanban and Calendar view for Umbraco content collections — drag cards between lanes with safe-publish, plus a calendar view with real-time sync so editors see each other's changes live. We love this genuinely useful editorial upgrade for anyone managing structured, status-driven content!

A small, practical fix from Nathaniel for an annoyance most of us have hit: docs.umbraco.com defaulting to the latest version when you're deep in an older one. His Tampermonkey userscript pins the docs to whatever version you're actually working on - and not only does this article show you how to use it, it shows you how he made it!

The real reason to move to Umbraco 17 isn't the EOL clock — it's the new MCP Server and expanded Management API, which let AI review SEO, accessibility, and content quality during the editorial workflow instead of after publish. Chris's post is well worth a read if you've been thinking about upgrades purely as a support-deadline problem.

Tim makes the case — backed by his own still-running Umbraco v4 site — that end-of-life is a date on a vendor's calendar, not a fact about your business. He walks through how to tell a genuinely managed risk apart from plain neglect, which is an interesting thought-piece on how and why we choose to upgrade our projects.