So, I have way too much university work still in front of me. One thing is a course that focuses on knowledge representation. Doing this course was my free will, I have to choose two from a bunch of courses. Well, I thought this one is cool, it's simple, so I'll do it. Part of that course is to create a "Hypertext-application". Well, not so bad, I'm TikiDev, hm? Nah, it's not that simple. They have pretty strict rules about usability - what's a good thing imho. But my Tiki does much more than just be a Hypertext Application for some twelve pages(that's the minimum you got to do for that course). I really don't know, how they will react on things like categorization, function menus on the side etc. Generally that's all a good thing, but if they say, that it makes the interface too overloaded, then I got a problem. ;)

So, my plan is to say, that I made a Hypertext Application that is embedded into the TIncubator - and that is the truth actually. The TIncubator is meant to be a bunch of Hypertext Applications not only for representing knowledge, but for creating it collaboratively. /Open .*/ Rock is one of its project (hotbeds) and it got a Hypertext Application of its own. I think I could gain full points for this with a Multi Tiki installation. That would allow me to clean up the interface completely. But let's see what they think of it - since I didn't customize Tiki too heavily, this could be some kind of TU Ilmenau usability certificate for Tiki.. ;)

I'm going to customize the structure browsing of luciash's simple.css, make a How To Use page and then submit it.