plugins could have pages on the website

[Matt Wilkie]

It would be nice if the plugins had their own page on the website. A simple(?) way of doing this might be to pull each one's docstring as it's page, which would be linked to from the main Plugin directory page.

So for example the Viewrendered section, http://webpages.charter.net/edreamleo/plugins.html?highlight=viewrendered#viewrendered-py, has a mini description, and a [more info] link to http://webpages.charter.net/edreamleo/plugins/viewrendered.html

[Edward K. Ream (edreamleo)]

On Thu, Oct 13, 2011 at 5:49 PM, Matt Wilkie <email address hidden> wrote:
> Public bug reported:
>
> It would be nice if the plugins had their own page on the website.

Technically, this bug is invalid. Plugins already have a page:
http://webpages.charter.net/edreamleo/plugins.html

However, I'll leave it open to remind us that more work is needed in this area.

> A
> simple(?) way of doing this might be to pull each one's docstring as
> it's page, which would be linked to from the main Plugin directory page.

Iirc, this is how the page got created. But we need a better way of
ensuring that the page is updated to reflect the latest docstrings.

Edward

[Matt Wilkie (maphew)]

>> It would be nice if the plugins had their own page on the website.
>
> Technically, this bug is invalid.  Plugins already have a page:
> http://webpages.charter.net/edreamleo/plugins.html

I meant to say a page for /each/ plugin, or at least the ones that
have extensive notes like viewrendered. Plugins.html would get
overwhelmingly long with them all on one page.

> However, I'll leave it open to remind us that more work is needed in
> this area ... [we] need a better way of ensuring that the page is
> updated to reflect the latest docstrings.

I'm happy with that addition/reinterpretation of the feature request.

-matt

[Edward K. Ream (edreamleo)]

On Fri, Oct 14, 2011 at 1:19 PM, Matt Wilkie <email address hidden> wrote:
>>> It would be nice if the plugins had their own page on the website.

> I meant to say a page for /each/ plugin, or at least the ones that
> have extensive notes like viewrendered. Plugins.html would get
> overwhelmingly long with them all on one page.

Sure, but let's not call such things bugs :-)

Edward