First off, thanks to the team for creating such an excellent wiki. I spent a lot of time sampling different programs and I chose this one because it seemed to be a great all-around tool plus easily extensible... which leads me to my next point. :)

After pushing for months, I finally convinced my office to use a wiki for design and documentation collaboration. After 24 hours of setting it up, 50+ pages were created by various members of the team. Not bad, if I do say so myself. Nevertheless, already I have gotten feedback on some things that they wish could be implemented in order to make their lives easier and to help increase the enthusiasm across the office.

I haven't really looked too deep yet into these issues. I would like to work on these and contribute code but in the meantime, I just want to jot the notes down here and make them public while I am at work doing paid labor. :) I'll formalize them into the SuggestionBox or plugin requests later.


System Setup:

Open Issues:

Thank you for pointing out my cultural insensitivity. :-) You're right, the issue of plurals is language specific, however, why not implement aliases instead?
OldWitch OldWitches,EvilWitch,EvilWitches
GreyWolf GreyWolves,GrayWolf,GrayWolves,DarkWolf,DarkWolves

Anytime one of the WikiWords in the right column is used, it points to the page specified by the WikiWord in the left column?

I'm sorry, the order LargeDomain/SmallDomain/Page is what I was trying to express. Wacko is doing exactly what I want.

It seems like this should be pretty easy to implement in Wikka. You keep the page table the same except add a column that stores a namespace string. Then you set up Mod_Rewrite to break up the url into three parts:
http://localhost /cluster/subdomain1/subsubdomain2 /WikiWord

You use regexp to get the domain and the page and whatever is left becomes the namespace string. Then you query for the page that has that name except also has that specific namespace string.

The only problem with this is that I don't know what current functionality this would break i.e. Handlers.

I'm using Wikka in the office primarily as a design doc system. However, since we develop software, often times we need to refer to classes of code we write in our design docs. Right now, we are using Doxygen for our CPlusPlus code. Now say for example we have the following CPlusPlus classes:


As you can see, the moment I type those words, Wikka turns them into WikiWords and tries to reference them as pages from within the wiki. What I would like to do is specify a list of reserved WikiWords into Wikka which means that whenever that WikiWord is found, it won't build a link to a page within the Wiki. It may instead link to another domain, specifically, the url of the Doxygen page for the documenation for that class. I want to avoid having to use the syntax for building outside links or InterWiki links because I don't want that specific page to exist in Wikka. I want to override the default behavior of some WikiWords to point to something else. Does that make sense?

I actually have an idea for this but I want to finish my other extension so that I don't have too many open issues. I don't think there is need for an external template system, Nick, as after all, Wikka is basically rendering every page according to certain rules. We would just need to create a subset of that.

You know how when you are editing a page, at the bottom, it asks you to "Please add a note on your edit."? Say I spend 10 minutes writing up a major section to a page, when I am finished, I add the note "added Widget X to Documentation" and store the page. 30 seconds later, because I was dumb and didn't preview, I notice a typo and re-edit the page in order to fix it. When I look at the bottom, the "Please add a note on your edit" box is blank. If I just hit the submit button, then the page gets stored and when I go to RecentChanges, the original edit note is gone. This should have a memory feature so I don't have to rewrite the note "added Widget X to Documentation" just because I needed to fix a typo 30 seconds later. Does that make sense?

Annoyances To-do:


Key: Blue indicates extensions deployed, Red indicates extensions I want to use but with different behavior, Green indicates extensions I've created.

There are 7 comments on this page. [Show comments]
Valid XHTML :: Valid CSS: :: Powered by WikkaWiki