Taking this issue on GitHub as a starting point, I would like to discuss some kind of "best practice" guideline for modules.
This thread is aiming at the assets itself (like "here they are, I don't know what you'll do with them, but maybe they'll be usefull") instead of how assets depend and extend each other - this question is topic of another thread!
Basically, the problem to discuss is how general modules should be and which resources should belong to the scope of a single module. The use case this discussion is build around involves the modules PlantPack, Crops and Wood and Stone.

This thread is aiming at the assets itself (like "here they are, I don't know what you'll do with them, but maybe they'll be usefull") instead of how assets depend and extend each other - this question is topic of another thread!
Basically, the problem to discuss is how general modules should be and which resources should belong to the scope of a single module. The use case this discussion is build around involves the modules PlantPack, Crops and Wood and Stone.
- Crops - this module does nothing else but defines several crops and its growth stages; there are now items or any other "products" of the crops in this module
- PlantPack - assembles a bunch of plant definition and growth cycle implementations; this module contains items (as drops of crops), e.g. corn cob or panicles of rice
- WoodAndStone - the "final" module, which has a dependency on PlantPack; this module adds further "processed" items, such as grains of rice or corn flour
- all the items/blocks are spread across several modules; it may get complicated to get an overview of "what is where"
- the set of corn resources is hard to reuse; other modules either need to copy files, add dependencies on PlantPack or even WaS or create new assets
- if we split up assets, what should stay together? why are crop stages together in one module, maybe I just need the last one, why are corn cob and flour separated again, ...
- no unnecessary assets are present; the current setup does not have "unused" items from one module dependency to another