1 Suggestions of ideas for plugins:
3 * list of registered users - tricky because it sorta calls for a way to rebuild the page when a new user is registered. Might be better as a cgi?
4 > At best, this could only show the users who have logged in, not all
5 > permitted by the current auth plugin(s). HTTP auth would need
6 > web-server-specific code to list all users, and openid can't feasibly do so
7 > at all. --[[JoshTriplett]]
9 * It would be nice to be able to have a button to show "Differences" (or
10 "Show Diff") when editing a page. Is that an option that can be enabled?
13 * For PlaceWiki I want to be able to do some custom plugins, including one
14 that links together subpages about the same place created by different
15 users. This seems to call for a plugin that applies to every page w/o any
16 specific marker being used, and pre-or-post-processes the full page
17 content. It also needs to update pages when related pages are added,
18 so it needs to register dependencies pre-emptively between pages,
19 or something. It's possible that this is a special case of backlinks and
20 is best implemented by making backlinks a plugin somehow. --[[Joey]]
22 * random page (cgi plugin; how to link to it easily?)
24 * How about an event calendar. Events could be sub-pages with an embedded
25 code to detail recurrance and/or event date/time
27 * 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.)
29 * asciidoc or txt2tags format plugins
31 Should be quite easy to write, the otl plugin is a good example of a
34 >>Isn't there a conflict between ikiwiki using \[\[ \]\] and asciidoc using the same?
35 >>There is a start of an asciidoc plugin at <http://www.mail-archive.com/asciidoc-discuss@metaperl.com/msg00120.html>
38 * manpage plugin: convert **"ls(1)"** style content into Markdown like **\[ls(1)\]\(http://example.org/man.cgi?name=ls§=1\)** or into HTML directly.
40 > With a full installation of groff available, man offers HTML output. Might
41 > take some fiddling to make it fit into the ikiwiki templates, and you might
42 > or might not want to convert pages in the SEE ALSO as
43 > well. --[[JoshTriplett]]
45 * As I couldn't find another place to ask, I'll try here. I would like to install some contributed plugins, but can not find anywhere to downlod them.
47 > Not sure what you mean, the [[plugins/contrib]] page lists contributed plugins, and each of their pages tells where to download the plugin from.. --[[Joey]]
49 * I wrote a very crude wrapper around tex4ht to render TeX files. I hesitate to give it a contrib/plugins page in its current state, but if someone wants to play, [here](http://www.cs.unb.ca/~bremner/wiki/software/ikiwiki/tex4ht.pm) it is.--[[DavidBremner]]
51 * Setting default values for the meta plugin in the setup file, particularly author, license, and copyright, would be useful
52 There is work in progress at
53 [[plugins/contrib/default_content_for___42__copyright__42___and___42__license__42__]]
56 * Would it make sense to have a hook to set the page name? This would solve a problem I see with
57 [[source_code_highlighting|plugins/contrib/sourcehighlight]]