Why Zomplog?
There are many good weblog-systems around, why create yet another one? I've worked with many of the major weblog-systems around, and noticed they had a few flaws in common:
- They required a lot of technical knowledge from users
- They had too many bells and whistles that confused users into thinking it was something difficult they were doing.
- Their interface wasn't logical (why upload a picture in a completely different part of the site, if you're gonna need it for creating a weblog-entry?)
- They were ugly!
My aim with Zomplog was to create a simple weblog-script that was easy to install and use, even for people without any technical knowledge. A script that would work out-of-the-box, and would not require users to wade through endless instruction-files before they could do their first posting. I feel that anyone should be able to benefit from new technical possibilities, and thus tried to make Zomplog as easy and intuïtive as possible. Well, even my mom uses Zomplog now. So I guess I've reached my aim :)
Another problem I regularly came across is that open-source programmers are no graphical designers. Open-source scripts and systems might work fine, but they're often not really attractive to the eye (to say the least). Wouldn't it be much more fun to work with systems that are beautiful as well? Isn't that a vital part of the way we appreciate the things we see and work with?The open-source movement needs graphical designers! That was another aim I had with this script: make it something that's just attractive to look at!
