Suggestion: Section for user-submitted use-cases or implementations

Apologies if this is the wrong issue queue -- I'm not a regular in this neck of the woods :)

I think we all know that most of the skill in setting up a drupal site is knowing which modules can do what. It's one thing to read the description of a module, but it often takes an install, or an in-depth tutorial to learn what a given module is actually capable of. This is particularly evident as configuration gurus find new and interesting ways to use modules, and these emergent uses sometimes surprise even the module maintainer, who couldn't have imagined that particular implementation.

While it's true that module maintainers are sometimes kind enough to supply a description section dedicated to when/how their module can be used. This is well-and-fine, but for the reasons stated above, this doesn't always do a module justice -- that's only one person's off-the-cuff ideas.

As it stands, the only way to get an idea of what a module is capable of is to read scattered case-studies and tutorials, or even install the module and try mixing and matching it with others. This doesn't seem to be the best way to learn this important info. For example, case-studies are not easily filterable by which modules they discuss, so you can't easily find a case-study that will give insight into a particular module that you're interested in.

My suggestion would be to add a section to the project pages where users could easily submit a quick explanation of a novel use they've found for a given module. It would be a similar format to the upcoming "review" functionality. Not everyone is going to write a case-study, but this would encourage users to share their experiences in an organized fashion.

I would imagine that there could be a textarea for the general description, and there might also be a field to list all the complementary modules that were used (noderef?), as well as a link to the site where the functionality is domonstrated, if available. Using a noderef to list complementary modules would have the added benefit of being able to show an implementation on THOSE project pages as well, and the user wouldn't have to write one of these mini-case-studies for each module.

Any thoughts on this? I know we don't want to pollute the project page with features, but it would really help to have a centralized way for module users to share experiences and ideas -- one in which use-cases are focused on the modules themselves, and not the website on which they're used.

Thanks for hearing me out, and apologies about the length :)