I agree. I think we should create this list manually, after we review plugins and allow a "here are really good ones people have been using for a while and proved themselves stable and useful" list. On Wed, Feb 2, 2011 at 12:30 PM, David Precious <davidp@preshweb.co.uk>wrote:
On Wed, 2011-02-02 at 10:45 +0100, damien krotkine wrote:
it would be cool to get the list from CPAN, and try to link them with github. For example, you search all Dancer::Plugin::* on cpan, for instance Dancer::Plugin::FlashMessage. You would then try to search for dancer-plugin-flashmessage or other variants on github. Some modules also point to a repository URL in the meta files (I do that for my modules).
I'm not sure whether it ought to be automatically generated, or a manually-generated list, with the plugins we find to be of most interest listed first; ideally we want people to look at this page and see all the things they're most likely to want to do with Dancer listed first, and realise there's a plugin for all the stuff they need.
If we automatically generate it, they're likely to have to read further through a list to see what's of interest to them.
We can also ensure each module gets a well-written description of what it does, so it's clear.
Basically, qx(pod2html Dancer::Plugins) would be a good start, since we already have that :)
Cheers
Dave P
-- David Precious <davidp@preshweb.co.uk> ("bigpresh") http://www.preshweb.co.uk/
_______________________________________________ Dancer-users mailing list Dancer-users@perldancer.org http://www.backup-manager.org/cgi-bin/listinfo/dancer-users