Tuesday, October 25. 2005
Review: Dokuwiki
I'm Wiki Crazy. Everyone knows that.
For those that don't know what a wiki is (which rock have you been living under) Wikipedia will explain all.
So now, it is time to review some wiki software: DokuWiki. I've installed some wikis in my time. Some of them were okay, some of them were good, and lots of them were CRAP. Until I met DokuWiki, MediaWiki (the software that runs Wikipedia) was my all time favourite.
Was.
DokuWiki however is overtaking MediaWiki. DokuWiki is like MediaWikis faster cuter cousin. Installation isn't too difficult at all. About the hardest thing you need to do is make a few directories webserver writable.
The reason why a wiki does its thing so well is that it takes simple text, and transforms it into HTML, which, if you don't know, is the stuff that makes the web go.
Basically it lets you turn something like this:
DokuWiki also has a good selection of plugins to extend what kind of syntax you can have in your wiki. This goes from the simple (plugins for displaying the date according to the users region) to the massively complex (a blog plugin, so that you can use your wiki like a blog). Programmers can easily write their own plugins, and the plugin API is pretty well designed.
There is also the option of adding different media types to DokuWiki, such as images, PDFs, and pretty much anything else you could imagine. This setup doesn't seem as powerful as MediaWiki's handling of ... well... media, but it is easy to use and elegant.
And unlike lots of other PHP projects, the directory structure is laid out properly. For most people this really isn't an issue, but as a programmer I respect the level of organization and detail. Another big plus is that it uses the PHP native templating engine. Which is to say, the writers of the software use PHP the way it is designed to be used, instead of writing (or using) massively complex parsing engines to display some HTML.
The code quality of DokuWiki is good. The code is done up so that there is no newline between braces, which I find annoying, but that is just a question of style. The code itself is well commented, both for each function and inline. I think that the variable names and function names could be a little clearer, and a little more modular, but the programmer at least knows what refactoring is.
So the verdict is... if you need a wiki installed, DokuWiki is the one.
Update: I linked up Dokuwiki. Duh. I also added my own wiki at wiki.jonnay.net.
For those that don't know what a wiki is (which rock have you been living under) Wikipedia will explain all.
So now, it is time to review some wiki software: DokuWiki. I've installed some wikis in my time. Some of them were okay, some of them were good, and lots of them were CRAP. Until I met DokuWiki, MediaWiki (the software that runs Wikipedia) was my all time favourite.
Was.
DokuWiki however is overtaking MediaWiki. DokuWiki is like MediaWikis faster cuter cousin. Installation isn't too difficult at all. About the hardest thing you need to do is make a few directories webserver writable.
The reason why a wiki does its thing so well is that it takes simple text, and transforms it into HTML, which, if you don't know, is the stuff that makes the web go.
Basically it lets you turn something like this:
== A big Titleinto this:
This is some normal, **bold**, //italic// text
This conversion from somewhat normal text into the cryptic goblety-gook of HTML is what makes a wiki so good. This somewhat-normal-text is called "Wiki Markup" Hell, I know HTML like the back of me hand, but I still prefer using good Wiki Markup instead. DokuWiki has absolutely excellent wiki markup. It is simple enough to use, but is remarkably effective.A big Title
This is some normal, bold, italic text
DokuWiki also has a good selection of plugins to extend what kind of syntax you can have in your wiki. This goes from the simple (plugins for displaying the date according to the users region) to the massively complex (a blog plugin, so that you can use your wiki like a blog). Programmers can easily write their own plugins, and the plugin API is pretty well designed.
There is also the option of adding different media types to DokuWiki, such as images, PDFs, and pretty much anything else you could imagine. This setup doesn't seem as powerful as MediaWiki's handling of ... well... media, but it is easy to use and elegant.
And unlike lots of other PHP projects, the directory structure is laid out properly. For most people this really isn't an issue, but as a programmer I respect the level of organization and detail. Another big plus is that it uses the PHP native templating engine. Which is to say, the writers of the software use PHP the way it is designed to be used, instead of writing (or using) massively complex parsing engines to display some HTML.
The code quality of DokuWiki is good. The code is done up so that there is no newline between braces, which I find annoying, but that is just a question of style. The code itself is well commented, both for each function and inline. I think that the variable names and function names could be a little clearer, and a little more modular, but the programmer at least knows what refactoring is.
So the verdict is... if you need a wiki installed, DokuWiki is the one.
Update: I linked up Dokuwiki. Duh. I also added my own wiki at wiki.jonnay.net.
Comments
Display comments as
(Linear | Threaded)
nice writeup. i love too, except there is no built-in category support, and using namespaces is rather confusion for newbies.
I would have to agre with you on namespaces. I view namespaces as wikis within wikis, as you can see on my own wiki http://wiki.jonnay.net; where I have the x0xd0x wiki, and the Bunny wiki.
Category support is there actually. It just has to be used like the C2 wiki, where at the bottom of the page you list the categories, and then have the user click on the page title to view the pages in the category. The backlinks plugin can help with that.
Category support is there actually. It just has to be used like the C2 wiki, where at the bottom of the page you list the categories, and then have the user click on the page title to view the pages in the category. The backlinks plugin can help with that.
hi does anyone know how can edit the code so if a user who is in the edit document screen unintentionally closes the browser (by clicking the X button) a javasciptlike dialog box will appear and warn the user that the document hasn't been saved after editing. Any idea?
Add Comment





Oops. In my last post, I forgot to provide a link to the DokuWiki homepage where you can download the thing. So there you go. If you want to play around with a dokuwiki, I have set one up here. Feel free to go ahead and create pages and generally pl
Tracked: Oct 27, 09:17