tags:

views:

489

answers:

9

With no limits on the technology and cost what is the best wiki/blog solution for corporate use. I have a customer that wants to use blogs to post up-to-date information on company standards for discussion and dissemination, then when the blog entries have been massaged they want to move the content to a wiki page as a more permanent place. Internally they then want to make small modifications to these standards while it is on the wiki but have it readable to the outside world. They do not use share point.

+3  A: 

Confluence is a very good one.

Otávio Décio
I have *many* years of wiki usage and I am a big fun of them but Confluence is one of the ones I would recommend only to enemies.
Sorin Sbarnea
A: 

I'd have thought it would be the other way around: massaging and discussion on a Wiki and then move to a blog when done for viewing by the outside world.

You can't go wrong with Wordpress for the blog. Free. Tons of themes. Tons of plugins.

Steve Claridge
+4  A: 

I think wordpress and mediawiki would be a very acceptable (free) solution. There are several integration solutions for the two.

Joel Hooks
Multi-user WP: http://mu.wordpress.org/ with Automattic support (http://automattic.com/services/support-network/) should work very well, I think.
Nick Presta
I would vote against MediaWiki for general corporate use. In our company, the editing syntax and non-intuitive method of creating new pages has proven to be a significant barrier to adoption among the non-developers.
Matt Dillard
A: 

I like JSPWiki.

Gary Kephart
+2  A: 

Screwturn has helped my team a lot, it's written in asp.net.

jdecuyper
A: 

Is your company using SharePoint? If so, you can setup blog and wiki in SharePoint.

Zaagmans
Sharepoint Wiki is a major disappointment - ugly, hard to use - I would stay away from it (even if your company uses Sharepoint elsewhere)...
marc_s
+1  A: 

I would look at what tech is in the company already ... you don't want to use wordpress/mediawiki if you already are running IIS and share point. Also look at authentication do you already have an LDAP server ... who will need to authenticate and from where. Try to set up as little extra infrastructure as possible.

trent
+2  A: 

Plone has a good document editing and publishing workflow. You can control what is being viewed internally and by the outside world.

Rohit
+1  A: 

At my work, we'd been using a mix of TiddlyWiki & Sharepoint, but we've now moved to Confluence. It's been really working well for us, and now tons of other teams at my company are also on Confluence.

Confluence has WYSIWYG editing, email archiving, edit in Word, a Sharepoint Connector, tons of plugins & macros, connection to Jira, personal spaces, RSS feeds, email updates, front page with latest changes, favorite spaces/pages, page templates, page history and diff revisions, labels, export to PDF, comment threads per page, a people directory, etc.

It's not free though, although I think they have a free version for open source projects.

Anthony Brien