The document describes how Atlassian convinced their development team to use the Magnolia CMS. It outlines their previous content management process, issues they faced, a pilot program using Magnolia for 40 pages, a redesign, and eventual adoption of Magnolia for their entire website. Key benefits of Magnolia included support for multiple languages, separation of content and layout, and a staging process.
2. Atlassian and Magnolia
How Angry Nerds convinced Atlassian to
use Magnolia CMS
Wednesday, 12 September 12
3. About Me
Director of Interactive
Atlassian Software
San Francisco, CA
@halv0112
Wednesday, 12 September 12
4. About Atlassian
Make JIRA and Confluence
Based in Sydney, Australia
About 21,000 Customers
~550 Employees
Over $120M annual sales
Wednesday, 12 September 12
24. This is where we
wanted to be
Wednesday, 12 September 12
25. What we needed
• Multiple Languages
• Separation between layout and content
• Delegated Authoring
• Staging and QA
• Rollback
Wednesday, 12 September 12
30. iWac Why iWac? Design Features Performance Try Now
Introducing iWac
The ultimate all-in-one. Turbocharged.
Wednesday, 12 September 12
31. iWac Why iWac? Design Features Performance Try Now
International
Wednesday, 12 September 12
32. iWac Why iWac? Design Features Performance Try Now
International
10 Languages
Wednesday, 12 September 12
33. iWac Why iWac? Design Features Performance Try Now
Local
Wednesday, 12 September 12
34. iWac Why iWac? Design Features Performance Try Now
Local
33 Countries
Wednesday, 12 September 12
35. iWac Why iWac? Design Features Performance Try Now
Scaleable
Wednesday, 12 September 12
36. iWac Why iWac? Design Features Performance Try Now
Scaleable
10x33x40=13,200
Wednesday, 12 September 12
37. iWac Why iWac? Design Features Performance Try Now
Scaleable
10x33x40=13,200
Wednesday, 12 September 12
38. iWac Why iWac? Design Features Performance Try Now
Scaleable
10x33x40=13,200
(4x7)+(3x4)+(2x33)=106
Wednesday, 12 September 12
39. iWac Why iWac? Design Features Performance Try Now
Why iWac?
Expansion in Europe
Japanese Website Aging
‘Spelling Error’ problem
No staging process
Wednesday, 12 September 12
40. iWac Why iWac? Design Features Performance Try Now
Design Requirements
Must fit in existing architecture
Must allow delegation of content editing
Must support internationalization (i18n)
and Localization (l10n)
Wednesday, 12 September 12
41. iWac Why iWac? Design Features Performance Try Now
Features
Seamless user experience
Phased approach to moving content to CMS
Workflow for Editors and Publishers
Clear path from Development->Staging->Production
Wednesday, 12 September 12
42. iWac Why iWac? Design Features Performance Try Now
Wednesday, 12 September 12
43. iWac Why iWac? Design Features Performance Try Now
Wednesday, 12 September 12
44. iWac Why iWac? Design Features Performance Try Now
Wednesday, 12 September 12
45. iWac Why iWac? Design Features Performance Try Now
Wednesday, 12 September 12
46. iWac Why iWac? Design Features Performance Try Now
Wednesday, 12 September 12
47. iWac Why iWac? Design Features Performance Try Now
Wednesday, 12 September 12
48. iWac Why iWac? Design Features Performance Try Now
Wednesday, 12 September 12
49. iWac Why iWac? Design Features Performance Try Now
Wednesday, 12 September 12
50. iWac Why iWac? Design Features Performance Try Now
The Fastest Wac yet.
Designed to describe our products in 90 seconds.
Wednesday, 12 September 12
51. iWac Why iWac? Design Features Performance Try Now
Try Now
atlassian.com/local
Wednesday, 12 September 12
52. iWac Why iWac? Design Features Performance Try Now
Success!
Wednesday, 12 September 12
53. “ I’d love to change the world, but they
won’t give me the source code
”
– Unknown
Wednesday, 12 September 12
55. 2008 - The PairOn
• Fully unit-tested in our
ego-free ergonomics lab
• Essential office furniture
for any eXtreme XP Pair
(XXPP)
• Fully adjustable via
individual or pair control
Wednesday, 12 September 12
56. 2009 - JIRA Solver
Modern development
environments literally write
code for your developers.
Why can't your issue tracker
do the same for your
issues?
Wednesday, 12 September 12
57. 2010 - Fourwalls
• Location based services for
developer check-ins
• It’s not what you code.
It’s where you code.
http://atlassian.com/fourwalls
Wednesday, 12 September 12
58. 2012 - IRKD
You use JIRA to track
defects in your software.
Now use IRKD to track
defects in your everyday
life.
http://irkd.me
Wednesday, 12 September 12
59. 2012 - Spooning
DVCS technology
introduced the world to
forking. Now, we here at
Bitbucket are proud to
present the next step in the
process – spooning!
http://bitbucket.org/spooning
Wednesday, 12 September 12
62. 2011 - Angry Nerds
What do you do when you
have bugs in your code?
Send in the Angry Nerds.
Consider these issues…
resolved.
http://atlassian.com/angrynerds
Wednesday, 12 September 12
64. “ This game seems pretty awesome, so I set up
some automation to play it while I slept. I
awoke to find myself on level 3019 with a score
in excess of twenty six million points. ”
– JST-17777
Wednesday, 12 September 12
67. Pageviews
1000000
750000
500000
Daily Pageviews
250000
0
March 28 March 29 March 30 March 31 April 1 April 2 April 3 April 4
Wednesday, 12 September 12
83. iWac Why iWac? Design Features Performance Try Now
The Fastest Wac yet.
Designed to describe our products in 90 seconds.
Wednesday, 12 September 12