At some point in a multi-site Umbraco project, someone creates a "Global" or "Shared" content node to hold whatever multiple sites need in common, and it never stops growing. Six months later it's holding navigation overrides, campaign banners some sites don't use, and properties nobody remembers the purpose of. This isn't really a technical failure, it's what happens when a single-site content model gets stretched across multiple sites without anyone deciding what "shared" actually means. Getting the structure right from the start, across content, media, permissions and search, keeps the tree something editors can still read a year later.
Read the postJust got back from vacation. For the first time in ages, I left my laptop behind. No Visual Studio. No migrations. No coding. No “Can you just…?” It felt great to unplug. I soaked up the sun, enjoyed doing nothing productive, and had a few beers. And somehow, my mind still wandered back to work. Maybe stepping away gave me the space to reflect on the last couple of years.
In a few days, I'm packing my bags for a holiday, and for the first time in ages, my laptop will stay home. No Visual Studio. No Docker containers spinning up in the background. No sneaky last-minute Git commits. And, honestly, no more of those "let me just fix this one bug real quick" moments.
There are flashy features that get everyone excited—new editors, AI integrations, shiny dashboards. They look great in a keynote and are fun to show off. But then there are those features that, quietly, just fix long-standing headaches. For me, the new Library and Elements in Umbraco 18 are absolutely in that second group.