Template and/or specific guidelines

I think it would be advantageous to offer a template and/or specific guidelines with respect to directory structure, file naming, structure and content of the cabal files etc.

It might be that you already thought about this, and do not want to impose any restrictions on the "bits". If so, could you please provide your reasons?

If not, I suggest providing at least a project template with a basic cabal file (probably with all components: an executable, a library, a test, and a benchmark (probably others?)). I also saw that the projects all provide a `stack.yaml` file. This could be made mandatory (or not, depending on where we want to go).

I also thought that one could divide the bits into "applications", "libraries", etc. (but maybe some bits belong into neither of those categories). This is just a thought that came up. I do think though, that structure is going to help people find the "bit" they are looking for.