https://community.umbraco.comRecent blog posts from members of the Umbraco community.enhttps://www.wearediagram.com/blog/why-umbraco-17-is-more-than-an-end-of-life-escapedcacea68-432d-451d-9d86-f989ec58f85cWed, 29 Jul 2026 15:40:39 GMTDiagramhttps://owain.codes/blog/2026/july/a-reusable-deploy-pipeline-for-umbraco-cloud/357b617d-1055-4710-bd50-02a3e26b2131Mon, 27 Jul 2026 00:00:00 GMTCreate a reusable deploy pipeline for Umbraco CloudOwain Williamshttps://blog.tsd.digital/assume-your-software-will-outlive-its-end-of-life/a2be94ef-6ff8-4be6-9fcc-aedca2cf94dcMon, 20 Jul 2026 00:00:00 GMTWe still run an Umbraco v4 site, on purpose. End-of-life is a date on the vendor's calendar, not a fact about your customer's business. Why the version you ship is the one worth designing for, and how to tell a managed risk from plain neglect.Tim Gaunthttps://owain.codes/blog/2026/july/build-a-custom-umbraco-automate-action/5deec284-a4d4-4555-a824-f05d6f8b2de8Fri, 17 Jul 2026 00:00:00 GMTCreating a custom action in Umbraco Automate to pull tags from a blog and display them as hashtags in social connections.Owain Williamshttps://www.dynamicdave.nl/blog/no-laptop-still-learning-an-umbraco-developers-holiday-checklist/c429075a-517e-44ab-88fd-c9d3cc561671Tue, 14 Jul 2026 22:00:00 GMTIn 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.And to be completely honest? I can't wait.But that doesn't mean I'm putting my developer brain entirely on pause. If you've been working with Umbraco for years—like me—you know it's much more than a tool you clock in and out of each day. It's a community, an ecosystem, and, let's be real, a craft that's always changing. Even if I don't write a line of code, there's no shortage of ways to stay inspired and come back from my break with fresh perspectives.Here's how I'm planning to keep the inspiration flowing while away.Dave Jonkerhttps://www.nevitech.co.uk/blog/migrating-umbraco-13-to-umbraco-17-on-umbraco-cloud/b517358b-24b5-4247-9e52-a5b64d48e0e1Fri, 10 Jul 2026 23:00:00 GMTA developer guide to upgrading an Umbraco 13 site to Umbraco 17 on Umbraco Cloud by migrating locally and deploying into a fresh Cloud project, covering the full sequence through to a low downtime go live.Justin Nevillehttps://www.nathanielnunes.com/blog/pin-umbraco-docs-version-tampermonkey661f6699-ede1-4029-9fac-bcb2d92676b7Fri, 10 Jul 2026 11:30:00 GMTHere is a Tampermonkey userscript that pins docs.umbraco.com to whatever version you are actually working on.Nathaniel Nuneshttps://cornehoskam.com/posts/how-i-upgraded-umbraco-13-to-17-in-less-than-two-hours/d2e4ca0c-4092-4f75-a558-dd1e52655c98Fri, 10 Jul 2026 00:00:00 GMTI jumped straight from Umbraco 13 to 17 on Umbraco Cloud in under two hours, TinyMCE to Tiptap and all. Here's the full checklist of what I touched.Corné Hoskamhttps://dev.to/mpisaacs/codegarden-2026-a-little-late-because-it-gave-me-something-to-build-2em6b2cd460a-a8de-4904-a420-b0b99067bbf3Thu, 09 Jul 2026 00:00:00 GMTA few weeks ago I was in Copenhagen for my first Codegarden, and one quiet thought has stuck with me...Mike Isaacshttps://skttl.dev/blog/go-to-partial/932c9d2f-a2d6-4d62-b7d6-32c2644370b3Thu, 09 Jul 2026 00:00:00 GMTA small VS Code extension that adds Go to Definition and live diagnostics for Razor partial view references in .cshtml files.Søren Kottalhttps://hayleymarkdigital.co.uk/blog/exploring-umbraco-ai-for-end-users/60e3094c-02b7-4781-a5cd-4de030148deaThu, 09 Jul 2026 00:00:00 GMTProviding reliable, proactive and personable freelance support for website updates, SEO, lead generation and ongoing marketing strategies.Hayley Markhttps://www.dynamicdave.nl/blog/umbraco-18-elements/3e2293a7-111a-43f4-a269-938c7c820cd5Tue, 07 Jul 2026 22:00:00 GMTThere 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.When I first saw these demoed at Codegarden, I immediately thought, "Here we go. This is definitely going to be one of my favorite updates since a long time." It's not a brand-new idea. In fact, it's almost more impressive because it turns something most experienced Umbraco developers have hacked together themselves into an actual, official feature.If you’ve built Umbraco websites for any length of time, you’ve probably done this: made a “Globals “ of “Various Content” node and hidden it, set up a Shared Content folder, tossed reusable stuff onto a Settings page, or kept a folder with call-to-actions, testimonials, author profiles, or banners. None of which are even real pages.Did it work? Yeah… most of the time. But let's be honest—it always felt like a kludge.That kind of content never really belonged alongside website pages. This “content” didn’t need URLs; users weren’t supposed to visit it. We only structured things this way because editors needed somewhere to manage reusable pieces. For years, we just pretended these were documents because Umbraco left us no other option.With Umbraco 18, the compromise disappears.Dave Jonkerhttps://marathonus.com/about/blog/what-umbraco-codegarden-2026-left-on-me-permanently/e0888e27-38b2-4a67-b142-8fd9d33c6df5Mon, 06 Jul 2026 00:00:00 GMTMarathon's Scott Clevenger reflects on Umbraco Codegarden 2026 — an MVP, a tattoo, and a platform that's ready for whatever comes next.Scott Clevengerhttps://www.linkedin.com/pulse/ai-signalling-end-cms-we-know-simply-becoming-much-bigger-durrant-z3nme/ab02fa51-3f7c-4579-8e10-42505c73a77bMon, 06 Jul 2026 00:00:00 GMTNick Durranthttps://gibe.digital/blog/gibe-goes-to-codegarden-2026-edition/493aed42-3675-449c-88bd-4277ac85a17cMon, 06 Jul 2026 00:00:00 GMTGibe reflects on Codegarden 2026, covering the latest Umbraco announcements, standout sessions, community highlights, and our Package Award nomination.Sam Forresthttps://owainjones.dev/blog/new-giscus-powered-comments-and-h5yr-widget/39c2627e-992d-4d0e-96cd-b86a87789053Sat, 04 Jul 2026 19:18:36 GMTI've added a giscus powered comments, and the awesome H5YR widget, to my blog posts!Owain Joneshttps://www.nevitech.co.uk/blog/introducing-imagesharp-trimcache-for-umbraco/e4683743-06e9-4e69-bdd0-0d540509f7aeFri, 03 Jul 2026 23:00:00 GMTA free Umbraco package that trims the ImageSharp.Web image cache by age on a schedule, for both the local physical cache and Azure Blob storage. Stop the media cache growing unbounded on Umbraco Cloud and self hosted sites.Justin Nevillehttps://shazwazza.com/post/letting-ai-agents-loose-on-examine/16dbb04e-fbe8-4f71-882a-efc8442a623cFri, 03 Jul 2026 17:45:20 GMTI've been maintaining Examine for a very long time now. It's the search and indexing library that sits underneath every Umbraco site, and like any project that's been around long enough, it has plenty of hot paths that could be faster, a steady trickle of issues that need triaging, and a backlog of "I'll get to that eventually" performance work that, well… I never actually get to. So a couple of months ago I thought I'd try an experiment - what if I stopped doing all of that myself and instead let a bunch of AI agents do it for me, on a schedule, while I got on with everything else? This post is about how that went. I've shipped a few releases off the back of it and some of the hot-path improvements are genuinely a bit ridiculous. So what are these "agentic workflows"? The thing I installed is GitHub Next's Agentic Workflows - a set of markdown-defined workflows that run in GitHub Actions and drive an AI agent to do actual maintenance work on your repo. They're not chat bots. They run on a schedule, they have persistent memory, they open real pull requests, and they leave the "should this ship?" decision to me. I ended up with a few of them running on Examine: Perf Improver - runs daily, hunts for performance bottlenecks, writes benchmarks to actually prove the improvement, and opens a draft PR with the before/after numbers. Efficiency Improver - its scrappier sibling, focused on the smaller allocation-and-LINQ-state-machine wins that add up over time. Daily Issue Triage - goes through untriaged issues, sets types, applies labels, spots duplicates, and leaves a tidy triage report for me. Agentic Maintenance - keeps the whole setup ticking along. Each one is just a markdown file in .github/workflows/ with a description, a schedule, some safe-outputs limits (things like "you may open at most 4 PRs per run, and they must be drafts") and a big prompt describing how to behave. That's it. The nice part is that the guardrails are declarative, so the agent can't merge its own PRs, it can't touch protected files, and it can only comment so many times per run. All of that is baked in. How it actually works day to day The bit that makes this more than a gimmick is the persistent memory. Every run, the Perf Improver reads its own notes - which build/test/benchmark commands it validated, what's on its optimisation backlog, what it worked on last time, and which suggestions I've already ticked off. Then it does a couple of tasks in a round-robin fashion so it's not endlessly poking at the same corner of the codebase. It also keeps a single rolling "Monthly Activity" issue open with a checklist of what needs my attention. So my side of it is pretty simple: the agent opens a draft PR with measured before/after numbers, I read it and run CI, and if I'm happy with it I merge. That's the whole loop. I'm the reviewer, the agent is the workhorse doing the grind I never had time for. So what did they actually get done? Over roughly the last two months, here's what these workflows actually got up to on Examine: 124 successful Perf Improver runs and 9 successful Efficiency Improver runs 20 successful Daily Issue Triage runs quietly keeping the issue tracker tidy 24 performance/efficiency PRs reviewed and merged (13 from Perf Improver, 11 from Efficiency Improver) between late May and the end of June And the bit that actually matters - three releases shipped off this work: v3.8.0, v3.9.0 and the v4.0.0-beta.7 pre-release That last point is really the whole thing. This isn't a pile of speculative branches rotting in a fork somewhere - it's code that went through my review, passed CI, and is now sitting in NuGet packages that real Umbraco sites are running. Show me the numbers Right, this is the part I actually get excited about. One of my favourite things about the Perf Improver is that its prompt tells it to only attempt improvements it can actually measure - establish a baseline first, make the change, then measure again and document both numbers. For the algorithmic hot-path stuff that means benchmarks, so along the way it built out a proper BenchmarkDotNet suite that compares the current source against the published NuGet packages (3.0.1 through 3.3.0), which means I can show you real, reproducible deltas instead of hand waving. The full-text search hot path ManagedQuery is the primary full-text search entry point in Examine - it's what runs on basically every search. The agent noticed it had no dedicated benchmark, wrote one, and then stacked up a series of small, individually measured changes: a volatile factory cache in SearchContext.GetFieldValueType, an early return in the extract-terms check, and killing off some redundant ConcurrentDictionary lookups in AddDocument. Here's the current source vs the most recent 3.3.0 release, on a 1,000-document index: Method Version Mean Allocated ManagedQueryAllFields 3.3.0 11.42 ms 1,323 KB ManagedQueryAllFields Source 2.17 ms 371 KB That's about 5.3x faster and roughly 3.6x less memory allocated on the single most travelled code path in the whole library. On the busiest thing Examine does. I'll happily take that. Building queries GroupedAnd / GroupedOr / GroupedNot are the workhorses of the query builder. A little string[] fast-path (skipping a defensive .ToArray() copy when the caller already handed it a string[]) plus some allocation trimming got this: Method Version Mean Allocated CreateQueryOnly 3.3.0 3,995 ns 8.34 KB CreateQueryOnly Source 319 ns 2.20 KB GroupedAndStringArray 3.3.0 21,377 ns 21.10 KB GroupedAndStringArray Source 16,659 ns 14.34 KB The CreateQuery() baseline dropping from 8.34 KB down to 2.2 KB is a lovely little win, and the grouped clauses are about 25% faster with a third of the allocation shaved off. Constructing a ValueSet Every single document you index goes through a ValueSet constructor. The old path allocated an intermediate dictionary and a generator state machine per field, which is exactly the kind of thing you don't notice until you're bulk indexing a big site. The agent got rid of both: Method Version Mean Allocated FromDictionary5Fields 3.3.0 1,183 ns 2,200 B FromDictionary5Fields Source 226 ns 592 B FromDictionary20Fields 3.3.0 4,007 ns 6,544 B FromDictionary20Fields Source 654 ns 1,520 B That's roughly 5-6x faster and about 4x less allocated on indexing, and when you're rebuilding the index on a large Umbraco site that adds up fast. The really nice touch is that these benchmark result tables now live in doc-comments right next to the benchmark code, so the numbers are versioned in the repo alongside the thing they measure. The agent did that bit too. Was it actually worth it? For me the thing that makes it work is the measurement. Everything comes to me as a small, focused, draft PR with the numbers attached, so I can look at it, sanity check it, run CI, and decide in a couple of minutes. It's not zero effort - I still read every change before it goes anywhere near main - but the ratio is fantastic. I'm getting a steady stream of well-measured, single-purpose performance PRs on a library I care about, on paths I'd genuinely never have found the time to optimise by hand, and I've shipped real releases because of it. For a project I maintain around everything else, that's a pretty great deal. If you maintain a repo with a backlog you never get to, especially performance work that needs benchmarks to justify it, I'd recommend giving GitHub Next's agentics a go. You can see all of it out in the open on the Examine repo - the [perf-improver] and [efficiency-improver] PRs, the benchmark suite, and the releases they fed into. And there's a nice bonus here for me too: ExamineX, my managed, cloud-hosted Examine search offering, runs on this exact same internal plumbing. So all this work the agents have been doing to tighten up Examine's query and indexing hot paths feeds straight through into ExamineX - the underlying engine gets faster and leaner, and every ExamineX site gets those wins for free without changing a thing. If you'd rather have your search running as a managed service instead of hosting Lucene indexes on your own servers, that's what ExamineX is there for. 🙂Shanon Thompson (Deminick)https://medium.com/@ravimotha/umbraco-london-july-meetup-the-write-up-b4ce49a37390?source=rss-8e76be83b03f------2793547bc-9db7-466a-8ccc-ece4dcca2df3Fri, 03 Jul 2026 09:18:14 GMTRavi Mothahttps://mattbrailsford.dev/creating-a-safe-space-for-editors-to-be-wrongaa85a56d-cdf0-4219-9201-7223f09fa3acFri, 03 Jul 2026 00:00:00 GMTI spend most of my time these days working on Umbraco AI, bringing AI into the hands of content editors. So I think a lot about what actually makes...Matt Brailsfordhttps://dev.to/mpisaacs/codegarden-2026-a-little-late-because-it-gave-me-something-to-build-2em62b868ccd-61d7-4977-a92b-44f4da1c548fWed, 01 Jul 2026 15:53:03 GMTA few weeks ago I was in Copenhagen for my first Codegarden, and one quiet thought has stuck with me since. It didn't come from a keynote. It came from the bit the keynote leaves out. I've worked with Umbraco for years, but I'd never been to Codegarden, and I turned up without much of a fixed idea of what the two days would be. I kept that open on purpose. I wanted to take it in rather than measure it against something I'd decided in advance. What struck me most was that the value came from two places at once. The sessions were a fantastic source of inspiration; everything from keynotes to guest speakers all seemed to resonate in some way or another. The conversations in between the sessions - drifting around the event space and finding common ground with anyone and everyone - proved just as valuable. I came home more energised than I've been in a while, with a notebook full of half-formed ideas and a better feel for the community I'm part of. But the thing I kept turning over afterwards was that bit the keynote leaves out. That's what I want to write about. The easy half and the hard half Every major Umbraco release gets the same treatment. A polished keynote, a clean demo, a feature that looks effortless on stage. There's plenty in 18, and which part matters most depends on what you're building. For me it's Elements: a new Library section where you manage reusable content and reference it through a new element picker. Create once, use everywhere. It's a genuinely good direction. Reusable content has lived awkwardly in the content tree for years, and Library finally gives it a proper home. What the demos don't show you is the part I've been playing around with for the past few weeks. Taking a real Umbraco 17 site, with content pickers threaded through block lists, block grids, rich text blocks and base document properties, and getting all of it to point at the new Library without an editor ever noticing anything moved underneath them. The feature is the easy half. The migration is the half that decides whether anyone actually uses it. Why migration is where adoption lives A new way of modelling content only matters if existing sites can get to it. New projects will use Library because it's there and it's the obvious choice. The much bigger pile of work is the sites already in production, built the old way, where reusable content was faked with content pickers pointing at hidden nodes because that was the best tool on offer at the time. Upgrade conversations with clients are increasingly turning into "end of life is on the way, you need to upgrade!" but Umbraco have given us some genuinely useful new features that can turn those conversations from scaring clients away from security woes to improving their content management and supercharging their marketing activities. There's a timing thing here. The migration path has to exist when the feature does, not three months later when the upgrade conversation has gone cold. A site that wants Library is at its most willing in the window right after release, while the appetite is fresh and the project is being planned anyway. Miss that window and you're asking someone to reopen a decision they've already made, which almost never happens. That's the question I bring to every shiny thing on a keynote slide. Not "is this exciting", but "what's the real path from a live production site to it, and how much of that path can be made painless". The exciting idea is the easy part. The route onto it is the work. What the package actually does This is the problem the Library Migrator package is built to solve, and the job is less glamorous than it sounds. It moves documents from Content into Library, so the things that were always meant to be reusable end up where they belong. It swaps every content picker on the relevant types for an element picker pointed at Library, so editors keep the same workflow and have nothing new to learn. And it rewrites the stored values, which is the part that earns its keep: every value held in an old content picker is updated to reference the new elements, across block lists, block grids, rich text blocks and base document properties. One reference left behind is a broken link an editor finds at the worst possible moment. None of that shows up in a demo, using a brand new, tailored project designed to show the feature off at its best. Yet content is the centrepiece of all CMS solutions and the value in existing content is always at the forefront of our clients' minds. Whether it's a same-platform upgrade or a complete rebuild, the question of migration always gets raised. The Library Migrator is out now. If you're looking at an Umbraco 17 site and wondering how on earth it's going to reach 18's (or 21 if you're LTS-conscious) Library, that's exactly what it's for. Library Migrator on Umbraco Marketplace Library Migrator repositoryMike Isaacshttps://kjac.dev/posts/postgresql-provider-for-umbraco-search/99d70815-d362-4e64-b826-41d97d226935Wed, 01 Jul 2026 00:00:00 GMTIntroducing a PostgreSQL powered search provider for Umbraco Search.Kenn Jacobsenhttps://owain.codes/blog/2026/july/using-umbracoautomate-to-populate-content-from-an-api/1202d7cd-76aa-4aae-91a2-c1f60e2837a5Wed, 01 Jul 2026 00:00:00 GMTLearn how to automatically populate Umbraco content from an external API using Umbraco.Automate, with a hands-on PokéAPI example and video demo.Owain Williamshttps://dev.to/luukpeters/advanced-permissions-meets-umbraco-18-26g0c2698f50-4853-45fd-a3a3-106c0085fbc9Sun, 28 Jun 2026 19:49:52 GMTA few days ago, the final version of Umbraco 18 was released! So it was time to update my Advanced Permissions package to support Umbraco 18. This was not just a simple case of updating a few namespaces and dependencies and calling it done. The main new feature in Umbraco 18 was a perfect candidate for Advanced Permissions support, so that is exactly what I added! What is new in Umbraco 18 The Umbraco 18 release is (and I quote) "a short and sweet release". The main attraction is the new Library section and the first version of reusable Elements. Reusable Elements in the Library section are essentially Content nodes without rendering and routing. Other than that, they behave a lot like Content: you can create, delete, move them, and so on. That made them the perfect candidate for support in v18 of the Advanced Permissions package. Besides Library support, the package also has a few other improvements and additions. Let's talk about them! Library support! The first obvious new feature is the Permissions Editor for the Library. Just like with Content, you can set permissions for a User Group using the same inheritance and scoping system as the Content Permissions Editor. You'll notice that not every permission is applicable in every case, so N/A is displayed when a permission does not apply. And just like with Content, the Library also has an Access Viewer where you can see the effective permissions for a User Group or an individual User. I also added a Library Element Type Permissions Editor. Just like the Document Type Permissions Editor, you can set the insert options for Element Types for a specific User Group. With this Permissions Editor, you can control whether a User Group can create instances of an Element Type. This acts as a filter on the "create" list in the Library. And when a User has multiple User Groups, the well-established resolver will determine the effective permissions. Currently, because of a limitation in Umbraco, it is not yet possible to scope these permissions to a specific part of the Library tree like the Document Type Permissions Editor does. And of course, the Element Type Permissions Editor also has an associated Access Viewer. Redesign Because of all these new Permissions Editors and Access Viewers, the menu became harder to read at a glance. So the main menu has been redesigned around the scope of the editor and viewer. All editors and viewers in the menu are now called Permissions Editor and Access Viewer respectively. Their purpose is determined by the menu header they are under: Content, Document Type, Library, or Library Element Type. In the screenshot, you'll also notice a slight redesign of the workspaces for the editors and viewers. They now look more Umbraco native and display a one-line description of what the editor or viewer is for. And when you have not selected anything yet, it will now display a much nicer view. This will also be ported back to the Umbraco 17 version. To help or not to help In the top-right corner of each editor or viewer, you'll also notice a "learn more" button. This button gives access to more detailed documentation. It describes what the editor or viewer is for, and it links to more generic documentation explaining the concepts. Consider this a first version. It is already much better than nothing, but I think it can still be improved over time. This will also be ported back to the Umbraco 17 version. Localization support! And lastly, apart from the expanded documentation, Advanced Permissions now has localization for all languages that the Backoffice supports. Obviously, these translations are automatically generated because I am not fluent in 28 languages, so if you find an error, please let me know! All in all, I think this is a very nice and complete release. I'm happy that Advanced Permissions can support new Umbraco features as soon as they come out. You can find Advanced Permissions for Umbraco here: NuGet: https://www.nuget.org/packages/Umbraco.Community.AdvancedPermissions/ The Umbraco Marketplace: https://marketplace.umbraco.com/package/umbraco.community.advancedpermissionsLuuk Petershttps://owain.codes/blog/2026/june/ocautomatelinkedin-now-available/750bf608-35e4-4278-a43f-6df4b0b71eb1Sun, 28 Jun 2026 00:00:00 GMTOC.Automate.LinkedIn is out of beta and OC.Automate.Bluesky and OC.Automate.Mastodon are all working on Umbraco 18Owain Williamshttps://anju-dev-notes.hashnode.dev/my-first-codegarden-experience-a-journey-from-india-to-copenhagenf9d31e16-0cf5-49b2-8d94-95fa147775f6Fri, 26 Jun 2026 10:36:14 GMTAttending Codegarden for the first time was truly a milestone moment in my career — not just because of the event itself, but because it also became a very personal and memorable journey for me. ThisAnjumol Babuhttps://owain.codes/blog/2026/june/umbraco-automate/c45fd6c8-f1b8-4201-a18c-4dadb25a4e56Fri, 26 Jun 2026 00:00:00 GMTOwain Williamshttps://owain.codes/blog/2026/june/umbraco-automate-workflows/6db4380d-1c82-421c-a3ab-3735efca3cebFri, 26 Jun 2026 00:00:00 GMTOwain Williamshttps://www.nurhakkaya.com/2026/06/im-umbraco-mvp-for-fifth-year-running.htmlf614fb4c-04c9-4211-8cf9-84f494650e0cWed, 24 Jun 2026 14:04:05 GMTEvery year, Umbraco recognises the people who have gone above and beyond with their contributions to Umbraco projects and community, and I am pleased to announce that I am honoured to be renewed as an Umbraco MVP for the fifth consecutive year. To celebrate this achievement, I also wrote an article which you can read here. Thank you, Umbraco, and the Umbraco community, for their fantastic support in making this happen once more! #h5yrNurhak Kayahttps://www.johanreitsma.com/blogs/validating-an-umbraco-13-to-17-upgrade-with-a-sitemap-audit/3e35e468-54f4-4e63-9db5-b7b36f2c1dd0Wed, 24 Jun 2026 10:54:04 GMTHow I used a small .NET console tool to crawl a sitemap, compare Umbraco 13 and 17 environments, and quickly find broken pages after an upgrade....Johan Reitsmahttps://www.linkedin.com/pulse/you-never-know-whatll-stick-briony-mckenzie-2bjie/dd5f07fe-6316-4e4a-b8c7-74d034e7be84Wed, 24 Jun 2026 00:00:00 GMTOn unconventional career paths, accidental dev tools, and great people. ThereBriony McKenziehttps://www.dynamicdave.nl/blog/developer-productivity-hacks/4a8a6e81-696a-4ae7-a8ae-03db1223ca33Tue, 23 Jun 2026 22:00:00 GMTAs developers, we’re always searching for ways to get our work done faster. New frameworks roll out and promise to make us blazing fast, AI tools keep booming with talk about writing half our code, and if you’ve ever sat through a developer conference lately, you know there’s always a session on “How to be More Productive.” But after working with Umbraco since version 4, I have to be honest: those massive productivity leaps don’t really come from the shiny, new, revolutionary tools. It all comes down to friction. And not the dramatic, show-stopping kind. I mean those hundreds of tiny speed bumps scattered all over your day. A few extra clicks in the Umbraco backoffice. Rebuilding the same component again and again. Always double-checking a property alias. Waiting for your solution to spin up. Poring over a monster Razor file, desperately trying to recall where you put that chunk of markup. None of these feel like deal-breakers on their own, but stacked together? Suddenly, you’re delivering features at a crawl. What’s won me over with the latest Umbraco versions, especially Umbraco 17, is just how much more aligned the platform is with standard .NET development. It feels less like you’re wrestling with a quirky CMS and more like you’re just building .NET applications. There’s a real payoff: less fighting the system means more time solving real business problems.Over the years I’ve picked up quite a few habits that speed up Umbraco development and make it less painful—some are tied directly to Umbraco 17, while others are just hard-earned lessons from a decade of building websites. Here’s what’s helped the most for me.Dave Jonkerhttps://dev.to/bernadet/extending-tiptap-in-umbraco-a-real-world-list-example-1hd1b3f2f2d5-41e4-4377-8382-1d255bd6d9c0Tue, 23 Jun 2026 07:37:36 GMTIf you've spent any time migrating editors or building rich-text features, you'll know Tiptap looks great on paper but sometimes feels a little... minimal compared to what TinyMCE shipped out of the box. At ilionx we've been moving a few large sites to Umbraco 17 and bumped into the same feedback: list style options. Nothing dramatic, just the ability to pick Roman numerals, different bullet shapes, that sort of thing, but enough to make editors ask for the old behavior back. So we wrote a small TypeScript extension that adds back list-style variants. It gets built to App_Plugins with Vite, plugs into the UmbTiptapExtensionApiBase and wires up extra toolbar menu items. The actual extension is tiny, it just adds a listStyleType attribute to the list nodes and renders it as inline CSS, but the surrounding bits (icons, toolbar menus, wiring) make the UX feel polished. Tiptap has solid docs on extending and creating extensions, and Umbraco documents how to register a Tiptap extension, but stitching everything together took a little trial and error. Below is the extension configuration we used. It looks like a lot for a simple feature, but a fair chunk of the files are just icons and small glue code. Let’s start with the actual extension definitions in Umbraco-package.json, where we define 4 extensions: "extensions": [ { "type": "icons", "alias": "My.Icons.TiptapListStyle", "js": "/App_Plugins/My.TiptapListStyle/list-style-icons.js" }, { "type": "tiptapExtension", "alias": "My.Tiptap.ListStyle", "api": "/App_Plugins/My.TiptapListStyle/list-style.tiptap-api.js", "meta": { "icon": "icon-ordered-list", "label": "List style type", "group": "#tiptap_extGroup_formatting" } }, { "type": "tiptapToolbarExtension", "kind": "menu", "alias": "My.Tiptap.Toolbar.OrderedList", "overwrites": "Umb.Tiptap.Toolbar.OrderedList", "api": "/App_Plugins/ My.TiptapListStyle/ordered-list-menu.tiptap-toolbar-api.js", "forExtensions": ["My.Tiptap.ListStyle", " My.Tiptap.OrderedList"], "items": [ { "label": "Numbered list", "data": null, "appearance": { "icon": "icon-ordered-list" } }, { "label": "Numbered list: i, ii, iii", "data": "lower-roman", "appearance": { "icon": "icon-list-style-lower-roman" } }, // add other style definitions here ] }, { "type": "tiptapToolbarExtension", "kind": "menu", "alias": " My.Tiptap.Toolbar.BulletList", "overwrites": "Umb.Tiptap.Toolbar.BulletList", "api": "/App_Plugins/My.TiptapListStyle/bullet-list-menu.tiptap-toolbar-api.js", "forExtensions": ["My.Tiptap.ListStyle", "Umb.Tiptap.BulletList"], "items": [ { "label": "Bullet list", "data": null, "appearance": { "icon": "icon-bulleted-list" } }, { "label": "Bullet list: circle", "data": "circle", "appearance": { "icon": "icon-list-style-bullet-circle" } }, // add other style definitions here ] } ] Here’s what we register: an icon set (a bunch of tiny SVGs showing what each list style looks like) one Tiptap extension which carries the list-style attribute two toolbar extensions that replace the ordered/bulleted list buttons with menus that expose the variants. The icon set The icons are trivial: I asked an AI to generate SVGs for different list markers and put each one in a tiny TypeScript file that exports the SVG string. /** Ordered list with lower-roman markers (i, ii, iii). */ export default `i.ii.iii.`; And a small registry file maps the icon names to those files: export default [ { name: 'icon-list-style-lower-roman', path: () => import('./icons/svg-ordered-list-lower-roman.js'), }, //... ]; These images are purely to make the toolbar menus readable — a little UX polish so editors instantly recognise the option they’re picking. The Tiptap extension The extension itself is surprisingly compact. It adds a listStyleType attribute to the built-in orderedList and bulletList nodes and serialises it as inline list-style-type style so the HTML stays portable and renders the same in the backoffice and on the front end. import { Extension, UmbTiptapExtensionApiBase } from '@umbraco-cms/backoffice/tiptap'; /** * Extends the built-in orderedList and bulletList nodes with a `listStyleType` * attribute that maps to the CSS `list-style-type` property. * * The attribute is serialised as an inline style so the stored HTML is portable * and renders correctly both in the backoffice editor and on the front end. */ const ListStyleExtension = Extension.create({ name: 'listStyle', addGlobalAttributes() { return [ { types: ['orderedList', 'bulletList'], attributes: { listStyleType: { default: null, parseHTML: (element) => element.style.listStyleType || null, renderHTML: (attributes) => { if (!attributes['listStyleType']) return {}; return { style: `list-style-type: ${attributes['listStyleType']}` }; }, }, }, }, ]; }, }); export default class ListStyleTiptapExtensionApi extends UmbTiptapExtensionApiBase { constructor(...args: ConstructorParameters) { super(...args); this.getTiptapExtensions = () => [ListStyleExtension]; } } That’s it, the extension maps an attribute to CSS and makes sure works in both front- and backoffice. Nothing scary. The toolbar extensions Because ordered and unordered lists are separate toolbar buttons, we overwrite each one with a menu that exposes the style variants. To avoid duplicating logic we put the toolbar behaviour into a single helper and import it from the two small extension files. Each toolbar menu has to do a few things: create a list if the selection isn’t in one switch between ordered and bullet lists toggle or set a specific list-style-type and reflect the active state in the menu UI. That last bit is where the logic concentrates, the UI needs to show which style is active and allow toggling back to the default behaviour. The per-list-type extension files look like this: import { createListStyleMenuToolbarApi } from './list-style-menu-toolbar-api.js'; export default createListStyleMenuToolbarApi('bulletList'); And the shared toolbar helper contains the actual implementation and state logic: import type { Editor } from '@umbraco-cms/backoffice/tiptap'; import { UmbTiptapToolbarElementApiBase } from '@umbraco-cms/backoffice/tiptap'; type ListStyleMenuItem = { data?: string | null }; function getStyleType(item?: ListStyleMenuItem): string | null | undefined { return item?.data; } function applyListStyle( editor: Editor, listType: 'orderedList' | 'bulletList', styleType: string, ): void { if (editor.isActive(listType)) { const currentStyle = editor.getAttributes(listType)['listStyleType'] as string | null; const newStyle = currentStyle === styleType ? null : styleType; editor.chain().focus().updateAttributes(listType, { listStyleType: newStyle }).run(); return; } if (listType === 'orderedList') { editor .chain() .focus() .toggleOrderedList() .updateAttributes('orderedList', { listStyleType: styleType }) .run(); } else { editor .chain() .focus() .toggleBulletList() .updateAttributes('bulletList', { listStyleType: styleType }) .run(); } } function applyDefaultList(editor: Editor, listType: 'orderedList' | 'bulletList'): void { if (editor.isActive(listType)) { const currentStyle = editor.getAttributes(listType)['listStyleType'] as string | null; if (currentStyle) { editor.chain().focus().updateAttributes(listType, { listStyleType: null }).run(); return; } if (listType === 'orderedList') { editor.chain().focus().toggleOrderedList().run(); } else { editor.chain().focus().toggleBulletList().run(); } return; } if (listType === 'orderedList') { editor.chain().focus().toggleOrderedList().run(); } else { editor.chain().focus().toggleBulletList().run(); } } /** * Toolbar menu API for ordered/bullet list buttons with list-style-type variants. */ export function createListStyleMenuToolbarApi(listType: 'orderedList' | 'bulletList') { return class extends UmbTiptapToolbarElementApiBase { override isActive(editor?: Editor, item?: ListStyleMenuItem): boolean { if (!editor) return false; const styleType = getStyleType(item); if (styleType === undefined) { return editor.isActive(listType); } if (styleType === null) { const currentStyle = editor.getAttributes(listType)['listStyleType'] as string | null; return editor.isActive(listType) && currentStyle === null; } return editor.isActive(listType, { listStyleType: styleType }); } override execute(editor?: Editor, item?: ListStyleMenuItem): void { if (!editor) return; const styleType = getStyleType(item); if (styleType === undefined || styleType === null) { applyDefaultList(editor, listType); return; } applyListStyle(editor, listType, styleType); } }; } TODO / caveats I’m still getting comfortable with TypeScript, so this isn't a 100%-polished extension. One known quirk: clicking a custom style button after setting a style will clear the style but not fully remove the list node the way the stock ordered/bullet button does. It's a small UX edge-case and likely fixable by tweaking the toggle logic, but I haven't had time for it yet. If you want to copy this approach, the important bits are: expose a listStyleType attribute on the list nodes, serialize it in a way that works in both editor and front end (inline style is the simplest) replace the toolbar buttons with menus that set/update that attribute. Hopefully this saves you a few hours of experimentation. The overall idea is small, but the payoff for editors is surprisingly nice.Bernadet Goeyhttps://www.linkedin.com/pulse/my-first-codegarden-ai-umbraco-17-18-why-im-excited-build-murthy-3ncxe/713122ee-d074-4285-9424-ea3cc7b4b1dfTue, 23 Jun 2026 00:00:00 GMTThis was my first time travelling to Copenhagen, and my first ever CodeGarden, and what a way to start. I went over with Luca Colella and Kat Dixon and we had a brilliant couple of days.Raghavendra Murthyhttps://markmcdonald.dev/writing/what-codegarden-inspired-me-to-build-next/ea4b1333-c829-4b2e-ad93-9bbae2cc4f09Mon, 22 Jun 2026 00:00:00 GMTWhat I learned building an AI-assisted pipeline that maps existing sites into reusable Umbraco components.Mark McDonaldhttps://umbuntu.uk/blog/codegarden-2026-ubuntu/bb7a591e-a613-4cee-9ac5-0c22167de8a4Mon, 22 Jun 2026 00:00:00 GMT"I am because we are"Mitchell Nortjehttps://cornehoskam.com/posts/extending-umbracos-extensions-a-codegarden-workshop-you-can-try-yourself/b2f14cc2-43e7-478a-9e53-facdcf1a61b7Mon, 22 Jun 2026 00:00:00 GMTClone and try our four-hour Codegarden workshop on extending Umbraco's extensions: an escape room of coding quests across Engage, Workflow and Deploy.Corné Hoskamhttps://owain.codes/blog/2026/june/its-coffee-time/79fa4d08-39a0-4a36-b48d-51dd40b080b8Mon, 22 Jun 2026 00:00:00 GMTOwain Williamshttps://www.linkedin.com/pulse/most-interesting-thing-codegarden-wasnt-feature-adam-shallcross-cmxwe/5bd4884b-490d-421c-82b3-c70f775d224bMon, 22 Jun 2026 00:00:00 GMTThere were plenty of shiny things to look at this year. New content types, a workflow engine, hosted servers you can spin up in minutes.Adam Shallcrosshttps://www.shoutdigital.com/insights/codegarden-2026-and-the-next-chapter-for-umbraco/7b944c30-5a7b-4539-8320-248be30300c6Fri, 19 Jun 2026 00:00:00 GMTAI, automation, community - Umbraco MVP Ian Grieve talks about his key takeaways from Copenhagen.Ian Grievehttps://www.nathanielnunes.com/blog/umbraco-mvp-codegarden-2026ae4adfcd-8c06-4fca-b034-8c296daaf49fThu, 18 Jun 2026 11:30:00 GMTMy first year as an Umbraco MVP: receiving the award at Codegarden 2026 in Copenhagen, the MVP Summit, the sessions, the people, and the moments between.Nathaniel Nuneshttps://frytom.org/2026/06/13/tilbake-fra-kobenhavn-og-umbraco-codegarden-2026-%F0%9F%87%A9%F0%9F%87%B0/d1f2a0d6-ac9a-44c6-acc7-325a1f5a6fbaThu, 18 Jun 2026 00:00:00 GMTNoen dager fylt med faglig påfyll, gode samtaler og sterke relasjoner — det er alltid noe eget med Codegarden. Umbraco-communityet er ikke en kult, men… det er kanskje det nærmeste vi kommer …Tom Erik Rozmara Frydenlundhttps://www.linkedin.com/pulse/my-first-umbraco-codegarden-more-than-stickers-t-shirts-dave-jonker-tew6e/?trackingId=QknJFmSATw6wxaZj0VosrA%3D%3D66af1f8d-2b97-444d-9b14-7aa3bb12f72dThu, 18 Jun 2026 00:00:00 GMTAfter my blog was recently featured on umb.fyi — thanks to Matt Brailsford for that — I felt like I also owed the community a proper write-up about my very first Codegarden experience.Dave Jonkerhttps://owain.codes/blog/2026/june/codegarden-2026/5afc451a-08dc-4458-8704-f5d30edb012aThu, 18 Jun 2026 00:00:00 GMTOwain Williamshttps://medium.com/@ravimotha/codegarden-26-a-review-aa35c60e3b08?source=rss-8e76be83b03f------24b418492-8dec-4929-8c7a-515b7ffb1298Wed, 17 Jun 2026 17:42:48 GMTRavi Mothahttps://www.jeroenbreuer.nl/blog/my-codegarden-2026-highlights/38b4d6b3-f41a-4a60-999f-219eb4ec2913Wed, 17 Jun 2026 14:26:59 GMTA summary of my Codegarden 2026 highlights.Jeroen Breuerhttps://jcdc.dev/blog/umbraco-package-automate-inspectorea2298b7-b19d-45a1-b34a-da9d1bf2a2b1Wed, 17 Jun 2026 07:00:00 GMTExplore everything Umbraco Automate has to offer with this new community package!James Carterhttps://www.blendinteractive.com/thoughts/codegarden-2026/4c9b77c2-d771-43e8-a245-c34f228856c4Wed, 17 Jun 2026 00:00:00 GMTA road report from Codegarden 2026 — UmbracoJoe Kepleyhttps://aaronsadler.dev/blog/2026/june/16/codegarden-2026-i-went-to-copenhagen-for-a-week6a8d6551-f9bb-4a4b-9427-6a57fd0403c6Tue, 16 Jun 2026 00:00:00 GMTMy week in Copenhagen for Codegarden 2026: the MVP Summit, the launch of Umbraco Automate, the sessions that stood out, and why I keep coming back. Continue readingAaron Sadlerhttps://dev.to/luukpeters/tiptap-is-not-broken-your-expectations-are-5h8ma75948fa-e5b9-4052-bdc9-95489f635a71Mon, 15 Jun 2026 12:47:24 GMTSince the Umbraco 16 release, Umbraco ships only with the TipTap Rich Text Editor. This was unfortunately something that Umbraco was forced to do. TinyMce 7 has a license that is incompatible with the open source license of Umbraco and TinyMce 6 was going out of support. So an alternative had to be found. Umbraco did a pretty good job at abstracting the rich text data. In Umbraco 15 both TinyMCE and TipTap were still present and exchangeable because of this abstraction. And arguably, the way you can set up your toolbars for the TipTap editor is superior to TinyMCE. But still, a new Rich Text Editor is a big change that presents real challenges. These challenges are most obvious when looking at the Umbraco forum's tip-tap tag. Topics vary, but a few come up again and again: Additional HTML tags getting added to the markup, like a tag inside a The inability to add certain tags to TipTap, like tags The inability to add styling to an element, for instance to create a link that looks like a button These are valid challenges, especially if you're upgrading from an existing TinyMCE setup. But this is also a good moment to ask two questions: Why do I want the same behaviour? And was the old behaviour actually any good to begin with? You don't have to migrate everything at once Before getting into that, it's worth knowing that TinyMCE is still available as a community package for Umbraco 16+. If you're in the middle of a project, dealing with a large codebase, or just not ready to rethink your Rich Text Editor setup right now, that's a valid escape hatch. Swap in the package, keep things running, and give yourself time to migrate properly. But "later" should still be on the roadmap. The package is community maintained, not an official Umbraco product, so there are no guarantees around long-term support or compatibility with future Umbraco versions. Relying on it indefinitely carries the same risk as the situation Umbraco just came out of with TinyMCE 6. So use it if you need to. Just don't treat it as a permanent solution. The RTE is not a page builder I'm not a big fan of giving editors too much freedom in a Rich Text Editor. Don't get me wrong, RTEs are great and help editors a lot. But give too much rope and things go wrong fast. My preference is for RTEs to handle the basics: adding a link, making text bold or italic, maybe a table if the frontend deals with it gracefully on mobile. What I don't like is image placement and scaling inside an RTE. Without proper processing this is a problem for performance and mobile layouts. I also don't like HTML snippets or trying to add CSS classes to elements from within an editor. It's error prone, and if something breaks, you need HTML knowledge to fix it. That's not a realistic expectation for most editors. So when people ask how to replicate that kind of behaviour in TipTap, I'd rather ask why they need it at all. Stop fighting the editor, start working with Umbraco Instead of trying to make TipTap behave like TinyMCE did, consider using the tools Umbraco already gives you. Need a link that looks like a button? Use a block inside the Rich Text Editor. TipTap has solid block support, and Umbraco exposes this well. You get a structured piece of content with its own view, its own properties, fully typed, fully renderable. An editor picks a "Button" block, fills in the label and the link and that's it. No CSS classes, no raw HTML, no risk of someone pasting style="color:red" into a script tag three months later. Need a pull quote, a callout, a code snippet with syntax highlighting? Same answer. Model it as a block. Render it properly. Keep the RTE itself lean. The argument I keep hearing is that recreating all of this takes more time than just making the old thing work again. That's sometimes true in the short term. But you're building something more maintainable, more predictable and more editor-friendly. There's another reason to think twice before pouring effort into recreating editor-specific behaviour: Umbraco has already switched its default Rich Text Editor once. It could happen again. If your implementation leans heavily on workarounds and editor-specific quirks, you're setting yourself up for the same migration pain all over again. If instead your RTE is kept lean and the complex bits live in blocks with their own models and views, a future editor switch becomes much less of an event. The RTE just renders text. Everything interesting is already abstracted away. What about the extra markup? The inside is worth addressing separately, because it looks like a bug but it isn't. TipTap is built on ProseMirror, which uses a strict document schema where every node needs to contain the right type of child node. For list items, that child is a block node and a paragraph is that block node. This is what makes editing reliable: without it, you can end up in situations where the cursor can't be placed inside a list item at all, or where deleting an item breaks unexpectedly. This behaviour is not unique to TipTap. Any editor built on ProseMirror does the same thing, and that includes quite a few well-known ones. TinyMCE handled lists differently, but that doesn't make TinyMCE's approach the correct one. If your frontend CSS breaks because of this, that's a one-time fix, typically just adjusting margin or display rules on li p. Once it's done, you're working with markup that is actually more structurally consistent than what TinyMCE produced. Closing thought A new editor is disruptive. But disruption is also a chance to reconsider decisions that were made years ago under different constraints, maybe with less knowledge of what Umbraco could do, or just because TinyMCE made it easy and easy felt like good enough. TipTap is not TinyMCE. It's not trying to be. And once you stop expecting it to be, you might find it pushes you toward solutions that are cleaner, better structured and easier to hand off to an editor who has no idea what a DOM is. Work with the grain of the tool, not against it.Luuk Petershttps://dev.to/d_inventor/i-attended-umbraco-codegarden-2026-5dak161357b5-54e2-4f88-b774-2636f250f13fMon, 15 Jun 2026 07:00:00 GMTCodegarden was last week in Copenhagen! I was there this time and here are my thoughts about the event. Previous time I attended was in 2023, so I will draw some comparisons to that year. It was a great experience and I left feeling generally excited and inspired. Organization Just like previous time, the event was very well-organized. At Codegarden, you're always well taken care of with lunch and dinner, great instructions, a little kick-off at the start of every day and a lot of spatial diversity. You always know what to expect. I was very happy to see that the quiet area was easy to find and it was mentioned at the beginning of the event. The previous time I didn't know that such a quiet area existed and I spoke out about that. It gave me comfort that I knew where to retreat to when I needed to. Additionally, there were many places to stand or sit outside and inside. The event was also a little shorter, which made it more manageable for me. The location was absolutely ideal for the amount of people that attended. There were many attendees (about 700 they said, if I remember correctly), but at no point did the venue feel crowded. I could always easily get to where I wanted to go, there were no long queues and there was always enough seats for all the talks at every stage. Talks I'll admit that, on the previous Codegarden, I had the wrong expectations for the talks. Talks are obviously aimed at specific target audiences and I don't belong to all of them. Some talks aim to inform, while others aim to inspire. Stories are not tutorials. Also, sometimes a talk doesn't teach you something new, but simply validates what you were already doing. So it was this time too. My focus is currently shifting slightly away from coding and more towards collaboration and I am looking for inspiration on how to deliver better software faster. I specifically wanted to attend Debugging Teams: What High-Performing Developer Teams Do Differently, because it seemed relevant to me. Although I was hoping for a deep analysis in development process and teamwork strategies, I ended up learning about the importance of trust and of sharing the "what", "how" and "why" of what we do. It surely gave me something to think about. I listened to Building Resilient Umbraco Integrations. A more tutorial-style demonstration with insightful information about what you need to think about when integrating with external services. The presentation included concrete code examples that gave concrete solutions to the presented problems. I personally already knew all of it, but it was nice to see anyway, because it confirms that I'm already doing it right. A special mention goes to Semira Allen and Jason Wodicka with their talks Drowning in Details: Turning TechTalk Into Everyday Language and How (not) to mess up everything. Their talks were incredibly engaging and they were a joy to listen to. I had a good laugh and they were each inspiring in their own ways. Some additional thoughts Copenhagen: The fact that it was in Copenhagen was what made me consider it again. I am not big on traveling abroad and the trip to Odense and back was seriously daunting. Being able to get there with just the airplane made the whole trip so much better! AI: I haven't mentioned AI in this blog. That's because I find the ethics of the application of AI at the moment very questionable. I am still working on forming a well-informed opinion. Umbraco and the community have showcased some very impressive work with AI. Umbraco awards: In case you didn't know it yet: we were nominated for an Umbraco award for "Accessibility and Security"! Even though we didn't win the award, I believe that our submission was still the best. The winning solution had a more visible approach to accessibility, but we can show off a real certification of accessibility with end-user testimonies to back it up. The nomination is a nice validation of my team's hard work. Umbraco in the bigger picture? Right now I am learning from people like Dave Farley, Emily Bache and Derek Comartin about better software development practices. Some of it is more about architecture and some of it is about collaboration and process. I feel like these topics deserve more attention in the Umbraco community. I need a talk named How I upgraded my mid-size web agency from feature branch and PR drag to real CI/CD. Maybe I get to give this talk myself one day, who knows. Conclusion It was a great event, and I'm very happy that I could be there. If it's like this again next year, then I will be eager to attend. Thank you Umbraco for everything!Dennis Heutinckhttps://owain.codes/blog/2026/june/ocautomatemastodon-released/7de901d1-ee3d-4a4e-abc9-096021994b0cMon, 15 Jun 2026 00:00:00 GMTOwain Williamshttps://www.nevitech.co.uk/blog/codegarden-2026-a-week-in-copenhagen-i-wont-forget/233e382a-01d6-4b35-b86e-561899c22357Sun, 14 Jun 2026 23:00:00 GMTJustin reflects on an unforgettable week at Codegarden 2026 in Copenhagen, where he was recognised as an Umbraco MVP, invited on stage during the keynote to demo his AI Log Analyser package, and won the AI Package Award.Justin Nevillehttps://www.dynamicdave.nl/blog/my-first-umbraco-codegarden/bbbc3e2f-5e98-47de-a90e-d1429527427aFri, 12 Jun 2026 22:00:00 GMTAfter my blog was recently featured on umb.fyi — thanks to Matt Brailsford for that — I felt like I also owed the community a proper write-up about my very first Codegarden experience.Because honestly, after finally attending for the first time, I completely understand why people keep talking about it long after the event is over.I’ve been building with Umbraco since version 4—that takes me back to 2012 or maybe 2013. After all those years, I finally made the pilgrimage: my first Codegarden. And wow, I get it now. I see why people talk about this thing like it’s some annual family reunion you can’t miss, not just a conference. All the stories you hear—about the talks, the people, those late nights that blur into early mornings—they're all real. Still, the heart of it isn’t just scavenging for stickers or filling your suitcase with t-shirts. It’s something deeper.What really struck me—and it hit pretty much as soon as I walked through the doors—is that sense of belonging. Suddenly you realize you’re a piece of something much bigger than just a CMS, a project, or a logo. You’re dropped right into the Umbraco community, and it’s almost impossible not to get swept up in that feeling.Dave Jonkerhttps://www.wearediagram.com/blog/diagram-wins-2026-umbraco-award-best-enterprise-solutionbc80816d-7bd4-42f0-9765-11f0866ec590Thu, 11 Jun 2026 20:46:10 GMTWe’re excited to share that the National Association of Tax Professionals (NATP) website, designed and developed by Diagram, has been named Best Enterprise Solution at the 2026 Umbraco Awards.Diagramhttps://www.dynamicdave.nl/blog/nominated-for-an-umbraco-solution-award/0ee9de5e-4407-49b9-b854-3e315e18e3e4Tue, 09 Jun 2026 22:00:00 GMTFeeling incredibly proud to have been nominated for an Umbraco Solution Award this year!Dave Jonkerhttps://www.enkelmedia.se/blogg/2026/6/7/codegarden-talk-hybrid-cache-changes-everything?utm_source=rss&utm_medium=rss&utm_campaign=rss841e586f-3774-4f15-943b-a7d84c91aa7bSun, 07 Jun 2026 05:31:32 GMTI recently spent some time looking closer at the new HybridCache implementation in Umbraco to prepare for my presentation at CodeGarden 2026, and the short version is this: it changes more than just the cache layer. Historically, Umbraco has been very good at keeping published content available in memory. That has made many common developer patterns feel cheap and convenient. Things like traversing content trees, using `.Children()`, `.Descendants()` and resolving references have often just worked without us thinking too much about the cost. With HybridCache, that mental model changes. The cache is still there, but not everything necessarily lives in memory all the time. The big win is scalability The reason for this change is very easy to understand when looking at large Umbraco installations. Keeping everything in memory can work beautifully for small and medium-sized sites, but it becomes painful when a site has hundreds of thousands of pages, many languages, or very large content structures. Startup time, memory usage and hosting constraints can become real problems. HybridCache helps by reducing the memory footprint and making startup faster. Instead of loading everything into memory, Umbraco can seed important content and load other content when needed. That is a big architectural improvement. The cost did not disappear The interesting part, at least for me as a developer, is that the cost did not vanish. It moved. Some operations that used to feel almost free can now become more expensive, especially on larger sites. Traversing a large tree, filtering over many children, or resolving many references may trigger more cache lookups or database access than before. That does not mean HybridCache is bad. Quite the opposite. But it does mean we need to be more intentional about how we build things like menus, listings, sitemaps and search-driven pages. Use the right tool for the job One of my main takeaways is that we should stop treating the published content cache as the answer to everything. For search and filtering, Examine is often a much better fit. For menus, footers and repeated structures, runtime cache or prebuilt DTOs can be a good option. For sitemaps, adding the right data to the index (e.g. URLs) can be much more scalable than traversing the whole content tree. So the practical message is simple: measure, observe, and choose the right approach based on what the page actually needs to do. HybridCache gives Umbraco a better foundation for large sites, but it also makes performance patterns more visible. And honestly, that is probably a good thing. Download the slides I’ve shared the full slide deck from the presentation if you want to dig into the examples, benchmarks and diagrams in more detail. Download the slidesMarkus Johanssonhttps://joe.gl/ombek/blog/codegarden-packing-list/58c35289-50d3-448e-abce-8e0c314d2d54Thu, 04 Jun 2026 10:14:30 GMTWow, hasn't time flown?! This weekend I'll be boarding my plane to Denmark ahead of Codegarden 2026 so it's about time we thought about packing our bags! But what to bring? If you've not been before, or if you're forgetful like I am, I've written you a packing list...Joe Glombekhttps://www.jeroenbreuer.nl/blog/umbraco-openid-connect-example-with-lightweight-external-members/e547bf8c-9056-4b31-8e4e-47f01df837ecTue, 02 Jun 2026 17:37:28 GMTThe Umbraco OpenID Connect example has been updated to Umbraco 17.4.2 with support for lightweight external members . This stores members from an external provider as a minimal record instead of a full content entity.Jeroen Breuerhttps://owain.codes/blog/2026/june/speed-up-slow-deployments-to-umbraco-cloud/fffd4c8c-2ad6-49c5-a4e9-dd2639c520e0Tue, 02 Jun 2026 00:00:00 GMTOwain Williams