chiq_chaq is a wiki derivative which is geared towards being very easy to install, use, internationalise and customise. http://chiqchaq.sourceforge.net/
I used this prior to discovering MiniWiki, and there are certain things about it that I love, particularly in the ease-of-use and the fact that it has a pretty box for adding at the bottom of every screen. But there is as yet no access control to allow some people to edit and others to add, it's all or nothing. There are other niceties like auto-emoticons and a good range of formatting options.
I'm looking to steal the add box, and some other features, and integrate them into MiniWiki because the latter is so clean and fast. I hope it can be done without making it dirty and slow :-)
jammin, you should find MiniWiki pretty easy to customize, as you can edit the template using MiniWiki itself. On this Nyetwork wiki, I've kept out all browser-specific things, so it's fast loading and works in almost any web browser (well, telnet would be painful).
I find it pretty easy to add new pages... just edit the page, add the link, save, then hit the ? mark to the new page. Simple, and works in 99.9% of the cases.
I just released MiniWiki 0.8 to CPAN, so it should show up in the mirrors soon. An update might come out soon, since after I released that I added an optimization for the thumbnailing.
Actual code for MiniWiki is still under 1000 lines (plus comments/docs). One of the main reasons for this is that much of the text->html conversion and handling of revisions and storage is done by CPAN modules like HTML::FromText, Image::Magick, and the RCS.pm module.
To clarify, what I meant by adding was not creating new pages (any Wiki can do that) but a box on every screen which adds a nicely-boxed comment to the bottom of the existing page, without having to edit the whole text. I see this as enhancing both ease-of-use and the range of deployment. For instance if combined with an authentication system, one might allow anybody to add to pages (without being able to edit their existing content) and only administrators to edit them directly. Most hardcore Wikians would see this as contrary to the Spirit of Wiki, but I live in the real world where if you give people enough rope to hang themselves, they will.
Highlevel/granular access controls like that are getting pretty complicated, and not simple/mini anymore. You'd also need to figure out where to store comments... in seperate text files in RCS? What about editting those comments? Use an SQL database? Feel free to add them, but there's no way I'd turn them on here... it's worked quite well so far...
Sure, I see my developments as taking a different path to MiniWiki. Maybe I'll call it MaxiWiki :-) or MetroWiki...
I don't really understand "blog features" (or blogs generally), I just think of it as being like a BBS. Added comments get inserted into the page, but they're not stored in a database, and the moderator still just hits Edit to edit the whole page if you need to change something in a comment -- but the idea is that ordinary/anonymous users can't modify what other people have said. It has a different aim and uses than a regular wiki.
jammin, "But there is as yet no access control to allow some people to edit and others to add, it's all or nothing". e-mail guy at ootips dot org
he wrote something that allows access to a lecturer to change, and to students to read. Not yet published in open source sites, but deployed in the Tel-Hay collage.
BTW, chiq_chaq is now quite compatible with Mozila, both on Mac and Linux. and every version of chiq_chaq comes with a bunch of brand new cool featurs.