Series
Some posts aren't one-offs — they're a journey through a single idea over several parts. Here they are grouped together, in order.
The design-patterns journey continues on the Xperience platform: startup hygiene, modeling missing data (nullable reference types, the Null Object pattern, the Maybe monad), error handling (the Result monad, centralized exception handling), and content/page type modeling.
The Quick Tips format carried over to the Xperience platform: short, focused posts on localization, performance (CLS and image rendering), custom data fields, and rendering rich text after a form submission.
Open-ended investigations adjacent to core Xperience work — running Xperience inside a .NET Core worker service, debugging queries from a console app, detecting Page Builder mode on a request, and why/how to bring in AlpineJS and Tailwind CSS.
The widget experiments continue on Xperience: how widgets relate to pages, page-specific marketing tags delivered through widgets, and cleaning up unused widget sections.
Short, standalone field notes for everyday Kentico CMS/EMS problems — Azure integration, integration testing, cache key generation, static file fingerprinting, custom page type icons, and more. Less a narrative arc than a running grab-bag of practical fixes, spanning over four years.
Early hands-on experiments with Kentico EMS's then-new MVC Widget feature — where widgets can be used, dynamic views, rendering Form Builder forms without widgets, and sharing widgets across pages.
Early, hands-on coverage of the Kentico Xperience 13 beta as it was still taking shape — Page Builder view components and tag helpers in ASP.NET Core, and the new data access APIs.
A 25-part, 14-month walk through applying classic software design patterns to Kentico 12 MVC development — starting from writing testable code and unit tests, through dependency injection, caching, and application structure, and ending at full solution architecture and MVC widget tips.
A tight, 8-day burst of three posts pushing past Angular's official style guide — the Rule of One, small functions, and symbol/file naming — arguing for stricter conventions than the guide itself recommends.