Feng Forum
Other Topics => Development => Applications => : conrado June 11, 2007, 01:50:21 PM
-
One of the toughest decisions is what Wiki engine should we begin with.
There are many excellent alternatives. Any choice will mean the sacrifice of the exclusive features the others might have.
After some discussion we came to realize that one very important feature for the selected wiki engine should be the existence of a plugins API or, better yet, known extensions.
Yed suggested that we build both the spreadsheets and the presentation apps over the wiki engine. It is an interesting idea, but one that makes this choice very hard.
What are your thoughts on the subject, and which are your candidates?
-
Check out the list of wikis based on the programming language used:
http://c2.com/cgi/wiki?WikiEngines
Also some more here:
http://c2.com/cgi/wiki?WikiEngineReviewWikiLists
-
Check out the list of wikis based on the programming language used:
http://c2.com/cgi/wiki?WikiEngines
Also some more here:
http://c2.com/cgi/wiki?WikiEngineReviewWikiLists
Great resource!
-
I use DokuWiki (http://www.dokuwiki.org/features), and I happy with it.
-
Yep. Maybe the best Wiki around (at least my favorite too).
Unfortunately we are not focusing on the Wiki aspects at the moment, and it seems it is not going to be top priority for some time.
Thanks for the tips aries!
-
You can use Textile wiki engine - we use Redmine project management system developed using Ruby on Rails and it has integrated wiki engine with Textile like wiki engine. But Ruby on Rails is slow and is not simple in installation.
This wiki engine is simpler than others. If editor had WYSIWYG abilities - no matter which engine to use - it must allow:
- working with tables
- images
- lists
- formatting of cause
- must have change history (user can restore to previous versions)
- page links (if page exists then link is not highlighed, but if not exists - it highlighted red, for example)
- autoassign parent page when crating page by clicking link to nonexistent page
- show wiki hierarhy as table of contents
- per project wiki
- interproject wiki links to prevent information duplicates
- and so on
It will be great for feng office to have such feature - it will give users tool for creation of knowledgebase and and other information networks.
Wiki table of contents may be made using mindmap style with ajax:
- rename page in mindmap tree (with autoredirection of links on other pages to this page)
- remove pages from mindmap tree
- create pages in mindmap tree
- open pages from mindmap tree
- move pages in mindmap tree
Thanks for your work! ;)
-
I know about Wiki engine, it is collaborative software that runs a wiki, i.e., a website that allows users to create and collaboratively edit web pages via a web browser.