Plates VS tailwind-nextjs-starter-blog

I use PHP with Route, the Plates template engine, and my blog posts are markdown files grouped by folder (year/month/day.md).

If it's a simple project you could try Plates. Escaping is a little more verbose, but you don't have to learn any new syntax since it's native PHP.

✅ Plates

Start reading through PSR standards and see if some (not all) of them sound like good ideas to you, and write a mini framework of your own around those ideas, with composer to import high quality third party packages such as Plates.

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.