Hello,
 
I have installed FlexWiki 1.8 (which btw seems to run perfectly under
framework 2.0) with the intention of using it as an Intranet knowledge
store. The data I plan to store in the wiki will be support information/How
to/documentation for each software application that my company runs
internally.
 
Due to this it seemed to make sense for me to create a Wiki Namespace for
each application. That way I would have good logical separation of the data,
plus the ability to have pages with the same name for each application.
 
After setting up a few test Namespaces the first thing I did was to add some
WikiTalk to the wiki's default homepage, that lists all of the Namespaces in
the Wiki. I thought that this would provide wiki users with a easy link to
each of the Namespaces. Unfortunately it would appear that although the
WikiTalk will happily produce the list of Namespaces, the names do not
become links to the homepage of each Namespace automatically. 
 
So I have two questions, the first is whether I have made a mistake in
creating lots of Namespaces. Should I just have one Namespace and use some
kind of page property to divide the applications?
 
Secondly, is there some way that FlexWiki can automatically link to topics
in another Namespace?
 
thanks
Ben


________________________________________________________________________
This email has been scanned for all known viruses by the MessageLabs Email 
Security Service and the Macro 4 plc internal virus protection system.
________________________________________________________________________
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/
_______________________________________________
Flexwiki-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/flexwiki-users

Reply via email to