X-Git-Url: http://git.vanrenterghem.biz/git.ikiwiki.info.git/blobdiff_plain/e6de0cfa62630a16e7c666cf6f603534b6f6e568..df22dd5cbdb50f5686d15af7d288de05c4629029:/doc/plugins/discussion.mdwn diff --git a/doc/plugins/discussion.mdwn b/doc/plugins/discussion.mdwn index 21d2659a3..70157f1e2 100644 --- a/doc/plugins/discussion.mdwn +++ b/doc/plugins/discussion.mdwn @@ -4,8 +4,42 @@ I have seen a few requests on discussion pages, but not any place specific I thi --JeremyReed -Some requests: +> [[todo/plugin]] has a list of stuff, moved yours there. --[[Joey]] -- rcs plugin ([[JeremyReed]] has one he has been using for over a month with over 850 web commits with 13 users with over ten commits each.) +It would be nice if the page gave a brief synopsis for each plugin. For example: + +>headinganchors +>Adds IDs to all headings based on their text. +>Posted Thu, 09 Aug 2007 02:34:19 -0400 + +>pagetemplate +>Inserts page text into chosen template with the template controlling the look and feel. +>Posted Thu, 26 Jul 2007 16:50:58 -0400 + +>graphviz +>Allows embedding of graphviz graphs. +>Posted Mon, 09 Apr 2007 05:09:04 -0400 + +--MichaelRasmussen + +Any objections to listing plugins alphabetically rather than by creation date? (i.e. change the inline to have sort="title".) + +-- Will + +> Well, it's been done by Josh, but I do wonder if there wasn't value to +> being able to look at the top of the page for new plugins? --[[Joey]] + +>> I agree, which is why I brought it up here rather than just changing it. +>> On balance I think the alphabetical list is better. You could have a +>> "recently changed" list with the 10 most recently changed plugins +>> at the top. That would allow what you suggested, but still allow +>> the main list to be alphabetical. -- [[Will]] + +How about adding a deprecated tag in order to clean up the plugin list? + +> AFAIK it's currently the only one. --[[Joey]] + +For instance [[googlecalendar]] is listed as plugin but should probably be removed from Ikiwiki in a future major version (v3?). + +-- [[AlexandreDupas]] -- manpage plugin: convert **"ls(1)"** style content into Markdown like **\[ls(1)\]\(http://example.org/man.cgi?name=ls§=1\)** or into HTML directly. \ No newline at end of file