Ok. I found out, that I’ve got some more things to say while using twitter, switching my work place, developing in Zimbra etc. So I needed a new Blog and after fiddling with Dokuwiki’s „old“ blog-plugin and failing again and again, I decided to give the (currently experimental) blog plugin a go.
What I dislike about it:
* Why is a database suddenly something good? Dokuwiki has been used filesystem magic for decades and now the blog metadata has to be stored into a database? After all, it’s SQLite, so I don’t need to tune for days, what most other databases require before proper use.
* Why is there no „add new blog“ button in the admin area? Hmm… I have to manually copy the template files to create a new blog? I don’t like that. But, perhaps it’s about the „experimental“ thing. So I guess I’ll have to wait…
What I like:
* It seems to work well and has (that’s a main advantage over the old plugin) a working rss feed for the pages. (But it was perhaps me, who didn’t know, how to configure or use the old plugin properly… could be)
* The additional edit form is nice. I can concentrate on writing the blog entry and all metadata isn’t stored into the page’s sourcecode.
* Andi Gohr is working on it. Andi’s a great developer from what I have experienced until now. And if the main Dokuwiki developer is working on the plugin and using it himself, I see a bright future.
Why I simply don’t use <>? I’m a Dokuwiki addict, I admit it. I like the whole concept and the power of Dokuwiki. And I’m using it to build my whole websites. Why should I embed an external application if the blog plugin can handle the main tasks?
As you can see, I’m no professional blogger. So I won’t use any special blog abilities of other, better engines.