We will talk about VPRO, one of the first (public) broadcasters in the Netherlands active on the internet, and our first adventures in Magnolia. VPRO created it's own open-source CMS back in 1994 and selected Magnolia as successor of that product, which was getting dated after 15 years. In this period we created a lot of content, a lot of which needs to be accessible after the migration. How are we looking at this problem?
In March 2010 we launched our first site in Magnolia, in May the second, with many more to come in the next 2 years.
Our philosophy is to get all our main sites on the same platform and try to develop applications for all of them simultaneously, so each site profits from developments on functionality. We think we will have about different 100 sites in Magnolia by end of next year, some big, some small.
During the talk I would like to zoom in to the festival site we released in may. VPRO is media partner for Pinkpop, the largest pop festival in the Netherlands. We created a 'mashup' site for this festival a couple of years ago and rebuild this using Magnolia, CouchDB and Camel. This technology is now available to our other sites on the Magnolia platform. Using one site to create new applications, which become available to other sites on our platform is something we like to do, this is a nice example.
18. ‘Architecture 2.0’
Implementation
• Whole new CMS to learn
• No experience doing this
• Big bang no option
19. ‘Architecture 2.0’
Per-site approach
• Reasonable featureset
• Each site should add to toolbox
• Don’t try to recreate entire sites
• Roadmap
20. Project Arch 2.0
Roadmap (1/2)
- small site
Tegenlicht lots to learn,
march 2010
(Backlight) - treat as huge
basic media
service
- social media
Festival site may 2010
mashup
- Media
Hollanddoc
service
(documentari July 2010
- Media
es)
archive
21. Project Arch 2.0
Roadmap (2/2)
Geschiedenis adds time and location
oktober 2010
(history portal) based navigation
Site wizard
november
Programsites rethink architecture
2010
fix errors
Huge contentbase
3voor12 April 2011
music + band db
22. ‘Architecture 2.0’
What we learned
• Think good, not too good
• Accept to make mistakes, fix later
• Make hard decisions
• Tie new functionality to one site first
25. Festivalsite
Editorial Goals
• Combine editorial and social content
• ...for people not visiting: feel like being
there
• ...for event audience, relive experience at
home
32. Text
Film it yourself
• Last year Lowlands: 5 concerts, 33
participants, 8 hours rendering,
within 24hr online
• This year Lowlands: 33 concerts, 88
participants, no rendering, within
3hr online.