website VS bulletproof-react

As engineers, we all know the feeling of encountering a stubborn bug that defies easy resolution. The Gitpod team recently faced such a challenge when we discovered a bug with our Gitpod Docs Search functionality during a comprehensive documentation restructure. The search feature was not updating correctly, returning outdated data even after we manually ran an Algolia indexing query to update the production data with newly deployed changes. This left us scratching our heads, wondering how to resolve the issue and ensure that our users could access the most up-to-date information quickly and easily.

This is a small doc from a PR I submitted to Gitpod's how-to guides but the prefer to have only a few databases in this guide (PostgreSQL, MySQL, Redis, MongoDB). No problem, I'll post this doc here.

Here is their repository on GitHub: https://github.com/gitpod-io/website

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.