Atlassian: A Case of Too Much Content

Page 2 of 2

May 27, 2013


Atlassian explored a few different content management systems but decided on Magnolia's CMS in the end. Halvorson was familiar with Magnolia as it is a customer through Atlassian's Free Open Source License Program.

Magnolia was designed with ease of use, flexibility, and scalability in mind. Regardless of the size of the organization, the number of languages used, or how many channels or websites are being used, content can be pushed out quickly and efficiently. With usability as a priority, Magnolia makes it possible for editors to create content at the same time that Java developers, designers, and programmers work.

In addition, Magnolia "integrates well with other key systems of record, e.g., booking engines or custom insurance policies. As such, it provides a digital bridge between the true organization-the people and systems at its heart-and its customers, members or citizens," explains Boris Kraft, chief technology officer and co-founder of Magnolia. This makes Magnolia a rather sophisticated system, despite how simple it is to use.

Because of its open source nature, Magnolia does not handle implementation of its product. This guarantees "that there is a vital source of revenue for our community, without the conflict of interest sometimes found around other open source CMS offerings," explains Kraft. Instead, implementation can be handled by an international network of qualified partners. However, as one of Atlassian's strengths lies in Java development, the company chose to oversee its own implementation.

Atlassian began its pilot phase with Magnolia's open source version, and relied heavily on the sizeable Magnolia community, which provided forums and documentation. This process took about 3 months and provided Atlassian with the benefit of being able to test the product without making an investment up front.

Following this successful pilot, Atlassian invested in Magnolia's Enterprise Edition. This afforded the benefit of Magnolia support for any issues or challenges. "We were fairly comfortable working with Magnolia after the pilot, however, with a system as configurable as Magnolia CMS, we still sometimes questioned whether we did things the ‘right' way. It is really easy to read a templating tutorial and just get started, but you can quickly make some errors that are difficult to recover from," shares Atlassian's Halvorson. Despite the sometimes challenging time difference of these international companies, Atlassian found the Magnolia support team incredibly responsive.

Magnolia provides a Standard Templating Kit (STK), a best practice tool to assist developers. However, as the available STK did not quite mesh with what Atlassian was looking for, Halverson's team decided to create its own campaign template that included all the components it uses throughout its site. With this template created, Atlassian was able to take advantage of the benefits of Magnolia's CMS.

The full overhaul of Atlassian's site took approximately a year, including the rebranding and a full redesign culminating in an Atlassian Launch Night, which was streamed live globally on Oct. 25, 2011.


It did not take long for Atlassian to begin realizing the benefits of Magnolia, and results have been consistently positive since implementation. Gone are the days of having to go through a single developer to add all new content or make a simple alteration or correction. Gone are long delays before changes took effect. Content owners now have the ability to access the system and implement changes directly and almost immediately; the process is straightforward and intuitive.

Because Magnolia is simple to use, Atlassian is not finding a need to invest in a great deal of training for current or new team members. "My team has to do very little explanation when on boarding new content owners. They just get it," Halvorson explains.

Although Atlassian's implementation of Magnolia is complete, its site is always undergoing changes and additions, and Magnolia is operating exactly as Halvorson and his team needs it to.

As two cutting-edge software companies with similar values of community and openness, both Atlassian and Magnolia hold each other in high esteem. They are pleased to be working together on multiple levels and look forward to future collaborative possibilities such as the integration of respective products being made available to the public.

Page 2 of 2