Umbraco.CMS.Backoffice VS Umbraco

If you'd like to see an example implementation of using the umb-property-dataset and umb-property elements there is an example in the Umbraco BackOffice code base here.

Umbraco.CMS.Backoffice - The main source code for the new back office UI, previously the demo project as part of RFC 0024

Nowadays, especially for any Umbraco extensions I develop, I try to follow Umbraco's own namespaces as closely as possible. e.g. I'd put my custom IContentFinder classes under a [Brand].Web.Routing namespace. Mostly so that it feels logical for any other developers who may be familiar with Umbraco core code.

🔴 Umbraco-CMS: The simple, flexible, and friendly ASP.NET CMS used by more than 730.000 websites.

Umbraco

Umbraco - for .NET devs

I discovered that I could recreate the behaviour manually if I deleted the TEMP index files. For about 1 minute I got 0 results, but then it fixed itself. Using the debugger, I discovered the ExamineIndexRebuilder class and the RebuildOnStartupHandler. As it turns out, these are the key classes that handle index initialisation. There were a few changes that I had to make in order to get my integration tests to work:

As /u/transhumanist2000 said, the only other one I've seen that looked heavily supported and had a sizable following are dot net nuke, and I'd add, Umbraco (https://umbraco.com/). Unfortunately I haven't heard the best of feedback about these cmses.

I really like Umbraco (https://umbraco.com/), It has a decent community, and is on DotNetCore these days makes it very easy to use. You can setup most basic things yourself, but since it exists as a satellite to your site. You can integrate with it as deeply or not as you want. Plus the workflow for defining content is nice, the customer-facing UI is also slick, and adding custom elements to it and extending is easy too. Plus it's free.

This is an extension for Umbraco (version 9+) that lets you use your Umbraco content in a headless fashion. It is highly customizable, and you can tweak or replace every aspect of the generated output.

This week I became Umbraco HQ's Director of Developer Relations. We're not known for sensible job titles but I wanted to let you know that this call was, in fact, mine.

Note: While testing and writing this post I found an issue with nodes having a listview, so if that isn't really working as expected. See the issue here.