Welcome to the Umbraco Community!

The Umbraco Community is at the heart of the Umbraco ecosystem. It’s built on people coming together to share ideas, help each other, and make Umbraco better every day.

Come see how the Community stays connected, what makes it such a great place to be, and how you can join in and get involved. We always have room for more people to join!

Join the community
MVP Summit audience.jpg 54610954933_1fd227623f_o (1).jpg Panel speaking in mics at umbraco event Person looking at laptop 52993341606_3b3a6a6991_o.jpg 2025 Group picture 1740139582170.jpg IMG_4217.jpg IMG20251030182101.jpg 2025 Community Teams day at Umbraco HQ DSC04687.jpg DSC05663.jpg MVP getting high five on stage MVPs speaking at MVP Summit 2 MVP waving at MVP Summit MVPs showing off awards IMG20251106141733.jpg 20251204_173423.jpg b6f67a24-17ea-4a21-bc55-65eca97d86ac.jpeg Codegarden 2023 Business Summit - people talking.jpg People high five'ing at Codegarden.jpg Boat ride 2025 Codegarden runners running

Get involved in the community

There's so many ways to get involved in the Umbraco community. 

A person looking into his laptop surrounded by people and light

New here? Welcome! We have a complete newcomer's guide to Umbraco and the Umbraco Community waiting for you.

New to Umbraco

A woman concentrating and looking down

No matter your interests, skills and time availability, there’s a way for you to participate in the Umbraco community. 

Find your path

Two people high five'ing

Umbraco Meetups are a great way to engage with the Umbraco community and meet other like-minded people.

Join a meetup

See what's happening

Join a meetup or an event near you - see all upcoming Umbraco events here

Read about the Umbraco Community

Get updates on what's happening directly from Umbraco and The Developer Relations team.

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

The time has finally come for the second part of this exciting two-part series. This time, you will hear from Sebastiaan and Laura, who share what they are most excited about on the new Community site.

3 min read

Saying Goodbye to the Commerce Advisory Board

For the last two years, the Commerce Advisory Board has been a driving force behind how we think about and shape Umbraco Commerce. But all good things come to an end. Commerce is in a really good place today, with our main focus on stability and reliability, though we'll keep evolving it where it makes sense. With that, it's time to close this chapter.

2 min read

An hour on Our, one last time

We have just retired our.umbraco.com. This is a thank you, and a fond farewell.

15 min read
Read more on the blog

Blog posts from the Umbraco Community

Explore the latest blog posts from our community. Want to add your future blog posts to the list? Contact us here and let us know!

Expanding the backoffice search in Umbraco - Highlighting lesser known Umbraco features

Recently, I started using Erik-Jan Westerndorp's community package "Heading". on a project. It’s one of those packages that solves a very specific problem really neatly. In this case, the client wanted editors to be able to choose the heading level for a title on an element. So, for example, one image block might need an H2, while another might need an H3, depending on where it sits on the page. The package worked great for that. But, as often happens, solving one problem uncovered another. Not long after, the client came back with a new bit of feedback: I can’t search for the custom title I’ve added. And honestly, my first reaction was: surely that should just work? So I gave it a try - and they were right. The backoffice document search was only finding results based on the page name, not on values stored in custom fields. Searching by page name returns the page Searching by page title returns no results The first thing I did was check the internal index — and the title field was there, so that allowed me to cross off one possible issue. So the content was being indexed - it just wasn’t being searched by the backoffice search. I asked a few colleagues about it, and the general feeling was that this probably wasn’t something you could change. The assumption was that Umbraco backoffice search just searches a predefined set of fields and that was that. Still, it felt like there had to be a way. And there is. The Missing Piece: UmbracoTreeSearcherFields It turns out this is already supported and documented, but it was a feature I hadn’t come across before. Since I suspect I’m not the only one, it’s worth highlighting here: Backoffice Search - A guide to customization of Backoffice Search That article introduced me to UmbracoTreeSearcherFields, which controls the indexed fields used by backoffice search. By replacing it with a custom implementation, you can expand the list of searchable fields. My first attempt looked like this: public class CustomUmbracoTreeSearcherFields(ILanguageService languageService) : UmbracoTreeSearcherFields(languageService), IUmbracoTreeSearcherFields { public new IEnumerable<string> GetBackOfficeDocumentFields() { return new List<string>(base.GetBackOfficeFields()) { "title" }; } } I restarted my environment, tried again… and it still didn’t work. Backoffice search could still only find the page by name. The Catch: Variant Field Names After taking a closer look at the index, the reason became clear: the field key wasn’t simply title. Because the property had language variants, the indexed field name includes the language ISO code. So instead of hardcoding a single field name, I updated the implementation to generate the variant field names dynamically. That also makes it more future-proof — if new languages are added later, search continues to work without any code changes. Here’s the updated version: public class CustomUmbracoTreeSearcherFields(ILanguageService languageService) : UmbracoTreeSearcherFields(languageService), IUmbracoTreeSearcherFields { private static readonly string TitleAlias = PublishedModelHelper.GetModelPropertyAlias((Page x) => x.Title); public override IEnumerable<string> GetBackOfficeDocumentFields() { return base.GetBackOfficeDocumentFields().Concat(GetVariantFieldNames(TitleAlias)); } private IEnumerable<string> GetVariantFieldNames(string alias) => languageService.GetAllAsync().GetAwaiter().GetResult().Select(l => $"{alias}_{l.IsoCode.ToLowerInvariant()}"); } And with that in place, the backoffice search started returning results based on the custom title value as well. Why I’m sharing this This is one of those things that’s probably obvious once you’ve worked with it before, but until then, it’s easy to assume backoffice search is less flexible than it actually is. If you’ve got editors relying on custom fields it’s worth checking whether those fields are included in backoffice search. If they’re already indexed, you may only need to extend UmbracoTreeSearcherFields to make them searchable. A small change, but a very useful one for editors.

by Bernadet Goey

Umbraco Codegarden 2026 Day 1: AI, Elements & Community News | manifesto

Explore key takeaways from Day 1 of Umbraco Codegarden 2026, including major product keynotes, AI governance, new Elements features, and the Umbraco Awards.

by Rich Howell

Setting up Windows Server 2025 for Umbraco

Every time I build a new server I go through the same sequence, and every time I find myself trying to remember what I did last time. So this is my reference for turning a clean Windows Server 2025 instance into something that will happily host Umbraco on IIS and SQL Express, in the order I actually do things.

by Justin Neville

See more Community blog posts

Get in contact with us

Would you like to discuss how you can get more involved in the Umbraco Community? Please contact the Umbraco Developer Relations team via the button below.

Contact DevRel