Umbraco VS contentlayer

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.

This looks and sounds great...

I'm currently using [contentlayer.dev](https://github.com/contentlayerdev/contentlayer) to manage docs and blog content, mostly .mdx files on urlbox.com.

It works well with next.js but unfortunately is abandonware now.

I also have a few custom remark/rehype plugins.

You're right it is a pain to update articles buried in your repo especially with less technical team members. I already tried out TinaCMS to try and solve the editing issues, but their editor wasn't so nice, and it seemed to implicitly make a commit on every tiny change to any content, so I'm really hoping I could use something like this to edit my already existing content...

Content Management: Contentlayer

For my personal website, I use Next and Contentlayer since I prefer to write my content as markdown files. I then host it using vercel's free tier.

I've seen https://www.contentlayer.dev/ used for similar stuff on open source codebases like taxonomy from shadcn

Contentlayer makes it super easy to grab our mdx blog posts in a type-safe way.

Flowershow uses Contentlayer to turn your Markdown content into data stored in JSON files. By defining document schemas, Contentlayer can generate data that is validated (making it type-safe) and can be imported from anywhere in your Next.js app.

My first reaction was to use MDX and use next/image just as in the example. But that means that we can't use normal markdown images and it turns out that this won't work with contentlayer. This wont work, because Next.js does some magic on the import of the static image. The object which gets returned by the import, contains not only a path to the image, it contains also the width and height, plus a very small version of the image for the blurred placeholder. This magic does not work if the MDX file is loaded with contentlayer, because contentlayer uses its own bundler, which does not know about the import magic for images.

After the installation we have to tell MDX that it should use the plugin. The example below shows a contentlayer config, but it should work with every MDX setup.