tailwindcss.com VS taxonomy

I'm a self-taught aspiring developer. Lately I've been exploring some of the frameworks everyone has been talking about in the React space. Nextjs 12, Astro, Remix, then Nextjs 13. I noticed that most of them mention MDX support. I didn't know anything about it, and even saw tailwind use it for their docs pages. I see how it could be beneficial for text heavy pages, otherwise the additional MD syntax and configuration seems like too much overhead.

Are there any Next 13 large scale open source project that people can view like https://github.com/tailwindlabs/tailwindcss.com (its in Next 12 i guess)

Today I learned that Tailwind's website is also an open source Next.js app! https://github.com/tailwindlabs/tailwindcss.com

For example, consider this project: https://github.com/tailwindlabs/tailwindcss.com

You could check out https://github.com/tailwindlabs/tailwindcss.com I haven't looked through the source

I wanted to make room for non-c# backend frameworks, so I switched from netcoresaas.com to saasfrontends.com. This way I could build Vue/React/Svelte frontends, without being tied to .NET. I built the SaasFrontends site using the non-MIT licensed tailwindcss.com repo, I really hope this doesn't get me in trouble 😟.

I am building this app with inspiration from Taxonomy and Acme corp so a lot of the design comes from there.

View on GitHub

Now, I must confess that I'm primarily a back-end engineer, and crafting a beautiful front-end was, well, a bit of an adventure. To keep things straightforward, I opted for simplicity. I figured I could enhance it as my customer base grew, as the real value, of course, lies in the robustness of the API and its backend. Looking back, I might consider using a template like https://tx.shadcn.com/ if I were to start all over again. It appears to be a great starting point for any SaaS, but the setup might pose some challenges.

Check out these two GitHub repositories: https://github.com/sadmann7/skateshop/ and https://github.com/shadcn/taxonomy/. They both use Next.js 13 and have well-structured folders and well-written code. Next.js provides performance optimization. To improve it further, avoid loading unnecessary items and use a CDN for fast content delivery. Both not loading unnecessary content & lazy loading) and CDN is 2 individual topics to dive into.

I've also been inspired by this repo, but the Vercel template seems more achievable for me at this point.

In addition to the repository I mentioned in my original post, I've also been inspired by another repository (Taxonomy Repo) which has implemented a similar Stripe integration. However, this one is a bit more complex and I'm finding the Vercel template to be more achievable for my current skill level.

I'm currently working on a Next.js project where I'm trying to integrate Stripe for payments and webhooks. I've been following the Taxonomy GitHub repo for guidance, particularly for setting up the app router and the lib files.