Given that every user has a personal favourite which might not apply to other users it seems logical that over time "all" modules would have to be included in the list.

Because for any given module $foo there is almost certainly a user or two who believe that is the world's best module!

For that reason above all I think that such a list wouldn't be as useful as you'd imagine:

• 20,000 people will enter DBI.
• 10,001 HTML::Template
• 10,000 Template::Toolkit
• and then 100 people each entering a distinct module!

What I would suggest is twofold:

1. Add a rating to the module review section and use that in preference to a new section.

2. When you say you don't have time to keep up with CPAN that is reasonable (and common!) but I think it is almost mandatory to have a quick look when working with a new area.

Taking you as an example you say you do mostly "databasey" things. I'd not expect you to look at every type of module available every day, but I would imagine that you would have a quick look if you wished to start workgin with say CVS code.

Does that make sense? Having the "best module" cover some modules for working with CVS servers might stick in your mind, but I'm sure that people who know of CPAN and are working on a new area would be liable to search there first, even if they weren't sure of what was available.