Feb 22, 2008
Day 13: Wiki vs. Content Management System
Can a wiki coexist with other tools? Here’s an example of how a wiki can work together with a Web Content Management System to make updating your public website more efficient:
Books |
|
|
 |
PhotosClick the photo above, or choose a photo essayAirbus Factory • Barcelona & Madrid • British Museum Istanbul • Porto • Sydney • Vancouver • Yosemite |
LinksBefore & After • Bobulate • Brand New • gary's choices Identityworks • The Ministry of Type • Pr*tty Sh*tty swissmiss • Taste of Beirut • Technology and Organizations • Work+Place |
WorkFuture Changes is the online home of Stewart Mader, an experienced content strategist and project manager, dynamic speaker to corporate audiences and conferences, and author of two books. He has helped organizations around the world, including Booz Allen Hamilton, Brown University, ICANN, MARS, SAP, and The World Bank develop content strategies and build products that increase information value, collaboration, and employee & customer engagement.Future Changes, founded in October 2005, has been cited by CIO Magazine, Fast Company, InformationWeek, InfoWorld, The Guardian, The New York Times, and The New Yorker. View Work Samples and Work with Stewart |
Future Changes, ISSN 1934-3728, is licensed under a Creative Commons License. You are free to share and remix, as long as you give credit and share alike. Questions? Contact me. Comments © their original authors. This site is powered by WordPress, Media Temple, and Polar Bears.
Martin says:
Feb 23rd, 2008
Totally agree. Every publication tool, whether blog, wiki or CMS has its own history, style and culture, and it is most of the time very difficult to switch from one collaboration tool to another if you don’t hide the change behind the familiar user interface that everyone knows.
Gina Fevrier says:
Jan 6th, 2010
We’re hoping to use our wiki as a CMS. Do you have any thoughts on that? We’re preparing to pilot a conversion of our Madcap Flare user docs to a wiki, such as Confluence.
Thanks!
P.S. We are getting lots of valuable information from your book Wikipatterns which we are reading online via our subscription at http://www.safarionlinebooks.com.
Stewart Mader says:
Jan 6th, 2010
Gina,
Great Idea. Make sure you know what content you want the system to contain, so that it doesn’t become messy and unfocused. You don’t have to define everything what will go in the wiki on day one, but you should have some clear starting points. For example, you might start with content that needs to be developed for marketing materials (data sheets, brochures, copy for your web site), pr (news releases, media contacts, promotion schedule for a new product launch), or product development (meeting agendas and minutes, requirements documents, and product documentation).
Good luck!
Stewart
Gina Fevrier says:
Jan 6th, 2010
Thanks very much for the comments.
We’ve already decided only to include the help docs (online help) and release notes for one of our products, one language at a time to start (English). Anne Gentle has given us some great ideas, especially in her book Conversation and Community: The Social Web for Documentation. I’ve also gotten great ideas from Sarah Maddox at Confluence. We like the way she’s used the Confluence wiki for its help docs.
I’m really glad you posted the videos which supplement your book (I’m still reading it).
Gina