Structuring your project or in other words your codebase is a very important and fundamental step. Nevertheless most developers don’t know how to do it the right way. I often see common mistakes like throwing all components into a single components folder, putting fetching logic directly inside server components, or cramming all mutation logic into one file. These mistakes will eventually make your application impossible to scale. But don’t worry in this video I will show you how to structure your codebase and project the right way!
<a href="https://www.youtube.com/watch?v=kH9Q8j-X7po&amp;t=345s" target="_blank" rel="noopener nofollow">https://www.youtube.com/watch?v=kH9Q8j-X7po&amp;t=345s</a>

Reinier

Learn proper project structure techniques to avoid common mistakes like dumping all components in one folder, mixing fetching logic with server components, or consolidating mutation logic. Proper organization is essential for building scalable applications that can grow over time.

Here is How to Structure Your Project the RIGHT Way

The thoughts are all right.
But the video suggesting that folder structure is equal to architecture.
Which is not true! Please be careful, a good folder structure doesnt mean that in depth your architecture is right.