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.
>> It would be nice if the plugins had their own page on the website. webpages. charter. net/edreamleo/ plugins. html
>
> Technically, this bug is invalid. Plugins already have a page:
> http://
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/ reinterpretatio n of the feature request.
-matt