List of plugins needs to be more 'reader-friendly'

[wesley]

The list of plugins shown at s9y's website is quite, uh... hard to read.
You have the name of a plugin, then right after that, the description.
Then without any spacing, there's a description for another plugin. I have
to carefully read the whole thing to see to distinguish one from another.

This is bad.

There should be at least a blank line between the plugins and preferably
the description should be put on the line after the name of the plugin.

So instead of this (which is how it looks):

Babelfish: Translate blog entries (trash!)
Static Pages: Shows static pages inside your blog with your blogs design and all formattings. Adds a new menu item to the admin interface.
Picture of the author: Shows a picture of the author to each entry. The image file must be placed in the "img" Subfolder of your selected template and be called like the authorname. All special characters (quotes, spaces, ...) must be replaced by an "_" inside the filename.
...

It should be like this:

Babelfish
Translate blog entries (trash!)

Static Pages
Shows static pages inside your blog with your blogs design and all formattings. Adds a new menu item to the admin interface.

Picture of the author
Shows a picture of the author to each entry. The image file must be placed in the "img" Subfolder of your selected template and be called like the authorname. All special characters (quotes, spaces, ...) must be replaced by an "_" inside the filename.

...

If the whole thing's done with a script I think it'd be pretty easy to fix it.
Oh, and the description part shouldn't be clickable. Just the name only.

[garvinhicking]

The problem is, this list is auto-generated from the RSS Feeds and is an internal cowiki feature. I don't know how to change that code, and I have to access to the site.

Basically what you need (and what we want) is a pear.php.net like site. Tom Sommer once created http://spartacus.s9y.org/ which is is packet manager interface for the plugins. This is basically, what we want, but no one currently had the time to code it.

Basically the XML information is all there, the Spartacus plugin already uses it. All we need is just another frontend which we put online at this spartacus site. Any volunteers?

Could be much fun to do that with PHP5's XML features...

Regards,
Garvin