Some financial portals (editors are, well, real editors).
Collaborative fiction sites
A major national software development magazine
Features for editors:
[X] easy to write (and powerful) wiki formatting rules,
[X] WYSIWYG capabilities in addition to wiki formatting,
[X] HTML allowed but not required,
[X] unlimited number of namespaces,
[X] change log per page or per namespace,
[X] easy to roll back to earlier versions,
[X] file upload,
[X] insert image
[X] page can specify its own skin/template (very unusual)
[X] editors can edit skin (advanced)
[X] can designate who else may edit
[X] author copyrights preserved
[X] ghost writers permitted
[X] limit sections to certain subscribers or roles
[X] auto sign & date
[X] sign-up sheets to public
[X] self-appending form pages, i.e., blog format possible on per page basis
[X] page templates
[X] configurable markup
[X] glossary-with namespace serach-path
Features for readers:
[X] mnemonic bookmarks,
[X] table of contents,
[X] regex searches from URL,
[X] canned searches,
[X] search results savable with annotations,
[X] navigation bar (aka "breadcrumbs"),
[X] printer friendly version for all pages.
[X] user personal pages,
[X] user preferences
[X] namespace preferences
[X] provisional page locking
[X] blog pages
[X] message system.
Access controls. [Yes - very advanced]
[X] read-only subscriber groups
[X] lots of roles definable:
cover art artist
multiple subscriber classes
any or all of the above
same user can take on multiple roles
invent your own roles
[X] page specific editors by name, role or both
[X] namespace specific editors
[X] supports delegation, hats, roles and apprenticeships
[X] separate skin per subscriber group
[X] home page,
[X] main/browse page,
[X] editor page,
[X] nothing written yet page,
[X] you-are-here navigation (breadcrumbs),
[X] multiple skins
All diagnostic messages come from html templates.
Selection of templates set can be by domain name.
Classic installer runs itself from browser in about 30 seconds.
Specifically designed for ISP/hosted installs.
Can go in a subdirectory.
Maintenance: [Core, modules, templates, extensions and user content all separately upgradeable]
Multiple extension APIs.
Can add additional markup.
Can add support CGIs.
Will wrap CGIs in skin.
Extensions don't have to be in Perl.
Are you locked into a particular package or wikitext format?[No]
Is it possible to export your text to other systems?[Yes]
Scalability: Is it suitable for large amount of pages? [Yes]
Most scalable wiki software needs a back end database to store pages.
[Kehei Wiki has been adapted to database on portal sites but does not require database]