Interferon Posted November 19, 2009 Share Posted November 19, 2009 I'd like to see a replacement for MediaWiki, even if it doesn't support as many features. Our online documentation is mostly written by the community in the wiki, and it would be nice if we could consolidate the wiki together with the forum/blog/profile system. Migration isn't even that big of an issue, since it is easy to copy and paste an article. All it needs is articles any authorized user group can edit. I'd make it simple in structure and just let the users define the layout of the articles. Link to comment Share on other sites More sharing options...
Enkidu Posted November 19, 2009 Share Posted November 19, 2009 I like the idea :cool: Link to comment Share on other sites More sharing options...
dr. Jekyll Posted November 20, 2009 Share Posted November 20, 2009 Quite interesting! I like it ;) Link to comment Share on other sites More sharing options...
Insydius Posted November 20, 2009 Share Posted November 20, 2009 http://www.ipbwiki.com It doesn't really replace MediaWiki, rather combines both MediaWiki and IPB3 together in one logged in session where you can register on either and have accounts sync on both, and allows posting to be transferred back and forth as well as setting up the skin template to be universal between the two. Link to comment Share on other sites More sharing options...
bfarber Posted November 20, 2009 Share Posted November 20, 2009 You can do this with IP.Content already. :) http://community.invisionpower.com/resources/articles.html Here's an example. Link to comment Share on other sites More sharing options...
Interferon Posted November 20, 2009 Author Share Posted November 20, 2009 That organization doesn't look too great for documentation. This is what our wiki looks like: http://leadwerks.com/wiki/index.php?title=Main_Page http://leadwerks.com/wiki/index.php?title=Entities Link to comment Share on other sites More sharing options...
bfarber Posted November 20, 2009 Share Posted November 20, 2009 Well, templates and CSS are fully customizable. It's of course understandable if a software product doesn't meet your needs, but I'd hazard a guess it's unlikely we'll write up a separate concurrent package that does one of the same things IP.Content does. A more realistic approach would be to figure out what IP.Content lacks, and then enhance it further to accommodate. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.