Provides a recap of how the online, wiki-based Carolina Communique evolved and won an Award of Excellence in the Newsletters: Web & Online category of the 2008 APEX Awards for Publication Excellence
Sapir, Rick. Carolina Communique (2008). Articles>Content Management>Newsletters>Wikis
Is a Documentation Wiki in your Future?
If we can solicit user participation in a Web 2.0 knowledge community (a volunter wiki documentation, for example), we might have a powerful means for creating high quality content. But how should this process work?
Hackos, JoAnn T. Center for Information-Development Management (2007). Articles>Documentation>Content Management>Wikis
Your staff may already be using one of the most productive collaboration tools ever built.
Dickerson, Chad. InfoWorld (2004). Articles>Collaboration>Content Management>Wikis
Using a Wiki to Write About Wikis 
Academic writers are used to having their ideas encapsulated and enshrined in printed text (e.g., a journal article or a book), but publishing them in a wiki strips them of this protection. What happens when strangers change our writing? Since the traditional academic publishing paradigm has not caught up with the open-editing, peer-to-peer model, are we equipped to deal with the paradigm shift that wikis represent? These are issues we consider in this short piece.
Wilder, Hilary and Sharmila Pixy Ferris. Journal of Electronic Publishing (2007). Articles>Writing>Content Management>Wikis
Wiki is a category of web server software that allows users to contribute content. Collaboration is the key to Wiki, which is designed as a powerful system for online communities to build web pages and web sites. Unlike blogs and forums, all users are allowed to contribute and edit existing content. Wiki is derived from the Hawaiian term "wiki wiki" meaning "quick". The concept behind a Wiki is that collaboration on projects will move it along quicker.
Small Business Software (2007). Articles>Content Management>Web Design>Wikis
Whikibility Cultural Key Drivers: Quickness
The fact that a Workplace could be considered 'quick' is not properly linked with the easiness to find information or with the speedy level of the communications: in this context it is linked to the Wiki feature of assuring a real-time updating access to contents and resources (data, information or knowledge and physical resources).
Cammarata, Vincenzo. Grow Your Wiki (2007). Articles>Content Management>Collaboration>Wikis
Wikibility Cultural Key Drivers: Collaboration
The true collaboration occurs when people have the possibility to co-work on the same sub-task, activating a mechanism of new knowledge creation. Collaboration is not so obvious if is not clearly supported: the risk is to exchange this 'together' learning process with a simple cooperation process, producing not new knowledge but only a simple addition of individual regress knowledge.
Cammarata, Vincenzo. Grow Your Wiki (2008). Articles>Content Management>Collaboration>Wikis
Wikibility Cultural Key Drivers: Flexibility
A flexible workplace is characterized by the capability of individuals to manage not only their work, time or resources, but also the possibility to influence and operate in an active way inside the community (from team to organizational level) and for these reasons to be part of the operational process.
Cammarata, Vincenzo. Grow Your Wiki (2008). Articles>Content Management>Workflow>Wikis
Wikibility Cultural Key Drivers: Openness
Strictly linked with transparency concept, openness is at the base of the principle that people work better if they have access to the right information and possibility to assume that all over the organization. The simple access to other group member data or the possibility to know activities scheduled also in other groups are normal operations in a mature context such as is allowed to look to other team solutions or results in order to decide something for the own team.
Cammarata, Vincenzo. Grow Your Wiki (2008). Articles>Content Management>Collaboration>Wikis
Wikibility Cultural Key Drivers: Peering
A common element between Wiki philosophy and innovation successful case histories, is the partial or total absence of structure or, saying better, of hierarchy. The possibility, in fact, to contribute in the same way, indifferently at which level you are involved in the organization, is one of the first steps towards the reduction of barriers to collaboration, participation and involvement in the organizational life.
Cammarata, Vincenzo. Grow Your Wiki (2008). Articles>Content Management>Collaboration>Wikis
Wikibility Cultural Key Drivers: Sharing
The possibility of sharing improves an effective distribution of common resources (meeting room, projector, corporate car...). In a more general acceptation of the term, the availability to ideas or previous solutions useful for different use is an advantage that make co-creation of new knowledge and a healthy circulation of knowledge possible.
Cammarata, Vincenzo. Grow Your Wiki (2008). Articles>Content Management>Collaboration>Wikis
The Rise Of Hyperlocal Information
The net effect of social networking is the increasing availability of fine-grained information about locales. This information is both interesting and valuable. It is sought after by people living in these places and by advertisers who are trying to reach these people. A handful of startups are recognizing the big potential of local information - relevance. In this post we look at different aspects of the hyperlocality, from satellites to local blogs, and ponder how this information will be organized and monetized.
Iskold, Alex. ReadWriteWeb (2008). Articles>Information Design>Content Management>Wikis
The Contribution Revolution: Letting Volunteers Build Your Business
Intuit’s cofounder challenges traditional companies to follow the lead of internet superstars—and of innovative peers such as Honda, Procter and Gamble, and Hyatt—in tapping the contributions of countless people beyond their organizations.
Cook, Scott. Harvard Business Review (2008). Articles>Management>Content Management>Wikis
Your Wiki Isn’t Wikipedia: How to Use It for Technical Communication

