UMB.FYI Firehose - News

Umbraco Package: Automate Inspector

Wed, 17 Jun 2026 07:00:00 Z

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

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.

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

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.

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!

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.

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

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

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

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

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

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

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.

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.

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.

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

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

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

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.

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

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.

DocTypeDoctor

Wed, 13 May 2026 00:00:00 Z

...

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.

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.

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