<a href="https://www.alexedwards.net/blog/11-tips-for-structuring-your-go-projects" target="_blank" rel="noopener nofollow">11 tips for structuring your Go projects - Alex Edwards</a>

A supportive squad for Go developers who want to dive deeper into what makes Go special. We focus on the language's clean simplicity, powerful concurrency, and reliable performance.

Go Developers

Learn 11 tips to effectively structure your Go projects for better organization and maintainability. The guidance covers various aspects, from organizing directories and files to best practices in coding and project management.

11 tips for structuring your Go projects

I dont agree with 9. I think big files in any language especially if you are using Git is going to cause you issues. A bad merge can be way more complex with a large file than a few smaller files.

Thanks for the article!
But I have a question:
In a website context, how would you organize your website features ?
Could we make <code>internal/&lt;feature name&gt;</code> ? Or just <code>internal/features</code>?