Wikis for intra-company usage are becoming well established as both commercial and open source applications. This article gives an overview of criteria and requirements involved in the decision making process, along with a comparison of our proprietary Wiki Confluence System and its open source competitors, Foswiki and MediaWiki.
Tag Archives: Confluence
Confluence and Foswiki Plugins – A Comparison
All wiki systems have the same basic functions: opening, editing and saving documents. These functions can be covered in a single Wikipedia paragraph. The functions of a more advanced business wiki, however, are more complex. A business wiki is not simply a web lexicon, but rather is intended to systematically handle a variety of processes in the company.
Company Wikis aren’t Wikipedia
Wikipedia is by far the best-known example of a wiki. This web lexicon is what most people immediately think of when they hear the word wiki. It’s not surprising, since the online encyclopedia is used by millions of people every day. However, Wikipedia is something completely different from a wiki that is used in a corporate intranet.
Classroom Licenses: Atlassian products for free at your university
You are a teacher or student at a university and want to gain practical experience working with Atlassian tools? Atlassian offers you the opportunity to use numerous products with the Classroom License – free of charge. All you have to do is submit an application. Why use Atlassian tools in your project? For budding software developers in particular, using Atlassian products during their studies is a great way to start working early on with tools designed for use in professional enterprises.
Atlassian Summit 2014 Highlights & Confluence Intranet Solutions – Sherif Mansour & Martin Seibert
As a follow up on last year’s surprise interview, Sherif Mansour, Atlassian Confluence product manager, talks with Martin Seibert about his Summit experience. Martin liked the road map, that Atlassian gave, announcing live editing and in line editing in Confluence in a future release. He also enjoys the integration of JIRA, Bamboo, and Stash with Confluence.
SharePoint as a Wiki vs. Confluence: Criteria and Requirements
Whoever is on the lookout for a simpler, slimmer solution that can be implemented much more quickly will find Confluence to be an extremely sophisticated package. In contrast to SharePoint, Confluence can be easily and successfully introduced without complications. And it can even be connected with SharePoint.
36 use cases for an enterprise microblog (13 – 24)
The digital form of the talk in the hallway, where employees exchange information, news, ideas and project details and receive feedback and input, are a benefit for enterprises. But what are specific use cases for an enterprise microblog? We have collected 36 use cases. After the first twelve, read more about use cases 13 to 24.
Wiki Adoption: Why there’s no Reason to be Scared of Sharing Knowledge
If in the opening phase of a wiki adoption it should be difficult to activate employees to participate, this is often because employees haven’t been properly brought up to speed and misunderstand the whole idea of a wiki. One symptom of this is the fear of sharing knowledge.
36 use cases for an enterprise microblog (1-12)
An internal microblog can become a useful channel of communication within an enterprise. Similar to having lunch or coffee together, or chatting in the hallway, employees exchange information, news, ideas or project details in a microblog. Sometimes the posts are time sensitive and important, sometimes they are just about exchanging ideas with colleagues and getting their input. Enterprises can benefit from that. What are specific use cases, and how can the internal tweeting gain strength? We have collected 36 use cases. Here are the first dozen.
Texts should be created, shared, and edited in a Wiki, not in Word or within e-mails
Within a company there can be many approaches for the development of texts as well as the sharing of texts for further revision. We could, for example, write a text in Word and then load the final version into the enterprise wiki. We could also send around texts by e-mail, asking colleagues to read them and, if necessary, to make changes. But we could also develop a text directly within a wiki. What should we think of this particular work process?