Working with Confluence, you notice how fast the content of your wiki is constantly expanding. Eventually some content needs to be updated due to new information or developments. The question that might arise: Shall I create a new page with new content or rather update the existing page? In this video, Martin Seibert from //SEIBERT/MEDIA explains the advantages of updating a page rather than creating a new one. This approach might involve a bit of work and time but reduces redundancies and helps communicating updates to the existing followers of the old content.
At //SEIBERT/MEDIA, we’ve been working on a wiki for years. Through our day-to-day work as well as through dozens of enterprise wiki projects, we have experienced – thanks to innumerable different cases – how useful and valuable a wiki can be on a number of levels. Therefore, we believe it is high time to compress the arguments for a wiki into the limited space offered by tweets to make our points as efficiently as possible.
Wikis for enterprise use, both those available commercially as well as those available in open-source contexts, have become quite sophisticated. This article introduces and evaluates possible requirements as well as decision-making criteria.
We can no longer conceive of the //SEIBERT/MEDIA Intranet without a Wiki. As a knowledge management system and employee portal, the Wiki is of incalculable value within the company network, fueling the Intranet motor.
From dozens of enterprise Wiki projects, we know that the successful introduction of a Wiki into a company typically depends on three factors: technology; organization; and culture. In the first of these three articles we focused on the requirements of technology. The second of these articles focused on organizational factors. This report will now focus on the implications of company culture and how these relate to the introduction of a Wiki.
Many companies are unsure of how a successful Wiki project should be started and executed. This article will give you an overview and inform you of the basics. //SEIBERT/MEDIA/ offers transparent services. Ultimately, as the saying goes, we’re also just cooking with water, but we’ve collected many experiences regarding the process for Wiki-projects, which we will happily explain here – regardless of whether or not you are currently running a project with us, are planning a project with us, or simply wish to be more successful with your Wiki – without our help.
Exciting product news, such as Confluence Questions, were announced during Atlassian Summit 2013, Atlassians big user and partner conference. Confluence Questions expands Confluence by functionalities to build a knowledge base, which allows the user to actively ask for information. During the Summit, we met and interviewed Matt Hodges, Product Marketing Manager for Confluence, and Chris Kiehl, Dev Manager in the Confluence Team. What can Confluence Questions do? How does it differ from Microblogging-Tools such as Yammer, where users can also ask questions? Why is Confluence Questions not available with Confluence for Enterprise customers, but needs to be licensed separately? The following video has answers to these and more questions: