Orchard Core VS Umbraco

In open source OrchardCore is ok in terms of project-complexity. When building OrchardCore (AVG 10 runs): https://github.com/OrchardCMS/OrchardCore with $git clean -fdx && dotnet build OrchardCore.sln --force Macbook: Time Elapsed 00:02:13 (AVG 10 runs) Dell: Time Elapsed 00:02:48

While I've been peripherally present in the game industry through my activity here and on GitHub as a Godot contributor, the vast majority of my time as a developer for the past 5 and a half years has been in web development (largely server/database with some frontend) so take that as you will. In that time, I've seen, worked in, and outgrown several project architectures. At this point, I think I've gotten to know the one that works the best, in part because while it has worked for me, it's also the same one that Microsoft employs to maintain its high-profile open-source projects (which are orders of magnitude more complex than anything I've come up with). A good example is the Orchard Core CMS.

Check out orchardcore, the framework not the cms https://github.com/OrchardCMS/OrchardCore it implements multi tenancy pretty easily

The project code is available in the repository on GitHub. We check the code with the PVS-Studio static code analyzer.

If you do want a .NET IdP then you could look into OpenIddict but will require some hands on work, at a minimum authorisation controllers. If you're looking for something more out of the box OrchardCore's OpenId module might be better for you.

As the older roadmap says, it was to be released in 2019. https://github.com/OrchardCMS/OrchardCore/wiki/Roadmap/a4277c874b4f7480c55f02d5a148e4bbb2ff0bcf

Orchard Core Framework (https://github.com/OrchardCMS/OrchardCore/), is a really good technique to implement modularity. Every module is self contained and you can share resources as needed.

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.