My Umbraco journey didn’t begin with a grand plan — it began with a simple support ticket.
Back then, I was working at my former agency ClerksWell as a support developer. My day-to-day tasks were mostly fixing bugs, handling small change requests, and keeping existing client sites running smoothly. My background was in Xamarin mobile app development, so stepping into the world of CMS platforms was completely new to me. Honestly, I had no clue what Umbraco even was.
One day, I was assigned my first Umbraco ticket. I opened the project solution, looked at the folder structure, the views, the backoffice… and thought,
“Okay, what is this?”
That moment — confused, curious, and slightly intimidated — was the true beginning.
At first, I stuck to the simple things: fixing broken links, adjusting templates, updating content models, making small frontend tweaks. But with every ticket, I learned a little more. What started as debugging someone else’s code slowly grew into understanding the architecture, and then into building features from scratch.
That was the turning point. Suddenly, the entire ecosystem clicked. The flexibility, the freedom, the clean architecture — Umbraco didn’t feel like a CMS anymore, it felt like a developer’s playground.
From there, everything changed.
I went from:
fixing bugs → to implementing new components
small tweaks → to leading features
supporting existing sites → to building full websites in Umbraco
The more I learned, the more I realized how powerful, elegant, and developer-friendly Umbraco really is. And that was just the technical side — the community came later, and that changed everything again.