Umbraco VS tailwind-nextjs-starter-blog

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.

Inspired by tailwind-nextjs-starter-blog

At Axolo (https://axolo.co/blog), we love this tailwind next.js open source project https://github.com/timlrx/tailwind-nextjs-starter-blog

I recommend that you find a template that looks reasonably good. You can than spend time on adding features to an already nice looking page. this is the template that I started with: https://tailwind-nextjs-starter-blog.vercel.app/ and I have made some small tweaks over time and now it looks like this: https://www.einargudni.com/

The repo you linked uses this pattern: https://github.com/timlrx/tailwind-nextjs-starter-blog/tree/master/pages/blog

Also visit the link below, in the answer there's a website that will help you https://github.com/timlrx/tailwind-nextjs-starter-blog/issues/577

I'm a fan of timlrx/tailwind-nextjs-start-blog [1]. It's easy to customize, responsive, uses Markdown, and makes use of SSR for SEO optimization.

https://github.com/timlrx/tailwind-nextjs-starter-blog#quick...

You can deploy it on Vercel for free and then point it to a custom domain using DNS records in the Vercel "Domains" tab.

I've been looking for a good, flexible template for SvelteKit / Tailwind CSS, but all the templates I found were either too simple, missing some needed features, or were too difficult to customize (or both). I loved Timothy Lin's simple but feature-rich Tailwind Nextjs Started Blog, so I decided to port that to SvelteKit, and add a few things I needed, including Netlify CMS, dynamic Open Graph image (og:image) support.