Re: Wiki lock-in?
> I'm concerned that I'll spend a lot of time and effort building a wiki, only to discover
> that I really should have been using some other wiki, or some other methodology. For
> example, if I had decided to build my documentation as ordinary html, I have my choice
> of hundreds of different editor and management tools.
>
> So my question is, what's the wiki (and Tiki in particular) world's answer to this conundrum?
> >
> > I want to replace the menu with a regular page-- In my "menu page" I can then easily create links to the rest of my wiki pgs.
> >
> > Anyone have thoughts on how to do this.
> >
My first question would be.... Why do you want/need a wiki? The wiki "methodology" is based on several assumptions:
- You want to have multiple contributors
- You want to use a simplified syntax
- You want users to edit pages using nothing more than their browser
- etc.
My second question would be.... Why choose Tiki as your wiki-based solution?
(This one I can answer....) Remember that Tiki is much more than simply a wiki.
My third quesiton would be.... What types of "documentation" are you going to deliver? Is his something that will change often? Do you want to allow visitors to read/upadate/comment the pages? Do you want different levels of access?
HTH,
-Rick
Now Available: TikiWiki for Dummies Smarties — A beginner's guide to using ))TikiWiki((.