UMB.FYI Firehose - News

Skrift Issue #129

Tue, 07 Jul 2026 00:00:00 Z

Featuring guest posts by Bogdan Kosarevskyi on "The tip of the observability iceberg: depth is not measured in meters, but in levels of observation" and Hubert Galuszka on "Virtual Members: Passwordless Umbraco Auth Without the Identity-Provider Bill"

ThtaAi

Tue, 07 Jul 2026 00:00:00 Z

AI-powered content generation for the Umbraco backoffice. Uses a local LLM (or other LLM API) to generate page content, block content, and full pages from natural-language prompts, with editorial review before anything publishes.

Security Advisory, July 7, 2026: Security Patches are now available

Tue, 07 Jul 2026 00:00:00 Z

Summary: A vulnerability classified as high has been found and fixed in Umbraco 13, 17, and 18.

Limbo.Umbraco.TextBox 17.0.0-alpha001

Mon, 06 Jul 2026 11:46:55 Z

Limbo Textbox (or Limbo.Umbraco.TextBox) is a package that adds new textbox and textarea property editors for Umbraco 10+. While having similar functionality to the build in property editors, this package adds a few extra features.

New Giscus powered comments and H5YR widget!

Sat, 04 Jul 2026 19:18:36 Z

I've added a giscus powered comments, and the awesome H5YR widget, to my blog posts!

Letting AI agents loose on Examine

Fri, 03 Jul 2026 17:45:20 Z

I'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, and honestly it went a fair bit better than I expected. We'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. If I'm not, I close it and it learns for next time. 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
Another 13 bug-fix PRs from the Copilot coding agent (more on those below)
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. This is 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 it isn't allowed to just claim an improvement - it's flat out forbidden from doing that. Every change has to come with a benchmark. 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 we 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 us a string[]) plus some allocation trimming got us 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 <remarks> 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.

It's not just perf, it fixes bugs as well

Alongside the scheduled perf work, I leaned on the Copilot coding agent for the gnarlier stuff - the kind of bug that needs actual investigation. A big one was the SyncedFileSystemDirectoryFactory (the default directory factory for Umbraco) getting into a permanent index outage when a temp index file was transiently locked, along with taxonomy replication getting out of sync. Those are exactly the sort of intermittent, hard-to-reproduce issues that can eat a whole weekend. The agent investigated, reproduced it, and proposed fixes that made the searcher lazily resettable and hardened the replication, and those shipped in the v3.x and v4 beta releases.

Was it actually worth it?

Honestly, yes. And I want to be straight about it, because there's a lot of AI hype flying around at the moment and most of it deserves a healthy dose of scepticism.

The bit that sold me wasn't that the agents are magic, because they're not. It's 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, and decide in a couple of minutes. When the agent isn't sure about something the prompt tells it to do nothing rather than post noise, and for the most part it actually behaves. The stuff that isn't good enough I just close, and it moves on.

It's not zero effort - I still read every change and I've closed plenty that weren't worth it. 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 that 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 genuinely 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 of this work the agents have been doing to tighten up Examine's query and indexing hot paths feeds straight through into ExamineX as well - 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 that search running as a managed service instead of hosting Lucene indexes on your own servers, that's what ExamineX is there for. 🙂

Umbraco London July Meetup .. the write- up

Fri, 03 Jul 2026 09:18:14 Z

Umbraco london is trying something silly a short unprogrammed stream of useless brain fog.

Continue reading on Medium »

uProfile July 2026 - Georgina Bidder

Fri, 03 Jul 2026 00:00:00 Z

Meet Georgina: From the deep end to the Codegarden stage: Meet Core Collaborator Georgina Bidder!

Creating A Safe Space for Editors to Be Wrong

Fri, 03 Jul 2026 00:00:00 Z

I 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...

Phases.Umbraco.ContentSearch

Fri, 03 Jul 2026 00:00:00 Z

Advanced content search for the Umbraco backoffice. Editors can search content by document type and property, view results in a sortable grid, export to CSV or Excel, and save searches for later.

UMBRAAD 2026 | Accessibility Manual Testing: Why Lived Experience Matters - Thiago Carmo

Thu, 02 Jul 2026 07:48:53 Z

Accessibility Manual Testing: Why Lived Experience Matters by Thiago Carmo UMBRAAD is a free virtual Umbraco community event packed with practical talks, live demos, and expert Q&A sessions on building a more inclusive web. Read more on https://umbraad.com

UMBRAAD 2026 | Accessibility Debt in Digital Products - Shivansh Mathur

Thu, 02 Jul 2026 07:28:49 Z

Accessibility Debt in Digital Products: What AI Fixes and What It Doesn't by Shivansh Mathur UMBRAAD is a free virtual Umbraco community event packed with practical talks, live demos, and expert Q&A sessions on building a more inclusive web. Read more on https://umbraad.com

UMBRAAD 2026 | Write Once, Reach Everyone: Accessible Writing - Corey Vilhauer

Thu, 02 Jul 2026 07:24:46 Z

Write Once, Reach Everyone: Accessible Writing and GEO Want the Same Solution by Corey Vilhauer UMBRAAD is a free virtual Umbraco community event packed with practical talks, live demos, and expert Q&A sessions on building a more inclusive web. Read more on https://umbraad.com

UMBRAAD 2026 | Why Automated Accessibility Tools Are Not Enough - Shadrack William Kyei

Thu, 02 Jul 2026 07:19:35 Z

Why Automated Accessibility Tools Are Not Enough by Shadrack William Kyei UMBRAAD is a free virtual Umbraco community event packed with practical talks, live demos, and expert Q&A sessions on building a more inclusive web. Read more on https://umbraad.com

UMBRAAD 2026 | What No One Tells You About Working in Accessibility - Danny Lancaster

Thu, 02 Jul 2026 07:16:46 Z

What No One Tells You About Working in Accessibility by Danny Lancaster UMBRAAD is a free virtual Umbraco community event packed with practical talks, live demos, and expert Q&A sessions on building a more inclusive web. Read more on https://umbraad.com

UMBRAAD 2026 | Shift Left on Accessibility: Beyond the Audit - Ramona Domen

Thu, 02 Jul 2026 07:13:10 Z

Shift Left on Accessibility: Beyond the Audit by Ramona Domen UMBRAAD is a free virtual Umbraco community event packed with practical talks, live demos, and expert Q&A sessions on building a more inclusive web. Read more on https://umbraad.com

UMBRAAD 2026 | Designing for cognition - Ellie Barrett

Thu, 02 Jul 2026 07:05:11 Z

Designing for cognition by Ellie Barrett UMBRAAD is a free virtual Umbraco community event packed with practical talks, live demos, and expert Q&A sessions on building a more inclusive web. Read more on https://umbraad.com

UMBRAAD 2026 | Automating Accessibility Audits - Jordan Smith

Thu, 02 Jul 2026 07:00:43 Z

Automating Accessibility Audits: Building a Full-Pipeline A11Y Scanning & Reporting Tool by Jordan Smith. UMBRAAD is a free virtual Umbraco community event packed with practical talks, live demos, and expert Q&A sessions on building a more inclusive web. Read more on https://umbraad.com

UMBRAAD 2026 | Accessibility starts before the software - Carl Sargunar

Thu, 02 Jul 2026 06:44:05 Z

Accessibility starts before the software: hardware, cloud tooling, LLMs and diminishing returns by Carl Sargunar. UMBRAAD is a free virtual Umbraco community event packed with practical talks, live demos, and expert Q&A sessions on building a more inclusive web. Read more on https://umbraad.com

The Agent-Ready CMS: Enable the ecosystem

Thu, 02 Jul 2026 00:00:00 Z

Learn how Umbraco’s MCP platform and software factory empower partners and clients to build agentic AI tools for a truly agent-ready CMS ecosystem.

Umbraco.Community.ImageSharp.TrimCache

Thu, 02 Jul 2026 00:00:00 Z

Scheduled, age-based trimming of the ImageSharp.Web image cache for Umbraco. Supports both the Azure Blob cache and the local physical cache, keeping the cache from growing unbounded (for example exceeding Umbraco Cloud media-storage limits). Old variants are removed in the background and regenerated on the next request. Supports Umbraco 13, 17 and 18.

Ideo.Umbraco.MediaManager

Thu, 02 Jul 2026 00:00:00 Z

Safe, async media cleanup for Umbraco v17: find and remove orphaned media nodes and orphaned physical files, guarded by a deep reference scan, with dry-run preview and Recycle Bin safety.

Codegarden 2026 - a little late, because it gave me something to build

Wed, 01 Jul 2026 15:53:03 Z

A 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 repository

Growcreate.LibraryMigrator

Wed, 01 Jul 2026 00:00:00 Z

A backoffice package for Umbraco 18+ that migrates content saved as Element Types to the new Library (reusable elements) feature introduced in Umbraco 18.

PostgreSQL provider for Umbraco Search

Wed, 01 Jul 2026 00:00:00 Z

Introducing a PostgreSQL powered search provider for Umbraco Search.

Using Umbraco.Automate to populate content from an API

Wed, 01 Jul 2026 00:00:00 Z

Learn how to automatically populate Umbraco content from an external API using Umbraco.Automate, with a hands-on PokéAPI example and video demo.

Casko.XmlSitemapsForUmbraco

Wed, 01 Jul 2026 00:00:00 Z

Xml Sitemaps package for Umbraco CMS.

uTPro.Feature.SimpleFormBuilder

Wed, 01 Jul 2026 00:00:00 Z

Lightweight form builder for Umbraco 16, 17 and 18 backoffice. Create, manage, and render dynamic forms with 19+ field types, groups/columns layout, client-side validation, sensitive data encryption, multi-language support, custom field extensibility, entry storage, and public submit/render APIs. Render any form with a single ViewComponent call.

U17

Tue, 30 Jun 2026 18:17:02 Z

This site has started as an Umbraco v4.x site, and has been regularly upgraded since then, never completely rebuilt. It has been running Umbraco 13 for about 3 years now, and it is about time to upgrade to Umbraco 17.

Packages

This is the easy part. The solution contains two projects: a Core project, and a UI project. Open each .csproj file, bump TargetFramework from net8.0 to net10.0, bump Umbraco package references from 13.0.2 to 17.4.0, bump a few other packages as per NuGet's suggestions.

The excellent Breaking Changes documentation tells us to remove RazorCompileOnBuild and RazorCompileOnPublish so, let us do it. It also tells us to clean our Program class a little. Remove a .AddDeliveryApi() call, remove a .UserInstallerEndpoints() calls, that is it.

At this point, rebuilding fails.

ModelsBuilderSettings.ModelsMode used to be an enum, looks like it is now a string. Quite simple to fix. Everything that queried the IPublishedContentCache does not compile anymore, porting to IPublishedContentQuery is trivial. There is no IContentService.SaveAndPublish() anymore, apparently, and one needs to Save() then Publish().

All in all, nothing dramatic.

Some of my custom Markdown property editor and converter will not compile, I am going to comment them out for the time being.

And... it builds.

Database

Trying to boot the site fails... with a BootFailedException. A migration seems to want to delete a non-existing constraint named DF_umbracoUser_createDate. A quick Internet search shows that this happened to others as well, so something must have gone wrong with migrations at some point. Not going to troubleshoot, creating the missing constraints before upgrading is quicker:

 ALTER TABLE umbracoUser ADD CONSTRAINT DF_umbracoUser_createDate DEFAULT GETUTCDATE() FOR createDate;
 ALTER TABLE umbracoUser ADD CONSTRAINT DF_umbracoUser_updateDate  DEFAULT GETUTCDATE() FOR updateDate;

And presto... the site upgrades, boots, and I can log into the back-office.

Data Types

A range of data types are gone or have changed. And of course my custom data types are CompletelyBroken™ which is not a surprise, since the back-office UI has been entirely rebuilt.

First, native data types. Basically, go into the Data Types back-office section, and re-assign those that have issues to the proper property type. Rather simple. Weird enough, a content list datatype is throwing in the back-office, because of its orderBy value. Something a migration did not catch? Manually re-saving the datatype fixes it.

And then, I actually use two custom data types:

ZpqrtBnk.ImgFocus is an image focus data type which is an alternative to crops. It allows the user to define a rectangle that represents the "zone of interest" of an image. That zone is defined on the media itself. Next, whenever we need to render the media, we can automatically figure out the best crop based upon this zone.
ZpqrtBnk.Markdown is a custom Markdown data type that uses the back-office widget pretty much unchanged, but implements some rendering helpers for links or images.

As far as Markdown is concerned, I was using a property editor in order to support additional custom syntax. Turns out a property editor is not needed anymore, a plain IMarkdownToHtmlConverter implementation is all that is needed. So, the property editor is gone, and it is way nicer this way.

On the other hand the image focus editor needs to be completely rebuilt.

My First Property Editor

There is some nice documentation about property editors in v17, so let us follow it.

