| Random Page
Which wikis are the most easily extensible today by their users? (a SelfProgrammingWiki
would be an extreme special case). The mark of a SelfProgrammingWiki
is that the wiki software itself may be modified. A merely extensible wiki means just that users can write additional software on the wiki that can be run, not necessarily that they can modify the wiki software (i.e. a Wiki:WikiWithProgrammableContent
). In this case the most extendable ones are the ones that allow the embedded scripts to access information about the Wiki beyond the current page; i.e. i believe that in SeedWiki
s are implemented as a script.
See also WikiPlugins.
Wiki:WikiWithProgrammableContents that are not SelfProgrammingWikis:
(at the moment, my descriptions of these are hearsay, I haven't seen the embedded code for them myself; question: which of these would allow something like BackLinks to be reasonably embedded?)
- SeedWiki will accept Active Server Pages (ASP) code "widgets" from users that you can then embed in a page
- Can this code access information about other pages in the Wiki?
- [Torge's Wiki] extends the system for security
- ZwikiClone allows embedded DHTML and limited python code. The recent changes and jumpsearch pages are implemented this way.
- MoinMoin allows to use XML and XSLT, and custom macros, parsers, directives and actions. Written in Python
- OpenWiki Very similar to MoinMoin in design. Allows to use XML and XSLT, and custom macros, parsers, directives and actions. Written in ASP.
- [Kehei] allows you to issue commands (to the wiki??) in the middle of your pages. (seems to be a broken link Mar.25.2004)
- OddMuse allows you to have a config page.
- The page acts like a config file: On that page you can place additional code to be executed by the script. The page is only createable by administrators. The "Safe" module is not used, therefore using this feature is a potential security risk. For an example, see EmacsWiki:Config and EmacsWiki:ConfigFr for an example of some uses for the config page. Basically it does not DevolvePower, and it does not really speed up development, since you cannot use the config page to significantly change the wiki. All it does is allow more powerful remote maintenance for administrators that don't always have access to the config file.
A related question is, which wikis are most easily extensible today by their proprietors? i.e. which are most modular, easiest to develop on, or to find and apply modules/patches for?
list here is duplicate content with Wiki:SmartWikis
; I duplicated it here because I've heard that WikiWiki
doesn't want continuing Wiki:WikiOnWiki