How Angry Nerds convinced Atlassian to use Magnolia CMS

Atlassian and Magnolia

How Angry Nerds convinced Atlassian to
use Magnolia CMS

Wednesday, 12 September 12

About Me

Director of Interactive
Atlassian Software

San Francisco, CA

@halv0112


About Atlassian

Make JIRA and Conﬂuence

Based in Sydney, Australia

About 21,000 Customers

~550 Employees

Over $120M annual sales


We make this.


and this.


“ You have to know the past to understand

the present.
”
- Carl Sagan


www.atlassian.com


wac


.2011
wacc

9 Years Old


~1200 Pages


~2000 .jsp ﬁles


This was our
development
environment


This was our
developer


This was our content
staging environment


This was our content
entry specialist.


When we wanted to
push out content,
we would go here...


and then we would
do this.


~1,000,000 Pageviews per
mo.


1 Language


This is where we
wanted to be


What we needed
• Multiple Languages
• Separation between layout and content
• Delegated Authoring
• Staging and QA
• Rollback


Tomcat
(existing site)

Apache

Magnolia
(~40 new pages)

Pilot Architecture

Pilot


iWac Why iWac? Design Features Performance Try Now

Introducing iWac
The ultimate all-in-one. Turbocharged.



International



International
10 Languages



Local



Local
33 Countries



Scaleable



Scaleable
10x33x40=13,200



Scaleable
10x33x40=13,200
(4x7)+(3x4)+(2x33)=106



Why iWac?
Expansion in Europe

Japanese Website Aging

‘Spelling Error’ problem

No staging process



Design Requirements
Must fit in existing architecture

Must allow delegation of content editing

Must support internationalization (i18n)
and Localization (l10n)



Features
Seamless user experience

Phased approach to moving content to CMS

Workflow for Editors and Publishers

Clear path from Development->Staging->Production



The Fastest Wac yet.
Designed to describe our products in 90 seconds.



Try Now
atlassian.com/local



Success!

“ I’d love to change the world, but they

won’t give me the source code
”
– Unknown


April Fools


2008 - The PairOn
• Fully unit-tested in our
ego-free ergonomics lab
• Essential ofﬁce furniture
for any eXtreme XP Pair
(XXPP)
• Fully adjustable via
individual or pair control


2009 - JIRA Solver
Modern development
environments literally write
code for your developers.
Why can't your issue tracker
do the same for your
issues?


2010 - Fourwalls
• Location based services for
developer check-ins
• It’s not what you code.
It’s where you code.

http://atlassian.com/fourwalls


2012 - IRKD
You use JIRA to track
defects in your software.
Now use IRKD to track
defects in your everyday
life.

http://irkd.me


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


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


“ This game seems pretty awesome, so I set up

some automation to play it while I slept. I

awoke to ﬁnd myself on level 3019 with a score

in excess of twenty six million points. ”
– JST-17777


Pageviews
1000000

750000

500000
Daily Pageviews

250000

0
March 28 March 29 March 30 March 31 April 1 April 2 April 3 April 4


Tomcat
(existing site)

Apache

Magnolia
(~41 new pages)

Pilot Architecture

Success... Finally!


Redesign


Logo Problems

Less Distinct

More Distinct

Dude. Suite.

Making It Real

To Learn More
HTML5 History api to Ajaxify your Magnolia Website
William Paoli, Atlassian

Tomorrow 9:45-10:15


Reﬁnement


“ I have not failed. I’ve just found 10,000

ways that won’t work.
”
– Thomas Edison


Campaign Template
• Similar to STK
• Inﬁnite Conﬁgurability
• Used almost exclusively


What’s New Pages
• Less landing pages
• Consistent location
• Less effort
• Self Service
• Clearer call to action


A/B Testing
• Always Be Testing
• Optimizely


Conclusion


Issues
• Lack of .ftl Versioning / Source Control with WebDAV
• Security difﬁcult to conﬁgure
• Upgrade to 4.5 Painful


Thank You!

mhalvorson@atlassian.com

@halv0112


Questions?


How Angry Nerds convinced Atlassian to use Magnolia CMS

Recomendados

Recomendados

Más contenido relacionado

Similar a How Angry Nerds convinced Atlassian to use Magnolia CMS

Similar a How Angry Nerds convinced Atlassian to use Magnolia CMS (20)

Más de bkraft

Más de bkraft (20)

Último

Último (20)

How Angry Nerds convinced Atlassian to use Magnolia CMS