mkdir PropertyEditors
cd PropertyEditors
npm create vite@latest ZpqrtBnk.ImgFocus
# with Lit
# with TypeScript
# without Vite RollDown (but I was not proposed it)
cd ZpqrtBnk.ImgFocus
npm i && npm install -D @umbraco-cms/backoffice@17.4.0
rm -rf public/* src/*

Then,

Update vite.config.ts
Create src/zpqrtbnk-imgfocus.element.ts
Create public/umbraco-package.json

Is all it takes. OK, it takes a bit of time to figure out how to put everything together but hey, this is my very first time with the new UI. The end result is quite polished. As in, it makes way more sense than the convoluted Angular version.

In the end,

npm run build

Drops files in my site's App_Plugins and we are done. As in, it just works. I have to say the experience is quite pleasant.

Models

We are not entirely done with backend work. A few more things have changed, including the CLR type of objects returned by various data types.

The new MediaPicker3 for instance does not return a plain IPublishedContent, but a MediaWithCrops. I do not care about crops. And I had a media converter ensuring that the property value type would be reported as Image in case the picker can only pick one single image. So... that converter needs a bit of update to report the proper type, and to unwrap MediaWithCrops to Image wherever appropriate.

And then, with the various changes applied to property types, I though I would rebuild my models. Turns out they were built using the Our.ModelsBuilder edition of the Models Builder, not the built-in one, because I am using some extra features.

Front-End Time

At this point, I have a running back-office, clean data types (though missing my Markdown converter, but that will be fixed later), everything is nice, time to test the front-end.

And... it does not work.

Umbraco Automate demo, Umbraco Codegarden 2026

Tue, 30 Jun 2026 08:41:04 Z

Discover the capabilities of Umbraco Automate, a native workflow automation tool integrated directly into the Umbraco back office. This session provides a comprehensive look at how you can create, manage, and execute complex automation chains triggered by backend events like content modifications or media uploads. Learn how the architecture coordinates triggers and actions, allowing you to build intricate logic chains across the entire Umbraco ecosystem. The presentation details native integrations with Umbraco Engage, Forms, Commerce, Deploy, and AI Agents, demonstrating how workflows can operate autonomously when ecosystem events occur. Who This Video Is For This video is designed for Umbraco developers, system architects, and content administrators looking to streamline backend operations. Understanding these automation workflows will help teams eliminate repetitive tasks, integrate external systems seamlessly, and safely embed AI utilities into their daily content management processes. Chapters 00:00 - Introduction to Umbraco Automate 00:38 - Understanding Triggers, Actions, and Logic Chains 00:54 - Ecosystem Integration: Forms, Commerce, Deploy, and AI 01:18 - Demo: Content Saved Trigger & Slack Notification Setup 02:34 - Demo: Connecting AI Agents and Webhooks 03:48 - Demo: Automated Media Transcription on Upload 05:26 - Implementing a Human-in-the-Loop Approval Step 06:30 - Community Packages and Early Access Extensions 07:34 - Open Source Availability and Wrap-up Key Takeaways Native Workflow Engine: Build and manage complex automation chains directly within the Umbraco back office without relying on external third-party integration platforms. AI & Webhook Extensibility: Send data to AI agents for automated summaries or transcriptions, and route outputs to external endpoints via standard HTTP webhooks. Human-in-the-Loop Guardrails: Insert manual approval gates into automated processes to pause execution until an administrator reviews and verifies the data. Ecosystem & Community Ready: Supports core Umbraco products alongside popular community packages like Translation Manager for automated translations and Newsletter Studio for transactional mailing lists. Free and Open Source: Umbraco Automate is fully open source and available for immediate deployment. Important Links Umbraco Automate Project Page: [Insert Link] Launch Announcement & Documentation: [Insert Link] Community Extension Guide: [Insert Link] Featured Session - AI and Umbraco by Matt: [Insert Link]

Knowit.Umbraco.AiTranslate

Tue, 30 Jun 2026 00:00:00 Z

A guided AI translation dashboard for Umbraco. Pick a language pair (or create a new language), choose pages or the whole site, and translate content into other languages using your Umbraco.AI profile. Media references are carried over, link titles are translated, and everything is saved as drafts for review. Requires the Umbraco.AI package.

umContentTranslator

Tue, 30 Jun 2026 00:00:00 Z

Umbraco backoffice package for translating content nodes using OSKI Content Translator.

Going from Umbraco 13 to 17

Tue, 30 Jun 2026 00:00:00 Z

Upgrading from Umbraco 13 to 17 LTS? Discover the two main migration paths and learn how Umbraco Cloud can smooth your transition before the 2026 EOL date for Umbraco 13.

OC.Automate.LinkedIn

Tue, 30 Jun 2026 00:00:00 Z

LinkedIn integration for Umbraco Automate. Post content to LinkedIn as part of your automation workflows.

Phases.Umbraco.Community.TemplateHistory

Tue, 30 Jun 2026 00:00:00 Z

Track version history for Umbraco templates, stylesheets, scripts, and partial views. Compare diffs side-by-side or unified, restore previous versions, and browse recent changes from a dedicated History workspace tab and Settings dashboard.

Advanced Permissions meets Umbraco 18!

Sun, 28 Jun 2026 19:49:52 Z

A 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.advancedpermissions

OC.Automate update

Sun, 28 Jun 2026 00:00:00 Z

OC.Automate.LinkedIn is out of beta and OC.Automate.Bluesky and OC.Automate.Mastodon are all working on Umbraco 18

[Breaking change]: Umbraco Search replaces existing search in Umbraco 19

Fri, 26 Jun 2026 11:38:19 Z

What we're most excited about on the new Community site - part 1 of 2

Fri, 26 Jun 2026 11:16:40 Z

What we're most excited about on the new Community site - part 1 of 2 | Umbraco Community

umbraCoffee - Codegarden 2026 Wrapped 🌯

Fri, 26 Jun 2026 09:00:07 Z

Welcome to your monthly dose of #umbraCoffee! Your hosts - Marcin and Callum - together with their guest(s) will drive through all of the community news and happenings in the Umbraco world. So... grab a cuppa, join us LIVE and enjoy! See ya?! --- ☕ Wanna buy us a coffee/pizza/donuts? https://www.buymeacoffee.com/umbracoffee --- Topics: //ToDo:

Umbraco Automate

Fri, 26 Jun 2026 00:00:00 Z

Umbraco.Community.EntityActions.ForceDelete

Fri, 26 Jun 2026 00:00:00 Z

A Umbraco community package that adds an entity action to force delete documents.

Umbraco.Community.SchemeWeaver.AI

Fri, 26 Jun 2026 00:00:00 Z

AI-powered schema mapping for SchemeWeaver using Umbraco.AI

Umbraco Automate Workflows

Fri, 26 Jun 2026 00:00:00 Z

Building with Claude and Umbraco: Setting Up MCP and Creating Content with AI

Thu, 25 Jun 2026 16:00:16 Z

I'll be honest, when Jason first mentioned setting up an MCP server to connect Claude to our Umbraco dev environment, I assumed it was going to be a difficult dev-heavy project that would take the day at least, and be a bit past my coding comprehension ability as a Front End Developer. I even made a new local branch assuming I was going to have to write and commit code.

Nope! It wasn't like that at all. And I'm still a little surprised about it. It was just setting up a config file in Claude and setting up API users in Umbraco.

If you're an Umbraco developer who's been curious about AI-assisted content workflows but figured the setup overhead wasn't worth it, this post is for you. I'm going to walk through exactly what I did, what tripped me up (spoiler: one small thing), and what became possible on the other side of it.

Part 1: What Is the Umbraco MCP Server, Anyway?

MCP stands for Model Context Protocol. It's an open standard that lets AI assistants like Claude connect directly to external tools and services, not just chat about them, but actually interact with them.

The Umbraco MCP server is an implementation of that standard for Umbraco. Once it's set up and connected, Claude can read and write content in your Umbraco instance through the Management API. We're talking creating pages, updating properties, working with block components, the same things you'd do in the back office, but driven by Claude. It's actually pretty amazing to see it work.

Part 2: Setting Up the MCP Server

Before anything else, a quick note on prerequisites. You'll need an Umbraco site to connect to (we're using our dev environment), and Claude Desktop or Cowork installed on your machine. That's really it on the "before you start" front, which was the first pleasant surprise.

The MCP server itself is configured through a JSON config file in Claude. Go to your Claude settings, then Developer, and click the "Edit Config" button to bring up the claude_desktop_config.json file in your favorite editor.

Note: Close Claude completely (including killing it in the taskbar) while working on the config file. If Claude is running, it will overwrite your changes when it closes.

Note: Make sure you're on the latest version of Node before you start.

Drop this into your config file, change the name as you like, change the BASE_URL to your site, and we'll cover the CLIENT_ID and SECRET in the next steps.

"mcpServers": {
  "YOUR-umbraco-dev-mcp-server": {
    "command": "npx",
    "args": [
      "@umbraco-cms/mcp-dev@latest"
    ],
    "env": {
      "UMBRACO_CLIENT_ID": "umbraco-back-office-api-user",
      "UMBRACO_CLIENT_SECRET": "12345-GUID-OR-PASSWORD-6789",
      "UMBRACO_BASE_URL": "https://your-site.io",
      "UMBRACO_INCLUDE_TOOL_COLLECTIONS": "document,media,document-type,data-type"
    }
  }
}

Part 3: Creating an API User in the Umbraco Back Office

This is the part I was most nervous about. "API user" sounds like something that involves a terminal and a lot of Googling. It does not. It's just a few clicks in the Umbraco back office and I was genuinely a little embarrassed by how straightforward it was.

Head into your Umbraco back office and navigate to the Users section. We're going to create both a new User Group and a new API user. First, the User Group. Create one and call it MCP-User-Developer and give it as much control as a developer would. If you ever wanted another group called MCP-User-Editor with less control, you can do that too. For now, add Content, Media and Settings sections and turn on everything you'd like it to have access to.

Next, go to Users and create a new API User. Name it something like "something-mcp-developer" and make it a member of the MCP-User-Developer group we just made. Add an email address for its username and check on access to start nodes (or give it full access).

Now the key step: click the Client Credentials button to add the key we'll need in the Claude config file. The ID will have a prefix of "umbraco-back-office" and then you name it whatever you want. In my example I went with "api-user", so the full ID becomes "umbraco-back-office-api-user". For the Secret, generate a GUID or secure password however you like.

Note: Once you click Create, the password won't be visible again. Save it somewhere before moving on!

Now we have all the info for the config file. Go back and add "umbraco-back-office-api-user" to the UMBRACO_CLIENT_ID and your password to the UMBRACO_CLIENT_SECRET.

Part 4: Connecting Claude to Your Umbraco Site

At this point you've got the config file set up and your API user created. The last step is getting Claude to actually recognize the connection. Save your claude_desktop_config.json file and restart Claude. Go to Settings, then Developer again, and you should see your MCP server listed there and running.

I was stuck here for a bit because I was not on the latest version of Node, and also because I had the UMBRACO_CLIENT_ID wrong. Woops! So make sure your config has all the correct info. But if everything checks out you should see a "running" label next to your server, and you're now connected!

A quick way to confirm everything is working is to just ask Claude something simple about your site. Something like "list the pages under the home node" or "what document types are available?" If Claude comes back with real data from your Umbraco instance, you're in business. As soon as it gave me the ID of the home node of our dev site, I knew things were about to get real.

Part 5: Creating Content with Claude

This is the fun part.

Once Claude is connected to your Umbraco instance, you can start asking it to do real content work. Not just drafting copy in the chat window, but actually creating and populating pages inside Umbraco. I started simple, asking Claude to create a Basic Page under the home node with a title and some body text. It did it. First try. I went and checked the back office and there it was, sitting as a draft, ready to review.

From there I started pushing it further. Our Basic Page document type has a bunch of block components available, things like Feature Boxes, Statistics, Testimonials, FAQ sections, Numbered Steps, and a Two-Column Comparison block. I described what I wanted the page to be about and asked Claude to use as many relevant components as made sense for the content. The results were genuinely impressive, well-structured pages with appropriate blocks chosen for the content, not just a wall of rich text.

A few tips from what I've learned so far:

Give Claude context about your document types. The more it knows about your block components and what fields they have, the better the output.
Keep pages as drafts first. Claude creates content as drafts by default, which is exactly what you want. Review before publishing.
Be specific about tone and content. Claude will make reasonable choices on its own, but the more direction you give it, the closer the first draft will be to what you actually want.
Watch out for placeholder content. Claude may generate fictional quotes or statistics as placeholders. Always review before anything goes live.

One small thing to be aware of: on our setup, pages created via the MCP server sometimes needed the template set manually in the back office before they'd render on the front end. It's a quick fix, just one more thing to check on your first run through.

Part 6: Real-World Use Cases

So what's this actually good for in practice? After spending some time with it, here are the use cases that have stood out most.

Spinning up draft pages quickly. If you've got a list of pages that need to exist, Claude can create and populate them fast. What might take an editor an afternoon of copying, pasting and formatting can happen in minutes. The drafts still need a human review pass, but you're starting from something solid rather than a blank page.

Consistent page structure across a site. When Claude is working from the same document type and block components every time, the output is naturally consistent. Every page gets a hero, a logical block order, appropriate use of the available components. It's a lot harder to end up with that one orphaned page that's formatted completely differently from everything else.

Exploring content strategy. This one surprised me. Being able to say "create a page making the case for upgrading Umbraco and use whichever block components make sense" and get back a fully structured draft is genuinely useful for figuring out what you actually want to say. It's a fast way to go from a topic to a first draft you can react to.

Auditing and rewriting existing content. Claude can read your existing pages too, which means you can ask it to review copy, flag inconsistencies, or suggest rewrites across multiple pages without touching the back office yourself.

Like I said, I knew things were about to get real.

We're still figuring out the best workflows ourselves at ProWorks, but it's already changing how we think about content production. I'm excited to see where it goes from here.

If you have questions or want to share what you've built with it, feel free to reach out.

Alan Ballard, Front End Developer, ProWorks

Umbraco MCP as a Platform Intoduction

Thu, 25 Jun 2026 10:11:03 Z

Phil Whittaker and Bolette Kern introduce the "Umbraco in AI" framework, showcasing how the Umbraco Management API exposes content, media, document types, and search configurations to modern AI models. This session highlights how to bridge the CMS with artificial intelligence using the Model Context Protocol (MCP) and dedicated command-line tools. Learn how to move beyond local environments using Hosted MCP servers with secure OAuth authentication, connect terminal environments directly via the new CLI tool, and use the Base MCP SDK to make custom Umbraco packages agent-ready. The talk also explores advanced architectural patterns like MCP chaining and an automated five-phase Software Factory. This video is for Umbraco package authors, digital agencies, and platform developers looking for a structured path to implement AI agents. By leveraging these official tools, development teams can eliminate manual integration plumbing and focus entirely on building custom logic, strategy, and creative experiences for clients. Key Takeaways: - Management API Core: Serves as the central translation engine, transforming structured CMS capabilities into discoverable data points that LLMs can read, reason about, and automate. - Multi-Channel Architecture: Support for Local MCP (on-machine agents), Hosted MCP (cloud remote agent access via secure user authentication), and a developer-centric CLI tool. - Marketplace Readiness: The official Base MCP SDK enables package authors to instantly convert existing OpenAPI schemas into functional MCP servers with minimal overhead. - The Five-Phase Software Factory: A command-line toolkit that handles boilerplate scaffolding, project configuration, API schema discovery, tool generation, and automated integration/evaluation testing. - Advanced MCP Chaining: Eliminates redundant manual configurations through structural orchestration patterns like proxying, delegation, and composite multi-step tools. Timeline Chapters: 00:00 - Introduction to the Umbraco in AI Strategy 00:59 - Interactive Integration Diagram Overview 01:07 - The Central Role of the Umbraco Management API 01:29 - Stage 1: The Local Developer MCP Foundation 02:10 - Stage 2: Hosted MCP and Custom ChatGPT App Setup Demo 03:24 - Native Connections via the CLI Tool and Claude Code Integration 05:08 - Unpacking the Differences: Local MCP vs. Hosted MCP vs. CLI 06:49 - Stage 3: Making Umbraco Packages Agent-Ready with the Base SDK 07:43 - Stage 4: Scaffolding a Server Using the Five-Phase Software Factory 09:57 - Stage 5: Advanced MCP Chaining (Proxying, Delegation, and Composite Tools) 11:07 - Composing Shared Capabilities Across Custom MCP Servers 11:51 - Stage 6: The New Umbraco in AI Documentation Section 12:12 - Summary: Lowering Barriers and Reducing Friction for Digital Agencies Resources and Links: Official Umbraco in AI Documentation: https://docs.umbraco.com/umbraco-in-ai Model Context Protocol (MCP) Core Concepts: https://docs.umbraco.com/umbraco-in-ai/concepts/model-context-protocol Base MCP Package Guide & Repository Info: https://docs.umbraco.com/umbraco-in-ai/mcp/base-mcp Developer MCP Server Configurations: https://docs.umbraco.com/umbraco-in-ai/mcp/cms-developer-mcp Umbraco AI strategy: www.umbraco.com/ai Umbraco Official CMS Resources: www.umbraco.com

Unboxing Umbraco 18

Thu, 25 Jun 2026 10:10:54 Z

Join us for a developer's perspective on Umbraco 18, the new Standard-Term Support release of the CMS. We discuss the new Elements feature, typed OpenAPI schemas for the Delivery API, and the move from Swashbuckle to Microsoft.AspNetCore.OpenApi. We also look at features you may have missed in recent Umbraco 17 minors, and explain the plan for Umbraco 17 - the current Long-Term Support release. Chapters: 00:00 Introduction 00:51 Releases review 02:50 A look at Elements 14:06 Typed OpenAPI schemas for the Delivery API 18:29 Moving from Swashbuckle to Microsoft.AspNetCore.OpenApi 21:10 The new login screen! 23:30 Umbraco 17 minors review 23:51 Umbraco 17.4 changes for AI 27:36 Upgrade considerations 29:21 Finding more information Related resources: Dive into the Umbraco 18 final release blog post: [URL] Visit our Umbraco 18 product page: https://umbraco.com/products/umbraco-cms/umbraco-18/ Ready to learn more? Explore the Umbraco 18 documentation: https://docs.umbraco.com/umbraco-cms Specific documentation links: Version-specific upgrade instructions: https://docs.umbraco.com/umbraco-cms/18.latest/get-started/upgrading-and-migrating/version-specific Umbraco 18 Release Candidate blog post: https://umbraco.com/blog/umbraco-18-release-candidate/ Laura's blog post on migrating away from Swashbuckle: https://dev.to/lauraneto/umbraco-18-and-openapi-a-heads-up-for-extension-developers-1k7 Filip's product update from Codegarden: https://umbraco.com/blog/umbraco-product-updatecodegarden-keynote-highlights-q2-2026/ Andy Butland's CMS Roadmap talk from Codegarden: https://www.youtube.com/watch?v=HO0BsEebTys

Clean Starter Kit v8 Released

Thu, 25 Jun 2026 08:07:26 Z

Clean Starter Kit v8 released for Umbraco 18. Explore the new element library features, block list labels workaround, and runtime migration solution for categories.

Umbraco.Community.MemberLogin

Thu, 25 Jun 2026 00:00:00 Z

Sign in to the front-end as a member from the Umbraco backoffice, with optional culture and redirect page, opening in a new tab.

Krebil.UmbracoAzureSearch

Thu, 25 Jun 2026 00:00:00 Z

Plug Azure AI Search into Umbraco Search as a fully-featured provider: filtering, faceting, sorting, culture/segment variants, and protected content out of the box.

Umbraco 18 Release

Thu, 25 Jun 2026 00:00:00 Z

The latest Major Release of Umbraco is here: Umbraco 18. Including Phase One of Elements for reusable content management, and typed OpenAPI schemas for the Delivery API. Upgrade today

Phil Whittaker, Umbraco in AI

Wed, 24 Jun 2026 11:15:38 Z

AI agents are becoming part of how we build and manage digital experiences. In this session, we explore how Umbraco works in an AI-first world - from a base MCP server and chained MCP architecture to Agent Skills for the backoffice, implementation, and content modelling. Learn how we’re reducing friction so LLMs and agents can interact with Umbraco using shared best practices.

Validating an Umbraco 13 to 17 Upgrade with a Sitemap Audit

Wed, 24 Jun 2026 10:54:04 Z

How 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....

Lait.Umbraco.Content.DragAndDrop

Wed, 24 Jun 2026 00:00:00 Z

Drag-and-drop and keyboard reordering for the Umbraco backoffice Content tree, plus the ability to drag an item out of a collection (list view) and drop it anywhere in the content tree. Three-zone drop targets, cross-parent moves, a move-in-progress spinner and WCAG-compliant keyboard grab & place.

SA.Automate.WeatherApi

Wed, 24 Jun 2026 00:00:00 Z

WeatherAPI.com connection types and actions for Umbraco Automate. Get the current weather for a location as part of an automation workflow.

Kenn Jakobsen, It's Elemental; reuse your content!

Tue, 23 Jun 2026 12:44:00 Z

Reusable content has arguably been one of the most requested features in Umbraco since forever. Umbraco 18 is just around the corner, and along with it comes Elements - a brand new way of managing content items that can be shared freely between pages. It's a fully-fledged content editing experience, built for content reuse. What's more, Elements promise a seamless integration with block editors such as Block List and Block Grid, making it an even more appealing choice for editors. In this session I'll give you the grand tour of Elements. Expect lots of demos and sneak peaks of what's to come.

Matt Brailsford, AI in Umbraco

Tue, 23 Jun 2026 09:19:15 Z

The core principle of Umbraco AI is to be a basis for custom AI integrations. Whilst the Prompt and Agent add-ons provide out of the box functionality, the real power of Umbraco AI is in its extension points. In this session we'll take a look at the various way in which you can extend Umbraco AI and build your own custom AI solution on top of it.

Bolette Kern, Umbraco CMS in the Age of AI

Tue, 23 Jun 2026 08:19:07 Z

AI in Umbraco. Umbraco in AI. And the question underneath both: how do you work with a CMS platform for a future no one can predict? In this talk, I'll present and demo the latest on both AI tracks, explore the changing role of content management, and why it's even more important now, and take a look at the next editor-facing features coming to the CMS.

Extending Tiptap in Umbraco – a real world list example

Tue, 23 Jun 2026 07:37:36 Z

If 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 `<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.75"><text x="1" y="7.5" font-size="4.5" fill="currentColor" stroke="none" font-family="serif" font-style="italic">i.</text><path d="M9 6h12"/><text x="1" y="13.5" font-size="4.5" fill="currentColor" stroke="none" font-family="serif" font-style="italic">ii.</text><path d="M9 12h12"/><text x="1" y="19.5" font-size="4.5" fill="currentColor" stroke="none" font-family="serif" font-style="italic">iii.</text><path d="M9 18h12"/></svg>`;

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<typeof UmbTiptapExtensionApiBase>) {
    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.

SA.Automate.Ntfy

Tue, 23 Jun 2026 00:00:00 Z

ntfy connection types and actions for Umbraco Automate. Send notifications to ntfy as part of an automation workflow.

SA.Automate.Pushover

Tue, 23 Jun 2026 00:00:00 Z

Pushover connection type and action for Umbraco Automate. Send notifications to Pushover as part of an automation workflow.

Knowit.Umbraco.EditorLock

Tue, 23 Jun 2026 00:00:00 Z

Prevents two editors from changing the same content node at the same time. When a node is already open, a second editor gets a read-only view with a red border and can either Request access (the current editor is prompted to accept or decline) or Force access (an immediate takeover with confirmation). Locks auto-release when the holder disconnects or goes idle, so nodes never get stuck. Real-time over SignalR.

The Pragmatic Enterprise: Balancing AI Innovation with Predictable TCO

Tue, 23 Jun 2026 00:00:00 Z

Limbo.Umbraco.Video 17.0.0-alpha001

Mon, 22 Jun 2026 18:05:01 Z

Package serving as a base for Limbo's video picker packages.

Bjarke Berg, Running Umbraco in a Changing World

Mon, 22 Jun 2026 11:23:06 Z

The web has changed. The traffic each Umbraco site is being asked to handle today looks very different from what it did just two years ago — and most of the growth isn't humans. AI has collapsed the cost of automated traffic, bots and probes are part of daily life on the open internet, and defaults that were merely sensible in 2024 are mandatory in 2026. There's plenty to talk about, and as ever, Codegarden is a great time to share where we are with you. This talk will cover what running Umbraco actually looks like in 2026 — no matter where you host. We'll walk through the highlights from the last twelve months on Umbraco Cloud, the things that have landed and the things about to. We'll dig into the dimensions every serious Umbraco operator should be thinking about right now: security, performance and operations. And we'll look at where the platform itself is heading next — there's a new chapter beginning, and we'll spend real time on what it means for you. Attend this talk and you will leave with a clear picture of what has changed about running Umbraco — and one concrete thing to check on every site you operate tomorrow morning. You'll be just as excited as we are about what's coming next on Umbraco Cloud, and familiar with the roadmap for what the future holds in the upcoming releases.

Umbraco Keynote, Mats Persson, Emma Bustow & Filip Bech-Larsen

Mon, 22 Jun 2026 10:51:13 Z

Creating and updating your website should be the least of your worries. With Umbraco, you get a content management system known and loved for its flexibility and great editing experience. Umbraco is easy to get started with install, set up, and host it yourself or let us take care of it all for you on Umbraco Cloud. https://try.umbraco.com Learn more about Umbraco on our website https://umbraco.com Discover our Umbraco Community: https://community.umbraco.com/ Find the Umbraco source code on Github: https://github.com/umbraco/Umbraco-CMS Visit the Umbraco Documentation: https://docs.umbraco.com

Arnold Visser, Build. Scale. Grow. From Running Projects to Growing Portfolios with Umbraco Cloud.

Mon, 22 Jun 2026 10:28:07 Z

Andy Butland, Our Roadmap, Your CMS Umbraco 17 Released and What We're Building Next

Mon, 22 Jun 2026 08:57:50 Z

"We Need to Go Deeper: Extending Umbraco's Extensions" Codegarden workshop now available as an escape room

Mon, 22 Jun 2026 07:48:45 Z

🔧 We turned our Codegarden workshop into an escape room.Ronald Barendse, Nathan Woulfe and I ran "We Need to Go Deeper: Extending Umbraco's Extensions", four hours of coding quests across Engage, Workflow and Deploy, each one unlocking a fragment of a bigger puzzle.And here's the thing... you can play it too! The whole workshop is public, so clone the repo and work through the quests at your own pace. 👇https://cornehoskam.com/posts/extending-umbracos-extensions-a-codegarden-workshop-you-can-try-yourself/#umbraco #codegarden #dotnet #extensions

Codegarden 2026: Ubuntu

Mon, 22 Jun 2026 06:44:08 Z

It's Coffee Time!

Mon, 22 Jun 2026 00:00:00 Z

Extending Umbraco's Extensions: A Codegarden Workshop You Can Try Yourself

Mon, 22 Jun 2026 00:00:00 Z

uProfile June 2026 - Ben Szymanski

Mon, 22 Jun 2026 00:00:00 Z

From restoring vintage Macs to catching waves and building backoffice magic - meet 2026 Umbraco MVP Ben Szymanski.

It's Coffee Time!

Mon, 22 Jun 2026 00:00:00 Z

kontainer.umbraco

Mon, 22 Jun 2026 00:00:00 Z

Adds a media picker to pick media items from a Kontainer repository

It's Coffee Time!

Mon, 22 Jun 2026 00:00:00 Z

Lait.Umbraco.Analytics.Plausible

Sat, 20 Jun 2026 00:00:00 Z

Surfaces Plausible Analytics tracking data inside the Umbraco backoffice: a Content dashboard and a per-page block on each document's Info tab.

Lait.Umbraco.UI.ScrollToField

Sat, 20 Jun 2026 00:00:00 Z

A table of contents navigation helper for the Umbraco backoffice. Adds a dockable outline panel to the document editor that lists the page's tabs, property groups and Block List / Block Grid items — so editors keep their overview and can jump straight to any section on long content pages. Click an entry to scroll it into view and highlight it.

FrontendSupport.PartialTextString

Sat, 20 Jun 2026 00:00:00 Z

Basically a TextString, but you can specify prefix and/or postfix strings to show, which can make it much easier to understand exactly what's supposed to go into the field.

What Codegarden Inspired Me to Build Next

Fri, 19 Jun 2026 13:39:21 Z

Spin up Umbraco websites quickly with Umbeasy

Fri, 19 Jun 2026 04:51:47 Z

Need to spin up an #Umbraco website for a quick test of something?Try the friction-free #Umbreasy ⚡🏃‍♂️‍➡️It's in beta right now: https://umbreasy.com

Esatto.Umbraco.Backoffice.Redirects

Fri, 19 Jun 2026 00:00:00 Z

Dead-URL → new-URL redirects for Umbraco 17. Provides a SQL-backed Redirects table, a Settings-section dashboard for editors to manage 301 rules, and an IContentFinder that resolves redirects at request time. A single flat list of redirects: exact case-insensitive matching with query-string preservation, draft rows, and idempotent migrations.

Copenhagen, Codegarden, and My First Year as an Umbraco MVP

Thu, 18 Jun 2026 17:53:16 Z

Codegarden Aftermovie 2026

Thu, 18 Jun 2026 10:39:22 Z

🐰 The Rabbit faced traffic jams, train delays, and several moments of “you’ve got to be kidding me” on the way to Codegarden. Then: Codegarden. 🍿 Hit play to see how quickly travel stress turned into community vibes, new friendships, and a reminder that Codegarden isn’t just an event. It’s a family reunion that keeps growing 🫶 And before your grandma out-plans you and claims that prime summer weekend for her 90th birthday, lock your calendar for 2027: 👵🥊 📍 Øksnehallen, Copenhagen 🏰 📅 June 9–10, 2027 🦆🇩🇰

Codegarden 2026 recap

Thu, 18 Jun 2026 00:00:00 Z

Codegarden 2026 recap

Thu, 18 Jun 2026 00:00:00 Z

Lait.Umbraco.Search.Typesense

Thu, 18 Jun 2026 00:00:00 Z

An extension for Umbraco CMS providing a custom search engine integration with Typesense.

OC.Automate.Bluesky

Thu, 18 Jun 2026 00:00:00 Z

Bluesky connection type and action for Umbraco Automate. Post to Bluesky as part of an automation workflow.

Codegarden 2026 recap

Thu, 18 Jun 2026 00:00:00 Z

Codegarden 26 : a review

Wed, 17 Jun 2026 17:42:48 Z

Photo by Lukas Rychvalsky on Unsplash

Continue reading on Medium »

My Codegarden 2026 Highlights

Wed, 17 Jun 2026 12:51:39 Z

Umbraco Package: Automate Inspector

Wed, 17 Jun 2026 07:00:00 Z

Explore everything Umbraco Automate has to offer with this new community package!

Umbraco.Community.YouTubePicker

Wed, 17 Jun 2026 00:00:00 Z

Custom Umbraco datatype to enable editors to pick YouTube videos or playlists from a specific YouTube channel. You'll need a Google account and signup for an API key before you can use it.

My Codegarden 2026 Experience

Tue, 16 Jun 2026 02:57:14 Z

My Codegarden 2026 experience: keynotes, talks, awards, and the moments that reminded me why this community matters. Nine years, still getting goosebumps.

Esatto.Umbraco.Backoffice.ContentTreeDragAndDrop

Tue, 16 Jun 2026 00:00:00 Z

Native HTML5 drag-and-drop for the Umbraco 17 backoffice Content tree. Adds three-zone (above / into / below) drop targets per row with optimistic same-parent reorder and full cross-parent move support. Pure App_Plugins package — no C# code.

umContentGenerator

Tue, 16 Jun 2026 00:00:00 Z

AI-powered content generation for Umbraco: create fully-populated Block Grid and Block List pages — text and images — base on template page and short promt, powered by OpenAI.

Codegarden 2026: I went to Copenhagen for a week

Tue, 16 Jun 2026 00:00:00 Z

My 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 reading

TipTap is not broken. Your expectations are.

Mon, 15 Jun 2026 12:47:24 Z

Since 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 <p> tag inside a <li>
The inability to add certain tags to TipTap, like <script> 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 <p> inside <li> 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.

How I Hacked the Sticker Printers at Codegarden 2026

Mon, 15 Jun 2026 10:29:21 Z

Discover how constraints sparked innovation at Codegarden 2026. I bypassed printer limitations using only my phone and creative problem-solving techniques.

Codegarden 2026: A Week in Copenhagen I Won't Forget

Mon, 15 Jun 2026 10:19:36 Z

Just back from @umbraco.com Codegarden in Copenhagen, and what a week! 🎉 I was awarded Umbraco MVP 2026, did a demo in the keynote, and won the AI Package Award too. Still feels surreal. 🏆 Read more in the blog post. www.nevitech.co.uk/blog/codegar... #Umbraco #Codegarden

New release for umbPublisher 1.5.1

Mon, 15 Jun 2026 08:43:36 Z

New release for umbPublisher 1.5.1Tags that are set in #obsidian can now be mapped to #umbraco property editor. Available on https://community.obsidian.md/plugins/umbpublisher

I attended Umbraco Codegarden 2026!

Mon, 15 Jun 2026 07:00:00 Z

Codegarden 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!

OC.Automate.Mastodon released

Mon, 15 Jun 2026 00:00:00 Z

Esatto.Umbraco.Backoffice.SharedPreviewLink

Mon, 15 Jun 2026 00:00:00 Z

Shareable preview links for Umbraco 17. Editors mint a tokenized URL via a workspace-action button; recipients open the URL externally and see the current draft (no backoffice login). Tokens are 7-day data-protected; recipient cookie scopes preview to the specific page for 5 minutes.

OC.Automate.Mastodon released

Mon, 15 Jun 2026 00:00:00 Z

OC.Automate.Mastodon

Mon, 15 Jun 2026 00:00:00 Z

Mastodon connection type and action for Umbraco Automate. Post statuses to any Mastodon instance as part of an automation workflow.

OC.Automate.Mastodon released

Mon, 15 Jun 2026 00:00:00 Z

Across the Himalayas and Into the Heart of Umbraco

Mon, 15 Jun 2026 00:00:00 Z

Meet Rashmita and Jasper, the founders of One Tech Nepal. Discover how they use their 100% Umbraco agency to fund IT education and libraries in remote Himalayan schools.

Introducing Larsingerlogue CV-5000

Sun, 14 Jun 2026 21:24:09 Z

Or how I gave Behringer FCV100 the reference power supply it deserves to use for CV-modulation with Korg Minilogue XD

If you're here to solve the problem and don't care for a story, keep scrolling, you'll get to schematics, breadboard pictures and an ingredient list.

There's also a short video montage for the even more impatient.

This is quite a different post than I usually make, if I'm allowed to call it usually anymore at all. In any case, I've been playing the keys in a band for a couple of years and have yearned for a proper synth to supplement my (6) master keyboards. Recently I acquired my first ever analogue synthesizer. It only took 40 years for the dream to come through. I found a 15% cheaper second hand "unused" Korg Minilogue XD. But I only had damper pedals to use with it. Half the fun of synthesizers for me is varying the low pass filter cutoff. It's what gives that cool swiping, buzzing or muffled sound depending on how you "turn" it. For that I needed another type of pedal, and not just a regular one.

The Minilogue has a ton of hand-controlled potentiometer knobs we can use for a multitude of parameters, amongst others the filter cutoff. However it does not have a regular 1/4" jack slot for expression pedals like keyboards usually have. It has a damper slot, but only for CC64 on/off (sustain on and off). What we want is a full, preferably analogue, range from 0 to 100%. Expression pedals are excellent for this since they're basically pot meters you turn with your foot.

What the Minilogue comes with are two 1/8" jack "CV in" ports. So I browsed the interwebz for "CV pedal" and found a bunch of alternatives. Since I'm eyeing a Behringer Poly D come fall I thought the Behringer FCV100 V2 pedal seemed a good deal. It's advertised as a volume pedal with a CV option, including reversing polarity. So I ordered one and excitedly unpacked it while the band leader ran out to buy the last 1/8" to 1/8" cable and a 1/8" to 1/4" adapter. I'd dutifully inserted a 9V battery and optimistically hooked everything up...

Nothing!

I tried both CV inputs, both polarities, tons of options on the minilogue, but still nothing.
When I got home - I plugged a 1/8" into the input port which according to the interwebs should "power it on". Still nothing from the CV output. And yes, I had measured the voltage on the 9V battery.

Note: I have had no ambition doing electronics "right" with this project, nor writing a proper tutorial with a "right" way of doing it. This is a story about fiddling around and getting things to work. It is not a tutorial in proper electronics, in fact almost the opposite. I have not bothered to look up facts or calculated things. This means people who know their way around electronics might find this article revolting. I'm sorry. It was a way for me to brush up on how things work and get something working quickly. DIY by fiddling around until it works. Again, sorry, but hopefully other learners might be inspired to both fiddle around and learn to do the calculations. There's even a gem of an insight in the end that only hit me while writing this post. 😇

The research

According to the interwebz, someone claimed to have gotten CV output when they had plugged an unconnected 1/8" jack into input 2, but showed no proof or measurements. The next answer was someone who had done some due dilligence and measured the output. Apparently it only works with instruments that feed a reference voltage from its control voltage (CV) input in order for the pedal to vary it.

So I dug out my trusty old multimeter and started the process of dusting off the parts of my brain still remembering reading "There are no Electrons: Electronics for Earthlings" ten plus years ago. I learned about what tip, ring and sleeve (TRS) for jack plugs are, and all the other variants. Measuring DC between the tip and sleeve of the unconnected side of the cable when pressing the pedal did absolutely nothing. Measuring resistance though showed a varying impedance of 0 through 50kΩ. If I flipped between TRS and RTS mode on the pedal it seemingly reversed the resistance on the ring, but the tip stayed fixed on 50kΩ in TRS mode. In any case, after some brain clearing with ChatGPT, I could conclude that the pedal in CV mode is only a 50kΩ potmeter and does not provide any of the sweet power from the (now useless) 9V battery I had inserted.

Note: I've left the pedal in RTS mode. In order to use both and reverse polarity there's more research and a V2 to be built. See closer to the end for a short rant about the factory presets in Minilogue XD.

I figured there has to be a way to provide that power even if the synth doesn't. So after a little more chatting with ChatGPT I figured I could dig through all my old cables and adapters to find an USB cable and adapter we're not using. I should be able to "inject" it's 5V DC voltage into the jack cable instead of relying on the synth to provide it. I dug through all my treasure drawers and found an USB mini-B 4-pin (?) to USB A cable and cut off the mini-B plug to reveal the two VCC/GND cables and two data cables. I found a couple of horribly old AC USB adapters and measured the DC from both via the cable's red (VCC) and black (GND) wires. One gave 3.3V and the other gave 5V. I happily threw the overdue 3.3V one in the "to recycling" bin and rubbed my hands together over the other. (Throwing out one old device should score me at least one plus in the wife's accounting system.)

Specifications

Of course it's prudent to actually check the specs of the hardware you're trying to shove a current into. So I dug up the details in the manuals, which to be honest are both quite a tad more than averagely vague about how to connect control voltage hardware.

The Minilogue XD manual has the following gem of a CV mention:

CV IN 1 and 2 jacks (3.5 mm monaural mini-phone jack; input voltage: –5V to 5V in modulation mode, –3V to 5V in CV/gate mode)

So I figured I'm safe proceeding with my 0-5V endeavour. We are going to use it for modulation.

The FCV100 manual has a similarly brief description of it's "CV" output:

1/4" TS - unbalanced Tip: Supply volt. from unit/instr. to be controlled: Impedance: 50kOhm Ring: Slider pick-up (CV dependend on ped. position, impedance: 0-50kOhm)

There's some more specs around 2V and output impedance, but as far as I've understood that's all about the volume control feature of the pedal. I have a hard time interpreting whether that sentence says "bring your own power" or "we'll use the battery you inserted".

Having this information and some support from the [un]trusty LLM though, I pressed on to simulating the imagined setup.

Tinkering

Tinkercad is an awesome tool for budding DYIers wanting to learn or experiment with electronics. Especially if starting to experiment with arduinos or other consumer grade microcontrollers. I could safely experiment with placement of the resistors and different resistance values and until I got the desired voltage output on the simulator's multimeter.

In place of the pedal I added a regular pot meter. It has three pins which is basically a 1:1 representation of the tip, ring and sleeve on a jack plug. The middle pin is the "wiper", which I'd measured on the pedal to output a varying resistance between the ring and sleeve on the opposite end of the jack cable.
Back and forth with GPT and the multimeter for a while made me understand that the CV input on the Minilogue likely has an internal 1MΩ or larger resistor, just like a multimeter has. That's how it's able to read the voltage loss between the sides and thereby also receive the varying "control voltage" input from the pedal.

Tinkercad also sports a USB connector and all the resistors you can dream of. And that's the whole recipe for this "CV adapter". It took some time to remember my URIs (Ohm's law) and how things affect the dance of the electrons (or little green men if you prefer). To be honest I still don't really know, but fiddling and discussing with GPT got me to something that works with a fair understanding. Mr. GPT had suggested a 50 kΩ resistor between the pedal and synth, but the simulations led me to choose a 10 kΩ. Again, the learned and/or dilligent would bother to calculate why.

The ingredients for the simulation ended up as follows:

Name	Value	Description
USB Standard A	-	USB connector. It gives 5V in the simulator as expected.
Resistor A	150 Ω (several tries)	A resistor to limit the circuit current slightly from the USB output. Just to be precaucious.
Resistor B	10 kΩ	A resistor to protect and limit the current going into the synth. (We'd rather not blow it up...)
Fake CV in port	1 MΩ	A resistor representing the internal impedance of the synth's CV sensor and the tip (VCC) and sleeve (GND) of the jack plug.
Multimeter	-	A multimeter in resistance mode measuring the loss over the "fake CV in port" resistor.
Fake pedal	50 kΩ	A potentiometer representing the pedal and the tip (VCC), ring (CV out), and sleeve (GND) of the jack plug.

Here's the breadboard layout:

I'm extremely discontent with how Tinkercad figured to lay out the schematic, but in any case I suppose it is correct. Why couldn't the pot go straight to the 10k resistor? Oh well, here's it is in all it's jumbled glory:

Prototyping and building in real life

Having the simulation show thumbs up I figured I should try it in real life and do some measurements before hooking anything up to my brand new synth. For some reason Tinkercad shows a tiny explosion on the USB connector when the simulation starts, but my adapter stood the test and I suspect there might be a bug with the implementation on Tinkercad. 😇

I have both breadboards and a plethora of resistors lying around from my Arduino adventures last decade. Finding a breadboard and some resistors didn't bide much problem. They're all within arms length to my left. But this is where I started going back and forth between the breadboard and Tinkercad. Turns out real life didn't give the same measurements as the simulation. Even if I used a PSU of 5.5V instead of a USB connector. My adapter gives 5.5V, remember?

Here's a little montage of all the crocodiles holding things together.

After a while I had the right resistors to see 0-5V on the multimeter having hooked up the pedal to my shortest mangled jack-cable. I excitedly hooked up some crocodiles to the other half-jack and the breadboard, wearily shoved the plug into my synth and tried the pedal. Sucess! The LCD-display on the synth showed 0 to ... 97%??? So even if the simulator and my multimeter showed I output 5V from the pedal when 100% down the Minilogue expects more. Anyone knowledgeable with electronics will likely know why, but I merely suspect that it somehow "feels" the max input from the source is 5.5V. So it was out with the jack, out with the GND crocodile and in and out with misc initial resistors until I saw 0-100% CV input on the synth. A 150 Ω resistor turned out to be the sweet spot.

I now had proof I could build this "CV-adapter", so it was time for V1.

Assembling V1

Again from my Arduino-days I found a few circuit boards in my drawers. The smallest ones were 24x18 holes (7x3cm) - a little big. But incidentally I could spot in the corner of my eye something resembling an Arduino-case. The 7x3 board fits perfectly within, and it's a slim one just 1.5cm tall. Perfect!

On to the soldering. Not that I lacked any space, but it's always nice not having to cross wires. Enter a slightly unorthodox tool, my favorite program in the whole world: Excel. Who needs technical drawing software when you have colorable cells? I first drew up the layout on the left, but inspecting the casing I'd found I figured I'd rather flip it around. So I ended up going for the layout on the right.

I'm extremely shaky, so soldering took its time. It's somewhat of a Zen excercise I've never quite mastered. I also realized way too late (of course) that I'd been better off stretching a few more wires, but hey - it's 10 years since last time I did anything like this.

In any case, the first test with the multimeter and pedal showed a semi-constant 5.4V so I had to go back to the soldering board. A few connection tests with the trusty meter showed a lacking connection to ground from the pedal. Even with my new "computer glasses" and a magnifyer on my little helper I couldn't see that the amputated resistor leg I'd connected to ground wasn't connected. But I could find the spot where the connection ended, so I added kind of a highway of tin all the way. Success!

Here's how the circuitboard ended up.

The final stretch was to have the board rest well within the box. I was lucky to find some double sided tape in the kitchen, and since one side of the board already rested slighly on the USB and jack cables I chuckled as I cut off another 2.5cm piece of the now 4cm long USB mini cord. It fit perfectly. Tape on the case, tape on the board, and a short piece of USB mini cord as a pillow.

Here's the final box.

Final fun

Of course my box needed a name and a logo. It didn't take many brain-iterations until I landed on Larsingerlogue CV-5000. It's my [Behr]inger [FCV100 to Mini]logue[ XD] CV-5[V * 1]000[mA adapter]. I turned to my age old friend "Impact" and quickly found a fitting gradient in Photoshop.

Video montage

I'd also shot a couple of videos and pictures during the process, so I amused myself by throwing together a short video of the whole process. It features the first built in patch of Minilogue XD and it's sample sequence with me "playing" the filter cutoff on the now functioning pedal, and the "riser" delay time and depth using my free hand. Farily cool. And then a quite off-beat attempt at the Stranger Things theme as an RL demo of the final product. Check it out.

I hope you've anjoyed following my little story of dipping my toes in electronics for music. There's high potential for a V2 with better polarity support, and who knows what other ideas one might come up with for 100% "DIY" effects to shove into those CV inputs. There's still one unused. 😁

Grief

My only grief, and that's kind of connected to the single polarity of my adapter, is that all of the built-in patches in the Minilogue XD are set to having CV 1 modulating the shape of VCO 1 from 0 to 100%, and CV 2 is set to filter cutoff from 0 to -100%. That means I open the filter by "closing" the pedal and close the filter by "opening" the pedal. Pedal to the floor means almost no audible sound.

Learning while blogging

In hindsight I think I just realized with writing this that 5V on the multimeter means (almost) no power moves through the resistor, which is measured as 0V - while I've been reading 5V (loss) on the multimeter. That would explain the "weird" direction of the pot meter in the simulation that'd been bugging me. 🤣

But hey - adds to a fun story about learning and just jumping into the water.

If you got this far I hope you had a chuckle, nodded or otherwise found this interesting.
Thanks a lot for reading, and have fun whatever endeavor led you to this post.

Esatto.Umbraco.Backoffice.DictionaryFilterValues

Sat, 13 Jun 2026 00:00:00 Z

Extends the Umbraco 17 backoffice Dictionary section filter to also match translation VALUES, not just dictionary-item names. Useful for editors who remember a translated string but not the dictionary key. Adds one authenticated Management API endpoint and a backoffice entry point that re-points the built-in Dictionary collection's data source at it — no window.fetch patching, no anonymous endpoints.

Esatto.Umbraco.Backoffice.CustomEditors

Sat, 13 Jun 2026 00:00:00 Z

A library of reusable property editor UIs for the Umbraco backoffice. Ships an Encrypted Textbox editor (encrypts sensitive values at rest via ASP.NET Core Data Protection, masked on screen) and a Date Range editor (two inline calendars with start/end constraint, optional time and min/max bounds).

umbraCoffee - LIVE at #Codegarden 2026!

Thu, 11 Jun 2026 10:52:11 Z

IM.Umbraco.AI.Local

Thu, 11 Jun 2026 00:00:00 Z

Local LLM provider for Umbraco AI. Connects the Umbraco backoffice AI features (prompts, agents, Copilot, embeddings) to any OpenAI-compatible self-hosted server such as Ollama, LM Studio or vLLM — no cloud account required.

RipplePreview

Thu, 11 Jun 2026 00:00:00 Z

See your actual pages while you edit them. Blocks render through your site's own views, styles and scripts — sections render whole with their children, carousels and animations run, and everything stays editable: hover to highlight a block inside the preview and click to open it.

Umbraco.Community.AiAgentMemory

Thu, 11 Jun 2026 00:00:00 Z

AI Agent Memory for Umbraco — persistent memory + learning layer for Umbraco's AI agent stack. Editors give thumbs-up / thumbs-down feedback on agent runs via the AI Agent Feedback widget; the package indexes that feedback as searchable memory and injects it into subsequent runs so agents suppress false positives and reuse validated patterns. Composes on Umbraco.AI 1.8+ (vector store via Umbraco.AI.Search). Memory is off by default; per-agent opt-in via appsettings.json. Built for Umbraco v17+.

The Umbraco MVPs 2026

Wed, 10 Jun 2026 00:00:00 Z

Meet our Umbraco MVPs for 2026. These are our Most Valuable People, people who have a passion for contributing to Umbraco and the Umbraco Community.

BT.RedirectManager

Wed, 10 Jun 2026 00:00:00 Z

Modern URL redirect manager for Umbraco 13 and 17. Manage 301, 302, 404, and 410 redirects from a clean backoffice dashboard with regex support, CSV import/export, and a built‑in test tool.

Umbraco Awards Winners 2026 🏆

Wed, 10 Jun 2026 00:00:00 Z

Umbraco Awards 2026 winners are announced! Discover the outstanding projects and celebrate the amazing work within the Umbraco ecosystem.

Esatto.Umbraco.Backoffice.ContentTreeDnd

Wed, 10 Jun 2026 00:00:00 Z

Umbraco.Deploy.Automate

Wed, 10 Jun 2026 00:00:00 Z

Umbraco Deploy support for Umbraco Automate (artifacts, service connectors, triggers and actions).

Umbraco Product Update/Codegarden Keynote Highlights, Q2 2026

Wed, 10 Jun 2026 00:00:00 Z

Missed the Codegarden 2026 Keynote? Catch up on Umbraco's Q2 product updates, including Umbraco Automate (new product!), CMS Elements, and Load Balancing for Cloud.

Umbraco.Automate

Wed, 10 Jun 2026 00:00:00 Z

Umbraco Automate

Flowcourier.Umbraco.CookieConsent

Wed, 10 Jun 2026 00:00:00 Z

A comprehensive cookie consent solution for Umbraco CMS with Google Consent Mode v2 support, customizable categories, and statistics tracking.

Umbraco.Forms.Automate

Wed, 10 Jun 2026 00:00:00 Z

Umbraco Forms triggers and actions for Umbraco Automate

Crumpled.Nostalgid

Wed, 10 Jun 2026 00:00:00 Z

...

Umbraco.AI.Search

Wed, 10 Jun 2026 00:00:00 Z

AI-powered vector search provider for Umbraco CMS

Umbraco.Engage.Automate

Wed, 10 Jun 2026 00:00:00 Z

Umbraco Engage triggers and actions for Umbraco Automate

Umbraco.Workflow.Automate

Wed, 10 Jun 2026 00:00:00 Z

Umbraco Workflow triggers for Umbraco Automate

Umbraco.Commerce.Automate

Wed, 10 Jun 2026 00:00:00 Z

Umbraco Commerce triggers and actions for Umbraco Automate

Umbraco.AI.Automate

Wed, 10 Jun 2026 00:00:00 Z

Umbraco Automate integration for Umbraco.AI.Agent

How to add Giscus Comments to an Umbraco Site

Mon, 08 Jun 2026 01:18:50 Z

Add Giscus comments to your Umbraco site with GitHub Discussions. Free, open-source comment system with no backend, privacy-friendly, and developer-native.

Umbraco.Cms.Search.Core

Mon, 08 Jun 2026 00:00:00 Z

Umbraco Search provides an abstraction for search services in Umbraco, allowing for implementations using search providers such as Examine.

CodeGarden-talk: Hybrid Cache changes everything

Sun, 07 Jun 2026 05:31:32 Z

I 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 slides link common soon]

Knowit.Umbraco.TranslationManager

Fri, 05 Jun 2026 00:00:00 Z

Backoffice dashboard for auditing Umbraco translation dictionary keys against actual code usage. Surfaces unused keys, missing translations, and language coverage gaps across Razor, React, Vue, or any custom pattern. Includes a setup wizard, multi-source scanning, and bulk dictionary management.

Knowit.Umbraco.SvgPicker

Fri, 05 Jun 2026 00:00:00 Z

Property editor for Umbraco 17 that adds a visual SVG icon picker to the backoffice. Editors browse and search symbols from any configured SVG spritesheet. Stores the symbol ID as a plain string and renders as svg/use in Razor via a built-in Html.SvgIcon() helper.

Codegarden: What to bring (2026 edition!)

Thu, 04 Jun 2026 10:14:30 Z

Wow, 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...

Why 2026 Is the Year to Finally Attend Codegarden

Thu, 04 Jun 2026 07:55:39 Z

Why 2026 Is the Year to Finally Attend Codegarden | DynamicDave

Umbraco.AI Security Advisory, June 4, 2026

Thu, 04 Jun 2026 00:00:00 Z

Security patches are available for Umbraco.AI core package, versions 1.0.0 through 1.13.x versions fix a moderate vulnerability. Find the fix here

All uSkinned Starter Kit and Themes Add-ons Out for Umbraco 17

Wed, 03 Jun 2026 09:42:08 Z

All Starter Kit and Themes Add-ons Out for Umbraco 17 Every uSkinned Starter Kit and Theme add-on is now ready for Umbraco 17 and uSkinned Site Builder 7.

Umbraco OpenID Connect example with lightweight external members (Updated)

Wed, 03 Jun 2026 05:26:52 Z

I updated the @umbraco OpenID Connect example to Umbraco 17.4.2 and added support for lightweight external members.Enabling it comes down to one flag: ExternalOnly = true. But there is one gotcha the docs don't cover. Existing content-based members are not migrated automatically. If you want them to become lightweight external members, you need to delete them first and let Umbraco recreate them on the next login.Full details in the blog post below.https://www.jeroenbreuer.nl/blog/umbraco-openid-connect-example-with-lightweight-external-members/#Umbraco

SplatDev.Umbraco.Plugins.MemberTypes

Wed, 03 Jun 2026 00:00:00 Z

Umbraco Member Type management plugin: create/edit custom member types with profile fields, custom properties and type templates. Supports Umbraco 13 (net8.0) and Umbraco 17 (net10.0).

SplatDev.Umbraco.Plugins.MemberLogin

Wed, 03 Jun 2026 00:00:00 Z

Custom member login for Umbraco: login form, remember me, forgot password, lockout handling. Supports Umbraco 13 (net8.0) and Umbraco 17 (net10.0).

SplatDev.Umbraco.Plugins.SocialMedia.Share

Wed, 03 Jun 2026 00:00:00 Z

Umbraco social sharing buttons plugin — configurable platforms and share links. Supports Umbraco 13 (net8.0) and Umbraco 17 (net10.0)

SplatDev.Umbraco.Plugins.Tweets

Wed, 03 Jun 2026 00:00:00 Z

Twitter/X feed display plugin for Umbraco 13 (net8.0) and Umbraco 17 (net10.0). Caches tweets locally and refreshes on a configurable schedule.

SplatDev.Umbraco.Plugins.VisitorCounter

Wed, 03 Jun 2026 00:00:00 Z

Umbraco visitor counter plugin: tracks unique and total site visitors, provides daily counts and a display widget. Supports Umbraco 13 (net8.0) and Umbraco 17 (net10.0).

SplatDev.Umbraco.Plugins.RdpManager

Wed, 03 Jun 2026 00:00:00 Z

Umbraco Remote Desktop connection manager plugin — store RDP configs and generate .rdp file downloads. Supports Umbraco 13 (net8.0) and Umbraco 17 (net10.0)

SplatDev.Umbraco.Plugins.Countries

Wed, 03 Jun 2026 00:00:00 Z

Umbraco countries data plugin supporting Umbraco 13 (net8.0) and Umbraco 17 (net10.0)

BlendInteractive.Umbraco.SecurityDashboard

Wed, 03 Jun 2026 00:00:00 Z

The Umbraco Security Dashboard is a package that provides a dashboard within the Umbraco backoffice to help identify potential security vulnerabilities in installed packages. It scans installed packages against known vulnerabilities and can report vulnerabilities to a central location via webhook.

SplatDev.Umbraco.Plugins.IspServices

Wed, 03 Jun 2026 00:00:00 Z

Umbraco ISP/IP services utilities plugin supporting Umbraco 13 (net8.0) and Umbraco 17 (net10.0)

SplatDev.Umbraco.Plugins.NewsTicker

Wed, 03 Jun 2026 00:00:00 Z

Scrolling news ticker plugin for Umbraco 13 (net8.0) and Umbraco 17 (net10.0). Configurable items, speed, and direction stored in the database.

SplatDev.Umbraco.Plugins.ExceptionManager

Wed, 03 Jun 2026 00:00:00 Z

Umbraco exception handling middleware plugin supporting Umbraco 13 (net8.0) and Umbraco 17 (net10.0)

SplatDev.Umbraco.Plugins.Newsletters

Wed, 03 Jun 2026 00:00:00 Z

Newsletter subscriber management, campaigns, and send tracking for Umbraco 13 (net8.0) and Umbraco 17 (net10.0).

SplatDev.Umbraco.Plugins.Rsvp

Wed, 03 Jun 2026 00:00:00 Z

Umbraco RSVP event registration plugin with attendee management, capacity limits, waitlisting, and cancellation support. Supports Umbraco 13 (net8.0) and Umbraco 17 (net10.0).

SplatDev.Umbraco.Plugins.ExamineExtensions

Wed, 03 Jun 2026 00:00:00 Z

Examine search extensions for Umbraco — additional query helpers, result transformers, and index utilities.

SplatDev.Umbraco.Plugins.CustomLogin

Wed, 03 Jun 2026 00:00:00 Z

Umbraco custom login page plugin with branding support, SSO integration hooks and 2FA readiness. Supports Umbraco 13 (net8.0) and Umbraco 17 (net10.0).

SplatDev.Umbraco.Plugins.SEO

Wed, 03 Jun 2026 00:00:00 Z

Umbraco SEO plugin supporting Umbraco 13 (net8.0) and Umbraco 17 (net10.0)

SplatDev.Umbraco.Plugins.Slider

Wed, 03 Jun 2026 00:00:00 Z

Image slider plugin for Umbraco — stores slide data with EF Core, renders via configurable view component.

SplatDev.Umbraco.Plugins.Surveys

Wed, 03 Jun 2026 00:00:00 Z

Umbraco survey builder plugin with questions, multiple choice, free text, rating, and results dashboard. Supports Umbraco 13 (net8.0) and Umbraco 17 (net10.0).

SplatDev.Umbraco.Plugins.WordsApi

Wed, 03 Jun 2026 00:00:00 Z

Umbraco Words API plugin supporting Umbraco 13 (net8.0) and Umbraco 17 (net10.0)

SplatDev.Umbraco.Markup

Wed, 03 Jun 2026 00:00:00 Z

HTML/markup helpers and extensions for Umbraco 13 (net8.0) and Umbraco 17 (net10.0)

SplatDev.Umbraco.Plugins.CharLimit

Wed, 03 Jun 2026 00:00:00 Z

Character limit property editor for Umbraco — enforces max length on text properties with live counter display.

SplatDev.Umbraco.Plugins.PasswordSettings

Tue, 02 Jun 2026 00:00:00 Z

Umbraco Password Settings plugin: complexity rules, expiration, history (prevent reuse), strength meter. Supports Umbraco 13 (net8.0) and Umbraco 17 (net10.0).

SplatDev.Umbraco.Plugins.Restricted

Tue, 02 Jun 2026 00:00:00 Z

Umbraco Restricted Content plugin: member-only content gates, role-based access and paywall support using IPublicAccessService. Supports Umbraco 13 (net8.0) and Umbraco 17 (net10.0).

Speed up slow deployments to Umbraco Cloud

Tue, 02 Jun 2026 00:00:00 Z

SplatDev.Umbraco.Plugins.EmailNotifications

Tue, 02 Jun 2026 00:00:00 Z

Email template engine, Mailgun mail provider, newsletter campaigns, and member notifications for Umbraco 13 (net8.0) and Umbraco 17 (net10.0).

uSkinnedSiteBuilder.StarterKit.TheFoundry

Tue, 02 Jun 2026 00:00:00 Z

The Foundry Starter Kit for uSkinned Site Builder for Umbraco CMS

Speed up slow deployments to Umbraco Cloud

Tue, 02 Jun 2026 00:00:00 Z

SplatDev.Umbraco.Plugins.Payments.MercadoPago

Tue, 02 Jun 2026 00:00:00 Z

MercadoPago payment integration for Umbraco. Supports preference creation, payment status lookup, and webhook handling. Supports Umbraco 13 (net8.0) and Umbraco 17 (net10.0).

SplatDev.Umbraco.Plugins.D4Sign

Tue, 02 Jun 2026 00:00:00 Z

D4Sign digital signature integration for Umbraco. Supports document upload, signer management, webhook processing, and a Lit 3 backoffice dashboard. Supports Umbraco 13 (net8.0) and Umbraco 17 (net10.0).

SplatDev.Umbraco.Plugins.LiveVideo

Tue, 02 Jun 2026 00:00:00 Z

Live video embed for Umbraco — YouTube Live, Twitch, and Vimeo live stream integration. Supports Umbraco 13 (net8.0) and Umbraco 17 (net10.0).

SplatDev.Umbraco.Plugins.VideoPreview

Tue, 02 Jun 2026 00:00:00 Z

Video thumbnail preview for Umbraco — auto-generate thumbnail URLs from YouTube, Vimeo, and Dailymotion video URLs. Supports Umbraco 13 (net8.0) and Umbraco 17 (net10.0).

SplatDev.Umbraco.Plugins.AdminBar

Tue, 02 Jun 2026 00:00:00 Z

Fixed admin bar injected at the top of the page for logged-in backoffice users. Provides Edit Page, Preview and Publish shortcuts. Supports Umbraco 13 (net8.0) and Umbraco 17 (net10.0).

SplatDev.Umbraco.Plugins.Newsletter

Tue, 02 Jun 2026 00:00:00 Z

Newsletter subscriber lists, campaigns, Mailgun bulk send, and stats tracking for Umbraco 17 (net10.0). Depends on SplatDev.Umbraco.Plugins.EmailTemplates for rendering.

SplatDev.Umbraco.Plugins.Payments.PagSeguro

Tue, 02 Jun 2026 00:00:00 Z

PagSeguro payment integration for Umbraco. Supports checkout session creation, transaction status lookup. Supports Umbraco 13 (net8.0) and Umbraco 17 (net10.0).

SplatDev.Umbraco.Plugins.Gdrp

Tue, 02 Jun 2026 00:00:00 Z

GDPR compliance plugin for Umbraco — cookie consent banner, data export, and right to erasure requests. Supports Umbraco 13 (net8.0) and Umbraco 17 (net10.0).

Speed up slow deployments to Umbraco Cloud

Tue, 02 Jun 2026 00:00:00 Z

SplatDev.Umbraco.Plugins.ENotAssina

Tue, 02 Jun 2026 00:00:00 Z

e-Not Assina electronic signature integration for Umbraco. Supports document creation, sequential signing, webhook processing, PDF download, and a Lit 3 backoffice dashboard. Supports Umbraco 13 (net8.0) and Umbraco 17 (net10.0).

SplatDev.Umbraco.Plugins.Payments.BancoInter

Tue, 02 Jun 2026 00:00:00 Z

Banco Inter payment integration for Umbraco. Supports Pix (immediate and due charges), Boleto com Pix, Banking (outbound Pix, boleto payments, balance/statement), and webhook handling. Supports Umbraco 13 (net8.0) and Umbraco 17 (net10.0).

SplatDev.Umbraco.Plugins.DictionaryManager

Tue, 02 Jun 2026 00:00:00 Z

Dictionary import/export/CRUD manager for Umbraco — full rewrite of the Umbraco 8 plugin using ILocalizationService. Supports Umbraco 13 (net8.0) and Umbraco 17 (net10.0).

Skrift Issue #128

Tue, 02 Jun 2026 00:00:00 Z

Featuring guest posts by Pasang Tamang on "From Umbraco 8 to Umbraco 17 in One Leap: uSync, Cursor, and the Umbraco MCP" and Aaron Sawyer on "Using Local LLMs wth Umbraco MCP"

SplatDev.Umbraco.Plugins.HiddenContent

Tue, 02 Jun 2026 00:00:00 Z

Umbraco Hidden Content plugin: hide nodes from navigation and sitemaps while keeping them accessible by URL via the umbracoNaviHide property. Supports Umbraco 13 (net8.0) and Umbraco 17 (net10.0).

SplatDev.Umbraco.Plugins.Mailer

Tue, 02 Jun 2026 00:00:00 Z

Umbraco mailer plugin supporting Umbraco 13 (net8.0) and Umbraco 17 (net10.0)

In-memory Umbraco Search

Mon, 01 Jun 2026 00:00:00 Z

How to run Umbraco Search purely in-memory.

Fixing the sort order in Content Pickers in Umbraco

Mon, 01 Jun 2026 00:00:00 Z

Fixing the sort order in Content Pickers in Umbraco

Mon, 01 Jun 2026 00:00:00 Z

Fixing the sort order in Content Pickers in Umbraco

Mon, 01 Jun 2026 00:00:00 Z

FastGooey.UmbracoForms

Mon, 01 Jun 2026 00:00:00 Z

Render Umbraco Forms into native iOS, macOS and Flutter viewing surfaces directly from your Umbraco projects.

More Visibility, More Control. What's New in Umbraco Cloud

Mon, 01 Jun 2026 00:00:00 Z

Discover what’s new and coming next in Umbraco Cloud. Explore new features like performance insights, security updates, and dedicated scaling for agencies.

Umbraco.Community.AI.Reframe

Sat, 30 May 2026 00:00:00 Z

Reframe image media to a new aspect ratio without leaving the Umbraco backoffice. A Reframe view on every Image media item lets editors retarget a picture either by Crop (instant, free, geometric) or by AI Outpaint (OpenAI gpt-image-2 invents the new edges so no content is lost). Preview before/after, then Accept to save the result as a new media item — the original is never changed. Outpaint requires your own OpenAI API key and incurs OpenAI usage cost; Crop is free.

SSO in Umbraco 17: Azure AD Back Office Login with OpenID Connect

Fri, 29 May 2026 18:47:06 Z

A step-by-step guide to wiring up Azure Active Directory as an external login provider for the Umbraco back office — with auto-linking…

Continue reading on Medium »

umbraCoffee - Agents, Codegarden, Tees

Fri, 29 May 2026 09:02:18 Z

Welcome to your monthly dose of #umbraCoffee! Your hosts - Marcin and Callum - together with their guest(s) will drive through all of the community news and happenings in the Umbraco world. So... grab a cuppa, join us LIVE and enjoy! Today we're joined by Adam Shallcross, CEO & Founder of Cogworks – and curator oft the Human Vibe Loop newsletter. See ya?! --- ☕ Wanna buy us a coffee/pizza/donuts? https://www.buymeacoffee.com/umbracoffee --- Notes: // TODO

Contentment 7.0.0-alpha001 for Umbraco 18 RC out now

Fri, 29 May 2026 06:23:49 Z

#umbraco #Contentment 7.0.0-alpha001https://github.com/leekelleher/umbraco-contentment/releases/tag/7.0.0-alpha001TL;DR, want to try out Umbraco 18 with Contentment this weekend?Is it stable? Probably!Does it have bugs? Nah!How can you help? Test it out and feedback!

Umbraco Forums #h5yr now display on HFYR.com

Thu, 28 May 2026 13:00:42 Z

Pleased to announce that now, if you give a #h5yr on the Umbraco Forum, that post will be displayed on H5YR.com Thanks @sebastiaan for helping get this setup. #umbraco

UmbHost launches automated Umbraco upgrades

Thu, 28 May 2026 09:35:45 Z

Automated Umbraco upgrades, sorted. GitHub Dependabot handles the dependency PRs, GreenStack handles the deploy. Here's how you can do it 👇https://umbhost.net/blog/2026/05/building-your-own-umbraco-cloud-style-auto-upgrades-with-github-dependabot#Umbraco #dotnet #DevOps #GreenStack

Umbraco 18 Release Candidate

Thu, 28 May 2026 00:00:00 Z

Discover and test the Umbraco 18 Release Candidate, featuring Elements for reusable content, typed OpenAPI schemas,

How I let Cursor build an Azure Search provider for Umbraco Search

Wed, 27 May 2026 13:57:13 Z

Codegarden 2026 - not long now!

Wed, 27 May 2026 00:00:00 Z

Lantern.Umbraco

Wed, 27 May 2026 00:00:00 Z

Add the Lantern bug-tracking widget to every page of your Umbraco site in seconds. Configure your embed key from the backoffice — no template changes needed.

Codegarden 2026 - not long now!

Wed, 27 May 2026 00:00:00 Z

Codegarden 2026 - not long now!

Wed, 27 May 2026 00:00:00 Z

Umbraco vs WordPress

Tue, 26 May 2026 10:17:32 Z

Die Wahl des richtigen Web-Content-Management-Systems gleicht heute einer strategischen Richtungsentscheidung, die maßgeblichen Einfluss…

Continue reading on Medium »

Browsing Umbraco Logs in Kudu

Tue, 26 May 2026 06:09:21 Z

Browsing Umbraco Logs in Kudu | skttl.dev

uPreviewShare

Tue, 26 May 2026 00:00:00 Z

Securely share unpublished draft content with external stakeholders via time-limited, view-capped, and PIN-protected preview links. Renders through actual Umbraco templates.

Umbraco Search Explained | Kenn Jacobsen | Umbraco India Meetup

Thu, 21 May 2026 09:52:54 Z

Featuring Kenn Jacobsen Kenn is a 4x Umbraco MVP and a long-time contributor to the Umbraco community, with more than 10 years of experience building solutions with Umbraco and .NET. 📺 Watch the full session recording and learn what’s coming next for search in the Umbraco ecosystem. 🌍 Join us for upcoming Umbraco India User Group events and community updates. 🔗https://www.meetup.com/umbraco-india-user-group 🔗https://www.linkedin.com/groups/14558029

M1sterPl0w.Umbraco.AccessRestriction

Thu, 21 May 2026 00:00:00 Z

An Umbraco package that restricts access to your site (or specific paths) by IP address whitelist. Manage whitelisted IPs and restricted paths from a dashboard in the Umbraco backoffice, with optional hardcoded entries via appsettings.json.

UmbHost.Tables for Umbraco has had an update

Wed, 20 May 2026 10:56:20 Z

UmbHost.Tables for #Umbraco has had an update courtesy of Mike Masey!This replaces the custom RTE with the fully featured tiptap RTE with all the configuration options you would expect.View source now opens in a modal windowThere is also a range of accessibility and UX improvementsMany thanks and a huge #h5yr for this PR!Grab it here:https://www.nuget.org/packages/UmbHost.Tables/17.1.0

Start With Markdown

Wed, 20 May 2026 06:00:00 Z

Clean starter kit for Umbraco 18 out in Beta

Wed, 20 May 2026 06:00:00 Z

PragmaticIT.Umbraco.VirtualMembers

Wed, 20 May 2026 00:00:00 Z

Passwordless, database-free member authentication for Umbraco CMS. Protect content nodes with email-only, OTP, or MFA login — members loaded from plain CSV files, no Umbraco Members database records required.

UmbracoTees day May 29th

Tue, 19 May 2026 15:13:52 Z

Can you believe we haven't had an #UmbracoTees day this year yet? Well, let's change that!! Get your Umbraco Swag on, share your photos with #umbracoTees and let's see you all celebrate all things #umbraco May 29th 2026!https://isitumbracoteesday.today/

Start With Markdown

Tue, 19 May 2026 14:17:30 Z

Learn about my new open source content publishing workflow called Start With Markdown It's a simple workflow which triggers when you create or modify a markdown file in the posts folder of your github repo. When it triggers it calls some endpoints on your CMS to create the content and it returns the edit, preview and publish URLs for you. Here is the link to the main project that you fork and setup to call your CMS endpoints https://github.com/prjseal/Start-With-Markdown/ And here is the link to the demo Umbraco project and supporting libraries with the custom resolvers for unsplash and things like that to get it working with the Clean starter kit https://github.com/prjseal/Start-With-Markdown-Umbraco-Libraries

Umbraco 18 and OpenAPI: a heads-up for extension developers

Tue, 19 May 2026 13:37:37 Z

Time to upgrade your extension to Umbraco 18?
A friendly heads up, the OpenAPI generation got an overhaul.

Microsoft.AspNetCore.OpenApi is Umbraco's new library of choice for OpenAPI document generation, replacing Swashbuckle.AspNetCore. It ships with ASP.NET Core and is maintained by Microsoft alongside the framework, which means one fewer third-party dependency to worry about.

The trade-off: if your extension wired up its own OpenAPI document on v17, it won't compile against v18. The Swashbuckle types it relied on are gone.

Two paths forward:

Migrate to Microsoft OpenAPI. Two options:
- Use the AddBackOfficeOpenApiDocument extension method: Umbraco's new helper. What the v18 template uses. Covers most extensions.
- Use Microsoft's AddOpenApi method directly: call Microsoft.AspNetCore.OpenApi yourself. For full control.
Keep using Swashbuckle (not recommended). Install Swashbuckle.AspNetCore in your own extension, wire it up, then plug your document into Umbraco's Swagger UI via AddOpenApiDocumentToUi(...). When rewriting isn't an option right now.

ℹ️ Note: the OpenAPI spec URL also changed from /umbraco/swagger/{documentName}/swagger.json to /umbraco/openapi/{documentName}.json. If you generate a client from the spec (e.g. via the v17 extension template's package.json generate-client script), update the URL before regenerating.

Use the AddBackOfficeOpenApiDocument extension method

We added AddBackOfficeOpenApiDocument() in v18 to take the boilerplate out of registering an OpenAPI document. It's an extension method on IUmbracoBuilder that wires up Umbraco's sensible defaults so you don't have to.

Out of the box, the helper registers your document, scopes it to endpoints decorated with [MapToApi(documentName)], applies Umbraco's naming conventions for schemas and operation IDs, and adds the document to the Swagger UI dropdown at /umbraco/openapi/.

⚠️ Watch out: the first time you call AddBackOfficeOpenApiDocument (or AddOpenApi directly) and build, you'll hit error CS9137: The 'interceptors' feature is not enabled in this namespace. The Microsoft.AspNetCore.OpenApi source generator (which surfaces your XML doc comments as descriptions in the OpenAPI document, among other compile-time enrichments) propagates through Umbraco's project reference, but the property that enables it ships only with the Web SDK. Class-library projects don't get it automatically, so add it to your .csproj:
<PropertyGroup>
  <InterceptorsNamespaces>$(InterceptorsNamespaces);Microsoft.AspNetCore.OpenApi.Generated</InterceptorsNamespaces>
</PropertyGroup>

Minimal usage

public class UmbracoExtensionApiComposer : IComposer
{
    public void Compose(IUmbracoBuilder builder)
    {
        builder.AddBackOfficeOpenApiDocument("my-api");
    }
}

This will add and configure a "my-api" OpenAPI document that will display the controllers/endpoints that have the attribute [MapToApi("my-api")].

Typical usage

public class UmbracoExtensionApiComposer : IComposer
{
    public void Compose(IUmbracoBuilder builder)
    {
        builder.AddBackOfficeOpenApiDocument("my-api", document => document
            .WithTitle("My API")
            .WithBackOfficeAuthentication());
    }
}

Besides adding a "my-api" OpenAPI document, this will set the document title to "My API" and declare that the document's operations require backoffice authentication (which is what enables the "Authorize" flow in the Swagger UI).

Builder method reference

Method	What it does
`WithTitle(string)`	Sets the document's `Info.Title`. Also used as the UI dropdown label unless `WithUiTitle` is set.
`WithUiTitle(string)`	Overrides only the UI dropdown label, leaving `Info.Title` untouched.
`ExcludeFromUi()`	Suppresses registration in the Swagger UI document dropdown. Document is still reachable at its JSON URL.
`WithBackOfficeAuthentication()`	Registers the backoffice OAuth2 security scheme on the document and marks operations as requiring authentication. Swagger UI uses this to prompt for login; generated clients use it to send the token.
`ConfigureOpenApiOptions(Action<OpenApiOptions>)`	Adds a configuration callback for the underlying `OpenApiOptions`. Multiple calls will run in order after Umbraco's defaults.
`WithJsonOptions(...)`	Sets the `JsonOptions` used when generating the document's schema. See Aligning schema serialization below.

Aligning schema serialization

Schema generation needs to use the same JsonOptions your API uses at runtime, otherwise the generated SDKs and the actual payloads will not match. By default, Microsoft.AspNetCore.OpenApi generates schemas using the global HTTP JsonOptions, which means whoever hosts your extension can change them and that affects your schema.

For most backoffice extensions you want the BackOffice named JsonOptions (the same ones Umbraco's Management API uses). Point the document at them with WithJsonOptions:

public class UmbracoExtensionApiComposer : IComposer
{
    public void Compose(IUmbracoBuilder builder)
    {
        builder.AddBackOfficeOpenApiDocument("my-api", document => document
            .WithJsonOptions(Constants.JsonOptionsNames.BackOffice));
    }
}

For this to be meaningful at runtime, your controllers also need to serialize with those same options. The v17 extension template inherits from a plain ControllerBase, which uses the default options instead. Fix that by adding [JsonOptionsName(Constants.JsonOptionsNames.BackOffice)] to your own base controller or to each controller directly.

Without it, the schema reflects backoffice serialization but the actual responses are serialized with the default options, and you're back to the schema-vs-runtime mismatch.

Going beyond the defaults

The helper is not a closed box. Anything you'd normally do on OpenApiOptions (custom operation/schema/document transformers, your own CreateSchemaReferenceId, a replacement operation ID transformer, etc.) is still available through ConfigureOpenApiOptions. It just runs after Umbraco's defaults, so you compose on top of them rather than starting from scratch.

For example, registering your own schema transformer:

public class UmbracoExtensionApiComposer : IComposer
{
    public void Compose(IUmbracoBuilder builder)
    {
        builder.AddBackOfficeOpenApiDocument("my-api", document => document
            .WithTitle("My API")
            .ConfigureOpenApiOptions(options =>
                options.AddSchemaTransformer<MyExtensionSchemaTransformer>()));
    }
}

Migrating an existing composer

If your extension followed the shape of the v17 dotnet template, the migration is: delete the old composer body and write the AddBackOfficeOpenApiDocument(...) call. Below is the same extension's composer before and after.

v17 (Swashbuckle)

public class UmbracoExtensionApiComposer : IComposer
{
    public void Compose(IUmbracoBuilder builder)
    {
        builder.Services.AddSingleton<IOperationIdHandler, CustomOperationHandler>();

        builder.Services.Configure<SwaggerGenOptions>(opt =>
        {
            opt.SwaggerDoc(Constants.ApiName, new OpenApiInfo
            {
                Title = "My Test Extension Backoffice API",
            });

            opt.OperationFilter<UmbracoExtensionOperationSecurityFilter>();
        });
    }

    public class UmbracoExtensionOperationSecurityFilter : BackOfficeSecurityRequirementsOperationFilterBase
    {
        protected override string ApiName => Constants.ApiName;
    }

    public class CustomOperationHandler : OperationIdHandler
    {
        // ...
    }
}

v18 (Microsoft OpenAPI + new builder)

public class UmbracoExtensionApiComposer : IComposer
{
    public void Compose(IUmbracoBuilder builder) =>
        builder.AddBackOfficeOpenApiDocument(
            Constants.ApiName,
            document => document
                .WithTitle("My Test Extension Backoffice API")
                .WithBackOfficeAuthentication());
}

The helper registers UmbracoOperationIdTransformer by default, so the old IOperationIdHandler is no longer needed. If you want custom operation ID logic, register your own through ConfigureOpenApiOptions:

public class UmbracoExtensionApiComposer : IComposer
{
    public void Compose(IUmbracoBuilder builder)
    {
        builder.AddBackOfficeOpenApiDocument("my-api", document => document
            .ConfigureOpenApiOptions(options =>
                options.AddOperationTransformer((operation, context, _) =>
                {
                    operation.OperationId = $"{context.Description.ActionDescriptor.RouteValues["action"]}";
                    return Task.CompletedTask;
                })));
    }
}

Use Microsoft's AddOpenApi method directly

If you want to register a document that isn't a backoffice document, or you want to start from a clean slate without Umbraco's defaults, call AddOpenApi yourself. The helper is just a thin wrapper around that method. Umbraco already wires the OpenAPI routing and Swagger UI hosting, so you don't need to call MapOpenApi or configure endpoints. You only need to register your documents.

For the transformer model itself (how operation/schema/document transformers work), see Microsoft's Customize OpenAPI documents docs.

For Umbraco's specifics ([MapToApi] filtering via options.ShouldInclude, schema/operation ID conventions, the public UmbracoSchemaIdGenerator.Generate(type) helper), see the API versioning and OpenAPI docs.

A few things worth remembering:

Backoffice authentication: call options.AddBackofficeSecurityRequirements() (from Umbraco.Cms.Api.Management.OpenApi) instead of subclassing BackOfficeSecurityRequirementsOperationFilterBase.
Swagger UI registration: documents are no longer auto-listed. Call services.AddOpenApiDocumentToUi(documentName, uiTitle) to surface yours in the dropdown.
InterceptorsNamespaces opt-in: same as the helper path. See the Watch out callout at the top of the helper section.

Keep using Swashbuckle

Not recommended. Consider this only if rewriting a complex Swashbuckle setup isn't feasible right now. Trade-offs:

Extra dependency on Swashbuckle.AspNetCore.
OpenAPI 3.0 output, whereas the rest of Umbraco's documents emit 3.1.
Extra wiring you maintain yourself.
Both libraries depend on Microsoft.OpenApi. A breaking change there that Swashbuckle doesn't follow leaves your extension incompatible with the rest of the stack.

If you still want to go this route, see the Swashbuckle.AspNetCore README for general setup. The rest of this section is the Umbraco-specific wiring.

1. Install the NuGet package

Add a PackageReference to Swashbuckle.AspNetCore in your extension's .csproj (or dotnet add package Swashbuckle.AspNetCore).

2. Register Swashbuckle and your document in a composer

In v17, Umbraco called AddSwaggerGen for you and your extension only configured SwaggerGenOptions. In v18 you have to call it yourself:

public class UmbracoExtensionApiComposer : IComposer
{
    public void Compose(IUmbracoBuilder builder)
    {
        builder.Services.AddSwaggerGen(opt =>
        {
            opt.SwaggerDoc(Constants.ApiName, new OpenApiInfo
            {
                Title = "My Test Extension Backoffice API",
                Version = "1.0",
            });

            var previousDocInclusion = opt.SwaggerGeneratorOptions.DocInclusionPredicate;
            opt.DocInclusionPredicate((docName, apiDesc) =>
                docName == Constants.ApiName
                    ? apiDesc.ActionDescriptor.HasMapToApiAttribute(docName)
                    : previousDocInclusion?.Invoke(docName, apiDesc) ?? true);

            // any operation filters, schema filters, or other v17 setup you had...
        });
    }
}

3. Host the Swagger JSON middleware via an IUmbracoPipelineFilter

Umbraco no longer calls app.UseSwagger(), so the middleware that serves the Swagger JSON isn't running. Add it through Umbraco's pipeline filter, and set the RouteTemplate to match UmbracoOpenApiOptions.RouteTemplate (default umbraco/openapi/{documentName}.json) so the dropdown link resolves.

public class UmbracoExtensionApiComposer : IComposer
{
    public void Compose(IUmbracoBuilder builder)
    {
        builder.Services.Configure<UmbracoPipelineOptions>(options =>
        {
            options.AddFilter(new UmbracoPipelineFilter("Swashbuckle")
            {
                PostPipeline = app =>
                {
                    var openApiOptions = app.ApplicationServices.GetRequiredService<IOptions<UmbracoOpenApiOptions>>().Value;
                    if (!openApiOptions.Enabled)
                    {
                        return;
                    }

                    var routeTemplate = openApiOptions.RouteTemplate;
                    app.UseWhen(
                        ctx => ctx.Request.Path == routeTemplate.Replace("{documentName}", Constants.ApiName).EnsureStartsWith('/'),
                        branch => branch.UseSwagger(c => c.RouteTemplate = routeTemplate));
                },
            });
        });
    }
}

Scope the middleware to your own document's URL. Otherwise Swashbuckle intercepts requests for Umbraco's own documents (Management, Delivery) and returns 404 because they aren't registered with AddSwaggerGen.

4. Register the document in the Swagger UI dropdown

public class UmbracoExtensionApiComposer : IComposer
{
    public void Compose(IUmbracoBuilder builder)
    {
        builder.Services.AddOpenApiDocumentToUi(Constants.ApiName, "My API");
    }
}

TL;DR

The helper is the simplest option for most extensions. AddBackOfficeOpenApiDocument() is what the v18 template uses, gives you Umbraco's sensible defaults out of the box (naming conventions, Swagger UI registration, JsonOptions alignment), and lets you register an OpenAPI document in a single call.

Calling AddOpenApi yourself is the standard ASP.NET Core approach and works fine. It means more wiring and code to maintain, so reach for it when you need full control (non-backoffice documents, or skipping the Umbraco defaults).

If rewriting really isn't an option right now, keeping Swashbuckle as your own dependency and plugging into the dropdown via AddOpenApiDocumentToUi(...) will get you through, but plan to revisit when you can.

Building a Passwordless Authentication Library for Umbraco - Part 1: Why?

Tue, 19 May 2026 12:36:58 Z

Releasing Image Hotspot 17.0.0

Tue, 19 May 2026 09:23:05 Z

Releasing Image Hotspot 17.0.0 | skttl.dev

AI on Your Terms: How Umbraco Reimagines AI

Tue, 19 May 2026 00:00:00 Z

AI is often introduced as a shortcut: more content, more insights, more efficiency. But for many organizations, especially those responsible for digital platforms, the initial excitement is quickly followed by unease. Who is in control of the output? What happens to sensitive data? And how do you ensure that automation doesn’t quietly erode quality, tone, or accountability?

uProfile May 2026 - Bernadet Goey

Mon, 18 May 2026 00:00:00 Z

Meet Bernadet: Former PHP-specialist, now a confident Umbraco Developer, looking to give back to the community that supported her journey

HCS.Passwordless.Otp

Mon, 18 May 2026 00:00:00 Z

One-time password (OTP) email add-on for Umbraco 17 passwordless member authentication. Delivers a short numeric code by email that the member enters to sign in. No passwords required.

HCS.Passwordless.MagicLink

Mon, 18 May 2026 00:00:00 Z

Magic link passwordless authentication for Umbraco 17 members. Send a one-click sign-in link by email — no passwords required. Includes built-in rate limiting, single-use tokens, and customisable branded emails.

HCS.Passwordless.WebAuthn

Mon, 18 May 2026 00:00:00 Z

WebAuthn/FIDO2 passkey add-on for Umbraco 17 passwordless member authentication. Enable hardware-backed biometric or security-key sign-in via the browser's Credential Management API. No passwords required.

Share the Love - Bringing #H5YR to jcdc.dev

Sat, 16 May 2026 09:00:00 Z

I've added the new #H5YR widget to my sites. Send a virtual High Five!

uSkinned Site Builder for Umbraco 17

Fri, 15 May 2026 14:03:31 Z

📣 Introducing 🥁 uSkinned Site Builder for Umbraco 17 🤩 Full support for Umbraco 17 is now available for uSkinned Site Builder. Install or upgrade today.

From zero to working product in two hours

Fri, 15 May 2026 07:58:10 Z

Umbraco.AI.Agent.UI

Fri, 15 May 2026 00:00:00 Z

Shared chat UI components for Umbraco AI Agent surfaces

Umbraco.AI.Agent.Copilot

Fri, 15 May 2026 00:00:00 Z

Copilot chat UI for Umbraco AI Agent

Modgift.Umbraco.Breakable

Fri, 15 May 2026 00:00:00 Z

A Breakable property editor for Umbraco CMS that lets editors mark soft-hyphen break points inside text values using | as a delimiter.

Our.Umbraco.PropertyToolTip

Fri, 15 May 2026 00:00:00 Z

Property ToolTip keeps Umbraco property descriptions available, but shows them as small tooltip help text beside each property label.

SwiftUI is a Disaster

Thu, 14 May 2026 17:24:48 Z

I’ll admit it. I’m still programming for Apple platforms using Objective-C, AppKit and UIKit.

Continue reading on Medium »

The Umbicosaurus De-Extinction: The Community Effort that Brought a Better Icon Picker to Umbraco 17.4

Thu, 14 May 2026 09:58:00 Z

In 2021, I dreamed of improving the icon picker in the Umbraco backoffice and today, in Umbraco 17.4, the package I started is making a splash as part of Core! This is the story of Umbicosaurus.

Articulate v6 RC 2

Thu, 14 May 2026 08:29:22 Z

Umbraco Scotland: Glasgow Edition, May 2026

Wed, 13 May 2026 09:00:58 Z

Umbraco Scotland: Glasgow Edition, May 2026 A great evening, bringing the Umbraco Scotland community together to share ideas and insights.

Umbraco.Community.HoldYourHorses

Wed, 13 May 2026 00:00:00 Z

Replaces the Save and Publish button in the Umbraco backoffice with a configurable, cancellable countdown — gives editors a short window to catch mistakes before content goes live.

Umbraco.Community.SmartRedirectSuggester

Wed, 13 May 2026 00:00:00 Z

Improve the Umbraco trash flow by suggesting redirect targets for published content before it is moved to the recycle bin.

DocTypeDoctor

Wed, 13 May 2026 00:00:00 Z

...

May 2026 Cloud Release Notes

Tue, 12 May 2026 15:21:19 Z

May 2026 | Cloud | Umbraco Documentation

Carlini-style software vulnerability hunting, on a budget

Tue, 12 May 2026 13:31:23 Z

https://www.etive-mor.com/blog/carlini-style-vulnerability-hunting-on-a-budget/Nicholas Carlini did a great talk at [un]prompted a few weeks ago, where he detailed how Anthropic were using LLMs to automate software vulnerability discovery. In this post, I take a look at replicating his process in the Umbraco-CMS repository, for less than 1% the cost.#umbraco #security #llm #ai

The new H5YR.com widget is now LIVE!

Tue, 12 May 2026 13:01:00 Z

The new H5YR.com widget is now LIVE! https://h5yr.com/h5yr-widget/ #umbraco

H5YR.com is now on Umbraco 17

Tue, 12 May 2026 07:08:15 Z

H5YR.com is now on #Umbraco 17 🎉 Thanks @UmbHost for the help with the deployment yesterday. #h5yr

H5YR embeddable widget progress

Mon, 11 May 2026 16:52:10 Z

H5YR update: https://www.linkedin.com/posts/owainwilliams_h5yr-community-umbraco-share-7459538862323924992-iV5D?utm_source=share&utm_medium=member_ios&rcm=ACoAAABj9KwBjr581HKBv-M3TbQu69Ia79rmfPw Sent from my iPhone

Designing an AI Agent skill for adding a page type to Umbraco

Mon, 11 May 2026 11:00:00 Z

Explore how experienced developers are building AI skills to scaffold Umbraco features. See the conventions and decisions that make page type creation effortless.

Adam Shallcross AI based search package progress

Mon, 11 May 2026 06:41:24 Z

Untitled: https://www.linkedin.com/posts/adamshallcross_quick-update-on-the-ai-search-package-im-ugcPost-7457449420633042944-t2zb?utm_source=share&utm_medium=member_ios&rcm=ACoAAABj9KwBjr581HKBv-M3TbQu69Ia79rmfPw Sent from my iPhone

Diplo Translator

Fri, 08 May 2026 08:28:41 Z

Diplo Translator | Umbraco Marketplace

Umbraco.Community.AI.Chatbot

Fri, 08 May 2026 00:00:00 Z

Drops a public-facing, AI-powered chat widget on a website's frontend. End users on the public site type a question; the package runs a semantic search over the site's Umbraco content (Umbraco.AI.Search), feeds the matched pages into an Umbraco.AI.Agent, and streams a grounded answer back with cited source pages and follow-up suggestions. The official Umbraco.AI.* packages expose chat only inside the backoffice. There is no path for an anonymous site visitor to ask questions of the site's content. This community package fills that gap. Key features: - Public-facing widget (drop in one