Draw.io is a powerful, professional diagramming-tool available as an add-on for Confluence and JIRA, and as a free online-tool. This post will introduce you to the latest features and show you how to stay up-to-date with the latest developments.
The basis for this article were recently constructed under the leadership of Martin Seibert at an open-space session at the WikiSym in Portugal. The original document is available in English under the title “How good is MS Sharepoint as a wiki?”
Without professional knowledge management, companies are losing potential, wasting resources, and acquiring unwanted competitive disadvantages. Along with many other companies, the industry giant Microsoft has rolled out its own application, SharePoint, which allows data to be centrally deposited and edited.
draw.io allows the creation of a diverse range of diagrams within Confluence and JIRA via an intuitive and responsive interface. Possible diagrams are flow charts, network diagrams, org charts, UML diagrams, mind maps and many more. draw.io is based on a market leading diagram technology that has been developed by JGraph in 2005 and therefore has matured a lot by now. In 2012 the application draw.io was created and is available as a plugin on the Atlassian Marketplace, directly offered by //SEIBERT/MEDIA.
There are several solutions to implement diagramming functions in Confluence. Creately is one of them – compared to the matured draw.io, Creately is at a disadvantage. We have compared Creately and draw.io regarding central requirements. Here is a comparison of both diagramming tools, let’s take at a look at the five most important aspects. Flash vs. native Browser technologies: Creately is based on Flash. This has been problematic, since Flash is well known for it’s security weaknesses and it’s vulnerability. Many enterprises (especially in Enterprise environments) do not allow Flash for standard computer installations and don’t allow users to install Flash at a later point. draw.io, on the other hand, is based on the market leading diagramming technology mxGraph – the only library that works in any browser without plugins and completely client based.
In our article, “Enterprise Wikis: Criteria and important topics in the evaluation of wiki software” we discussed the diverse and unique requirements an enterprise wiki needs to meet. Decisions about choosing the right wiki system cannot be made using generalizations, but rather only by taking into account the specific needs of the company. In this article, we will draw a concrete comparison between the approaches of the Atlasssian Confluence commercial system and the open source systems Foswiki and MediaWiki. What are the strengths of Confluence compared to Foswiki and MediaWiki?
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.
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.
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.
In this video podcast, Martin Seibert and Alex Boerger discuss Trello and Basecamp as JIRA alternatives in the enterprise. In the beginning, they give a brief introduction and overview of the functionality and best practice of each product. The discussion shows that each product has its own market and the usage depends on your use case. If you are a small team of up to 5 people, Basecamp and Trello might be a good choice. But for bigger companies, with different and more complex projects, JIRA is the only way to make you happy.