taxonomy VS bulletproof-react

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.

Using -> this guide to help structure a project in a better way

bulletproof react

Well I’d definitely have a file structure in place. I use bullet proof react as my go to. But I mean like…I’d say there’s probably 10 things causing 90% of the problems. So things like folder structure, yes, but also how long the files are, I mean…how enmeshed it all is…maybe the naming conventions.

Follow this: https://github.com/alan2207/bulletproof-react

Your approach is similar to bulletproof-react, which I personally love. I have built projects of all sizes with it and the DX was always nice! Check it out if you want and good luck on your project 😁

Link for the lazy ones.

Not sure if this helps, but Bulletproof React is a very good architecture to React projects of any size. Maybe it can give you some insight on how to structure your project. Good luck!

Been content with how Bulletproof react does it, only thing missing for me is differentiation between views and components.