Compare and contrast this with the Go Standards project-layout repo example[1] - which ironically is not a standard at all. Personally I prefer a bit more rigi

Compare and contrast this with the Go Standards project-layout repo example[1] - which ironically is not a standard at all. Personally I prefer a bit more rigidity in how the project is structured (/pkg/, /pkg/internal/, /cmd/) since it is more opinionated and requires less thinking. Typically my repos won't just have a Go backend but also a frontend too, and supporting assets, as well as documentation (designs, decisions, etc.) [1] https://github.com/golang-standards/project-layout https://github.com/golang-standards/project-layout