Learn how to use a wiki as an organizational tool within your company.
Mader, Stewart. Intercom (2009). Articles>Content Management>Wikis>Organizational Communication
The founder of FLOSS manuals discusses the intersection of books and Web 2.0 and the continuing evolution of publishing and technology.
Hyde, Adam. Intercom (2009). Articles>Documentation>Content Management>Wikis
What are your thoughts on whether wikis could be used for end-user technical documentation? I'd imagine that a more structured wiki based on DITA content (which may have already been created for end-users) might work well for technical documentation. Have you seen any good examples? I'd love to see a well-done example.
Gentle, Anne. BMC Software (2008). Articles>Content Management>Wikis>DITA
The aim of this paper is to introduce the concept of the Web-based collaborative authoring environment commonly referred to as wikis, and examine how they can be used in a corporate publishing environment. The paper also includes suggested techniques for transferring existing content from native authoring tools into a wiki format for online delivery.
Porter, Alan J. Shortcovers (2009). Articles>Content Management>Wikis>White Papers
Although wikis have gained substantially in popularity since they first appeared some ten years ago, many enterprises still begin their wiki projects with unrealistic expectations.
Jespersen, Dorthe R. CMS Watch (2009). Articles>Content Management>Wikis>Content Strategy
Control and Community: A Case Study of Enterprise Wiki Usage
There are a wide variety of uses for Wikis and a level of interest in using them that’s matched by an extensive range of Wiki software. Wikis introduce to the Internet a collaborative model that not only allows, but explicitly encourages, broad and open participation. The idea that anyone can contribute reflects an assumption that both content quantity and quality will arise out of the ‘wisdom of the crowd.’
Clarke, Matthew C. Boxes and Arrows (2009). Articles>Web Design>Content Management>Wikis
Wiki-fying Docs: Is Using Customer-Accessible Wikis for End-User Documentation Gaining Momentum?
While the effort to provide more interactivity and power to the end-user seems to suggest that we open up a wiki to allow them to add and edit content, the basic idea of a set of edited documentation is now challenged with a social network of participating customers, all of whom may now edit, add, and delete content. How social can you go? This article is an attempt to look at the process of evaluating the use of a wiki for end-user documentation, if such a thing can exist. Are the two types of customer content — wikis and end-user documentation — mutually exclusive?
Kent, Betsy and Bill Albing. KeyContent.org (2009). Articles>Documentation>Content Management>Wikis
Daisy: WYSIWYG Wiki for PDF Books 
If you need the collaborative aspects of a Wiki combined with DITA's modular topics and publishing capabilities, then DAISY might just be the system you need--and it's free. DAISY provides WYSIWYG editing for Wiki pages that can be combined to publish books, either in a PDF or as a single HTML page.
Armstrong, Eric. Sun Microsystems (2008). Articles>Content Management>Documentation>Wikis
The Medium is the Delivery Method
A question that technical communicators frequently ask about wikis is "How do I get the documentation out of a wiki?" A simple answer: "Don’t worry about it." Because the wiki is the delivery method.
Nesbitt, Scott. DMN Communications (2009). Articles>Documentation>Content Management>Wikis
Are Structured Authoring and Wiki Opposing Forces?
There are two camps in technical documentation. There’s the “quick web” folks who connect easily and author easily, and then there’s the “structured quality” camp that requires more thoughtful testing and time spent on task analysis and information architecture.
Gentle, Anne. Just Write Click (2007). Articles>Content Management>Information Design>Wikis
Control and Community: A Case Study of Enterprise Wiki Usage
Like many companies, CorVu has extensive knowledge of its own products and a desire to make that knowledge available to customers. A major block to achieving that desire has been a lack of people with the time to either record the internal knowledge or to fashion the knowledge into a customer-ready format. We needed to spread the load so that a broad range of developers, tech writers, professional service consultants and others could all contribute what time and knowledge they had to a shared goal. Our hope was that a process built around several Wiki sites would facilitate this collaborative approach.
Clarke, Matthew C. Boxes and Arrows (2009). Articles>Content Management>Wikis>Case Studies
Care to Write Army Doctrine? With ID, Log On
In July, in a sharp break from tradition, the Army began encouraging its personnel — from the privates to the generals — to go online and collaboratively rewrite seven of the field manuals that give instructions on all aspects of Army life. The program uses the same software behind the online encyclopedia Wikipedia and could potentially lead to hundreds of Army guides being “wikified.” The goal, say the officers behind the effort, is to tap more experience and advice from battle-tested soldiers rather than relying on the specialists within the Army’s array of colleges and research centers who have traditionally written the manuals.
Cohen, Noam. New York Times, The (2009). Articles>Content Management>Documentation>Wikis
There are 10 readers currently online: 1 registered user and 9 guests. Register.

![]()
![]()


![]()
![]()
![]()