Smidge 5 is out after about a year without a release - sorry 'bout that 😅. It moves to .NET 10 and minimal APIs, folds NUglify into the main package, simplifies the package structure, and fixes a race condition that could corrupt bundles under concurrent requests.…
Examine v4.0.0 is out on NuGet after sitting in beta since October 2023. The headline is native faceting, along with taxonomy indexes, deep paging, .NET 8/9/10 support and a lot of replicator work, and it's a drop-in replacement for v3 - which took a fair bit of testing with Umbraco HQ to get right. Here's what's new, what took so long, and what it means now that Umbraco's new search abstraction runs on it.…
Codegarden 2026 talk is now up on YouTube. It's a live demo where I point Copilot CLI at a completely empty Umbraco install and it builds an entire blogging site on stage - schema, templates, styling, content and all - while writing blog posts about its own experience of being built. Here's the video, and the repo so you can run it yourself.…
I've been maintaining Examine for a very long time, and there's always a backlog of performance work I never get to. So I let GitHub Next's agentic workflows do it for me, on a schedule, and it turned into three shipped releases and some genuinely ridiculous hot-path improvements. Here's how it went, with real benchmark numbers.…
A new Examine version 3.3.0 has been released to address a long awaited bug fix for Umbraco websites that use the SyncedFileSystemDirectoryFactory which is the default setting for Umbraco CMS. The bug…
Using the Suggester API with ExamineX and Azure AI Search…
In Umbraco v8, Examine and Lucene are only used for the back office searches, unless you specifically use those APIs for your front-end pages. So can you disable them for your front-end servers?…
Articulate 4.3.0 with support for markdown code snippets and syntax highlighting…
Auto upgrade your Nuget packages with Azure Pipelines or GitHub Actions…
This will generally be a rare thing to do but if you have your reasons to do it, then this is how…In Umbraco there is a valid reason to do this which has to do with how HTTP POSTs are handled for…