Suggestions of ideas for plugins:

* enable editable, non-htmlized files

    Some months ago, before upgrading my wiki, I used svn to check in an XML file
    and a companion XSL file for client-side styling. That was cool, ikiwiki
    copied them over unchanged and the file could be linked to as `\[[foo|foo.xml]]`.

    I even had the XSL produce an `Edit` link at the top, because I wanted a simple
    way for a web user to edit the XML. But I had to hack stuff to make the edit CGI
    not say `foo.xml is not an editable page`.

    I did that in a kind of slash-and-burn way, and apparently that's the one change
    that was uncommitted when I upgraded ikiwiki, so now it's in the same place
    as the wikiwyg project. On the bright side, that's a chance to think about how to
    do it better.

    Any suggestions for appropriate uses of existing plugins, or the plugin API,
    to selectively add to the set of files in the working copy that the edit CGI
    will consider editable? --ChapmanFlack 17July2008

* 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?
> At best, this could only show the users who have logged in, not all
> permitted by the current auth plugin(s).  HTTP auth would need
> web-server-specific code to list all users, and openid can't feasibly do so
> at all. --[[JoshTriplett]]

* It would be nice to be able to have a button to show "Differences" (or 
  "Show Diff") when editing a page. Is that an option that can be enabled?
  Using a plugin?

* For PlaceWiki I want to be able to do some custom plugins, including one
  that links together subpages about the same place created by different
  users. This seems to call for a plugin that applies to every page w/o any
  specific marker being used, and pre-or-post-processes the full page
  content. It also needs to update pages when related pages are added,
  so it needs to register dependencies pre-emptively between pages,
  or something. It's possible that this is a special case of backlinks and
  is best implemented by making backlinks a plugin somehow. --[[Joey]]

* random page (cgi plugin; how to link to it easily?)

* How about an event calendar. Events could be sub-pages with an embedded 
  code to detail recurrance and/or event date/time

* 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.)

* asciidoc or txt2tags format plugins

  Should be quite easy to write, the otl plugin is a good example of a
  similar formatter.

>>Isn't there a conflict between ikiwiki using \[\[  \]\] and asciidoc using the same?
>>There is a start of an asciidoc plugin at <http://www.mail-archive.com/asciidoc-discuss@metaperl.com/msg00120.html>
>>-- KarlMW

* manpage plugin: convert **"ls(1)"** style content into Markdown like **\[ls(1)\]\(http://example.org/man.cgi?name=ls&sect=1\)** or into HTML directly.

> With a full installation of groff available, man offers HTML output.  Might
> take some fiddling to make it fit into the ikiwiki templates, and you might
> or might not want to convert pages in the SEE ALSO as
> well. --[[JoshTriplett]]

* 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.

  > 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]]

* 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]]

* Setting default values for the meta plugin in the setup file, particularly author, license, and copyright, would be useful 
There is work in progress at 
[[plugins/contrib/default_content_for___42__copyright__42___and___42__license__42__]]
-- [[DavidBremner]]

* Would it make sense to have a hook to set the page name?  This would solve a problem I see with 
[[source_code_highlighting|plugins/contrib/sourcehighlight]]
-- [[DavidBremner]]