Some things just hang around on your bucket list forever. You tell yourself, “maybe next year,” but you never actually get around to it. For me, that's always been Codegarden.
Let's be honest—most teams know that accessibility matters. Everybody nods along when it comes up. But as deadlines creep closer and pressure ramps up, accessibility quietly slides out of focus, landing in the “we'll get to it later” pile. And we all know how rare it is to dig into that pile once the release goes live.
Most Umbraco Setups Don't Fail Immediately—They Fail Later
Every new Umbraco project usually starts the same—fresh solution, everyone energized and maybe even a nice architecture diagram. For a couple weeks, life's good. Everything moves quick, flows logically, and things feel buttoned-up.
AI pops up everywhere these days. It’s in editors, IDEs, your browser—and, yes, your CMS. But Umbraco handles AI a bit differently. You won’t find any “magic” buttons or get stuck with one vendor. Instead, you get a thoughtful, flexible setup that actually keeps you in charge. And that’s where things start to get interesting.