Consider refactoring the format of the repo to follow Go best practices, and have fewer items in the root directory

[echarrod]

Hello,

Just had a bit of advice that would certainly help me understand the code better. It seems all the code is at the top level. In my opinion this is harder to read and understand as:

1. Code isn't "categorised into areas", and I'm not sure where to find things
2. You have to scroll down quite far to get to the README!
3. packages can help follow the "single responsibility principle", rather than the whole repo doing everything.

I know I see the code is auto-generated by Crank, but hoping it's possible to find a solution that makes the code easier to digest.
Potentially following code such as https://github.com/golang-standards/project-layout would help 🙏