@cshoredaniel I am a little late to the topic, but thanks for pinging me! In general, I’ve thought about something similar.
In my little spare time, I am working on establishing a community around Hugo modules that actively develops and maintains them, going by the simple name hugo-mods. Initially, I only needed a namespace to organize my Hugo modules, but I intend to take this further.
Here the goal is also not to provide hundreds of modules that are just a wrapper around a specific dependency but instead to create user-friendly solutions for common problems (already covering some of the use-cases @schnerring mentioned). Two exemplary modules that work this way I’ve introduced here a while ago:
- GitHub - hugo-mods/lazyimg: Lazy image loading with superpowers
- GitHub - hugo-mods/icons: A Hugo icon system module that scales.
Many of the modules are still in development, and I’m drafting guidelines that help with engineering them throughout the whole lifecycle (w.r.t. project structure, config, testing, preview etc.) to ensure quality.
I’ll probably introduce this whole thing here properly in the next months, when I consider a good base of modules as stable, meant to be used in production.
That being said, I’ve recently had a lot of fun with the modules by creating a first version of the hugo-mods homepage, for which I’m using a theme that I’m currently heavily modularizing.
In the meantime, feel free to reach out if you have any feedback, like the idea or want to become a contributor!