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.

The Dutch Umbraco community is back

The Dutch Umbraco community is back! About 100 of us came together at STOOM in Apeldoorn for the very first Dutch Umbraco Alliance Festival. AI, Aspire, headless, a keynote I wasn't supposed to give, and a venue that practically had to kick us out at closing time. Here's my look back at the day.

by Sebastiaan Janssen 10 min read

When the Community Comes Together: Celebrating the first-ever Umbraco India Festival

Last week, something very exciting happened in India. In this post, you will hear the story of what happens when the community comes together.

by Mathilde Høst 4 min read

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.

by The Developer Relations Team 3 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? Submit it here!

Examine 3.10.1 and 4.0.1 released

Examine 3.10.1 and 4.0.1 are out on NuGet now. Both are patch releases and the main reason for them is a fix for an analyzer issue that could cause queries to be parsed with the wrong analyzer. The analyzer fix This was reported in #613 and it's been lurking for a long time, but it's an edge case that only shows up if something uses the index's analyzer before the index's field value types have been resolved on startup. With a normal startup that doesn't happen, which is why it hasn't come up before. LuceneIndex.FieldAnalyzer is lazily created and cached, but the per-field analyzer mappings were populated lazily too, so if the analyzer was used first, the PerFieldAnalyzerWrapper would cache the default analyzer for those fields. That stuck around for the life of the index, so any searcher created from it kept using the default analyzer for fields that were configured to use something else. So if you had a field configured with a KeywordAnalyzer, a native query like this: someField:"contentPage" could end up parsed as: someField:contentpage which is the StandardAnalyzer lower casing it, and then you get no results and a bit of head scratching. The fix in #621 is quite small: the field value types are now resolved before the analyzer wrapper is constructed, so it can't cache a fallback analyzer for a configured field. There's a regression test for it too. Other changes A few small allocation improvements in OrderedDictionary.Values, LuceneIndex.GetFieldNames and LuceneSearchQueryBase. These came from the agentic perf workflows I have running on the repo, which open PRs for this sort of thing that I then review. The docs site is updated for v4 and the v1/v2 docs are now marked as unsupported. A new release process These are also the first releases shipped with the new release process. Previously I'd tag a release, wait for the build, download the zip of packages, unzip them and push them to NuGet from my terminal. Now pushing a tag builds the packages and then waits for me to approve the deployment in GitHub. Once approved, it publishes to NuGet with trusted publishing (so no API keys sitting around) and creates the GitHub release with the packages attached. I also switched versioning from GitVersion to MinVer, which just uses the tag, which is all I wanted anyway. That's mostly only interesting to me, but it does mean releases should happen a bit more often now that there's less toil involved :) Release notes for each are on GitHub: v3.10.1 and v4.0.1. Happy Searching!

by Shanon Thompson (Deminick)

Estimating the CO2 of your Umbraco AI usage

A new community package adds a CO2 tab to Umbraco AI Analytics, estimating the energy and CO2e of your AI chat usage with the EcoLogits method.

by Matt Brailsford

AI is changing how I approach Umbraco development

Building a PDF metadata dashboard with AI made me reconsider when I reach for Umbraco's standard tools and when a custom extension is worth the maintenance.

by Søren Kottal

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