Revision [20165]
This is an old revision of TechnicalWriting made by TechnicalWriting on 2008-08-30 12:08:27.
Good Traits
* It is fast
* Has many features
* Has a mailing list
* Has graphics and audio functions
* Easy to install
Bad Traits
* Hard to Navigate
* Layout is not organized
* Some of the main links do not work
* It is still being developed so the format could change at any time
* The code is very hackable
* The site is also not ascetically appealing
* The very fact that this must be installed is a turnoff since others do not need to be
* Making a username is not easy "Username must be formatted as a WikiName"
Questions
* Is this site appealing to the eye? No, the layout is very unorganized. Many of the links are embedded into the pages which makes it difficult to navigate.
* How easy it is to use/register/surf? Not very easy. You have to search for the link to register, which is embedded into the page.
* How effective is the site in providing information? It is informational.
* Is the content organized throughout the wiki? It is not organized at all. It seems to be in no particular order and is scrambled. It is very difficult to remember where anything is.
Some general notes...(taken directly out of context from user reviews)
Features that make Wikka Wiki a winner://////
* RSS feeds. Suppose you like to write on the web, but hate the reverse-chronology shackles of weblog software. On the other hand, you want people to be able to read your most recent scribbling as you publish it. An RSS enabled wiki allows the freedom of a wiki and the syndication of a weblog.
* Flexibility∞. Okay, technically a wiki should be open to everyone to read, write, and edit. But what if you want to keep out the Anonymous Cowards who like to drop by and take a dump in your space? Wikka wiki allows some flexibility in who can play in your sandbox.
* Comments∞. So you want the wiki to be an intertwingling of your own making, but you want others to be able to drop by and point out your more obvious warts. Wikka wiki has comments built in.
* Over-powered∞. Doug Miller commented the other night that MySQL seem to be overkill when it came to running a wiki, and that something like SQlite would be a-plenty. Too true. But the nice thing about over-engineering a product means that it has room to breath and grow. Not satisfied with the current feature set? No worries, pet.
(Many users compare WikkaWiki to MediaWiki, claiming it to contain a lot less "fluff" and more functional tools.)
"I have found that the RSSfacilities built into Wikka Wakka Wiki is really useful!"
"It has all the features that I wanted without feeling like it is bloated like MediaWiki"
"[M]y first wiki was MediaWiki, and I just decided it was.. 'too much'. I wanted something that was easier, cleaner interface, and where new users with something to say would be more likely to add content and ended up with WikkaWiki (Jason Rahaim∞)"
"Wikka is an Wiki written in PHP with some great features:
PHP and MYSQL make it lightweight and fast. (Okay so that’s propaganda from the website but it really is great.)
Page level security so you can determine which pages can be viewed and edited by others.
Like other Wikis it uses the CamelCase syntax for links to other pages but it also has some neat tricks for creating elements like lists, horizontal bars, etc.
Its functionality can be extended using plugins called actions. People have written actions to display rss feeds and calendars among others."
