Convention on a model builder template

[brynpickering]

Is this suggestion related to a problem? Please describe.
I'd like to use lots of modelblocks together in a model building exercise. There are integration examples in each modelblock but what I lack is some clear idea of how I would best bring them together when building a model. In particular, when modelblocks interact (hydro module needs power plant and geoboundaries module outputs), I'd find it easier if it's all just ready for me to go rather than creating all those linkages myself. I'm also missing some central idea on the "best practice" for structuring a model building workflow repository.

Describe the solution you'd like
Although each model building exercise will have its nuances, I would like to see a copier template for a recommended model building repository living alongside the modelblocks, linked to each convention. This could e.g. have:

• all the modelblocks waiting as modules along with bare config files for each and coherent pathvars. Then the user can pull those in as they like, or just ignore them in favour of their custom, project-specific approach.
• CI, docs, etc. ready to go for some general things that any snakemake workflow would benefit from.
• (possibly) opinionated directory structure for some pre-defined modelling frameworks, that the user can select if that is the framework they will be using (with an "other" option obviously available).

Describe alternatives you've considered

• Different orgs maintain their own templates
• No template, just a wild west of model building exercises.

Additional context

• There are existing templates out there, like this one from @timtroendle.
• Currently pypsa-X projects are usually soft forks of some central project (e.g. pypsa-eur or pypsa-earth). This is almost like templating, but with way more issues caused by the heavy interconnectivity between upstream and downstream projects.