Tim Hodson
Hello everyone! I'm in the process of trying out Wakka wiki. My initial findings are:
- It is a lot faster than usemod, which I currently run for internal purposes
- It's a bit prettier too, generally, although I defined a CSS that worked alright there
- I like having some kind of access control - I may end up merging the two, and having the private one in the same instance.
The biggest problem I've had so far is that I became rather used to the usemod approach of allowing nested pages. These allowed you to define main pages (such as "work") and then child pages ("work/admin", "work/whatever") - and link to them just with "/admin" etc from the work page. Such "namespaces" felt like they made it easier to cover lots of different topics without having to have really silly long names. Any thoughts, anyone?
Another issue - albeit not exactly really serious - is the way that the markup for headings seems to my way of thinking to be "backwards". For most documents I think in terms of heading 1, heading 2 and so on rather than size 5, size 4. It would seem more sensible for me to have the markup for the biggest heading to be, say, =Heading 1=, then ==Smaller Heading 2== etc, rather than starting with 5 equals. It's a structure vs presentation issue, for me: do I think "heading 1" or "very big"?
On the whole, though, I've been getting on very well with this wiki.
If you're sad enough to be interested, my personal wiki lives temporarily at: http://jezreel.dyndns.org/Wikka/wikka.php - not a lot to see there right now, though, with no hugely imminent plans for world domination there either.
CategoryUsers
Well, Wikka definitely doesn't have namespaces.
That said, and not knowing how usemod works ... how is "work/whatever" not a really silly long name while WorkWhatever would be? Sounds like just a naming convention to me, but maybe I misunderstand what usemod really is doing.
You may also be interested in OnegWR's Tree (http://wikka.jsnx.com/OnegWRTree) and Subpages (http://wikka.jsnx.com/OnegWRSubPages ) actions.
Thanks very much for your response, though, and I will look in to those links shortly too.
re: "grown fond of them as a way of reducing the number of top-level pages"
I tend to think of a wiki as a hyperlinked *network* rather than a hierarchy - so "top-level" really doesn't come into it in terms of *pages*.
However, Wikka has a *category* system that serves as its main organizer (apart from links on actual pages - your home page is very important in providing access to your site's content). Maybe you should play a bit with categories as well - they *can* form a hierarchy and the top level comes installed as the CategoryCategory page. The advantage is that a page can be in multiple categories - providing an organization that is not possible with a strict hierarchical page relationships.
Now I shall look at the other two actions you referred to!
Yes. You could try that out if you add CategoryUsers to your page :)
>From the WikiCategory page I wondered whether there would be some sort of automatic hierarchy generation, but I think I must have misunderstood the WikiCategory page.
There is no generation of any hierarchy. so users can feel free to create their own. I tried to make the explanation on WikiCategory clearer but you can help if you tell what especially is unclear (and by correcting typos, thx for that :)
The WikiCategory page on this site seems fine to me; perhaps this should be included as the default version for new installations?