Impact Of A Cms Framework Change - Holland Open Netherlands


Published on

Presentation about the impact of a major CMS framework change, given on 18th of september at the Holand Open converence

Published in: Technology
  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide
  • Impact Of A Cms Framework Change - Holland Open Netherlands

    1. 1. Impact of a CMS framework change <ul><li>Holland Open </li></ul><ul><li>Amsterdam, Netherlands </li></ul>20 September 2008
    2. 2. <ul><li>Wilco Jansen </li></ul><ul><li>Development Working Group Coordinator </li></ul><ul><li>Senior project manager at Atos Origin </li></ul>Pleased to meet you!
    3. 3. <ul><li>What is the impact of an Open CMS framework change on installed versions. What pre-cautions can one take and what needs to be anticipated? Migration effort after a framework change can be vast and this session will discuss the right timing to do so and tools you can or should not use... </li></ul>Today’s program
    4. 4. What is a CMS?
    5. 5. What is a CMS Framework?
    6. 6. Meet Joomla!
    7. 7. <ul><li>Joomla is easy to install </li></ul><ul><li>Joomla runs on many platforms </li></ul><ul><li>Joomla is easy to extend </li></ul><ul><li>Joomla is multi-lingual (including RTL) </li></ul><ul><li>Joomla is easy to administer </li></ul><ul><li>Joomla allows you to create virtually any kind of look-and-feel (also following web standards) </li></ul><ul><li>Joomla is build to scale </li></ul><ul><li>Joomla supports rapid development </li></ul>The Joomla! Promotional talk
    8. 8. <ul><li>4.750.000 visitors and 21.000.000 page hits past month </li></ul><ul><li>1.365.000 posts, 295.000 topics and 220.000 users in our forum </li></ul><ul><li>590.000+ downloads of Joomla! 1.5 in 2 months after release (6.5 million in total, excluding mirrors) </li></ul><ul><li>82.000 registered developers and 2.255 registered projects on Gforge </li></ul><ul><li>3.747 registered (active) projects on our extensions site </li></ul><ul><li>60+ supported languages </li></ul>Some statistics
    9. 9. Joomla! In perspective Wordpress – 2,55% Joomla – 0,76% Drupal – 0,15% Source: CMS research Jansen IT Services 2008
    10. 10. The Joomla! Framework change <ul><li>Joomla! 1. 0 .x </li></ul><ul><li>Codebase originally released under GPL in 2002/2003 by Miro </li></ul><ul><li>Joomla! 1.0.0 released on September 2005 (fork from Mambo 4.5.3) </li></ul><ul><li>Mainly procedural oriented </li></ul><ul><li>Build for PHP 4.x and MySQL 3.x </li></ul><ul><li>Joomla! 1. 5 .x </li></ul><ul><li>Full re-write of the codebase </li></ul><ul><li>Joomla! 1.5.0 released 22 January 2008 </li></ul><ul><li>Fully object oriented and pattern based </li></ul><ul><li>MVC implemented </li></ul><ul><li>Made out of application and CMS framework part </li></ul><ul><li>90% backward compatible with 1.0.x compatibility layer </li></ul>
    11. 11. Joomla! 1.5 architecture <ul><li>Framework principles </li></ul><ul><li>Pragmatic Programming Concepts </li></ul><ul><li>Object Oriented API </li></ul><ul><li>Modularized Design </li></ul><ul><li>Focused on content management </li></ul><ul><li>Build for PHP 4 and upwards compatible with PHP 5 </li></ul><ul><li>Fundament for easy removal of backward compatibility and move to PHP 5.2+ and MySQL 4.1+ </li></ul><ul><li>Framework concepts </li></ul><ul><li>Decouple as much as possible </li></ul><ul><li>Use design patterns where possible </li></ul><ul><li>Don’t repeat yourself (DRY) </li></ul><ul><li>Remember the big picture </li></ul><ul><li>Create declarative interfaces </li></ul>
    12. 12. Joomla! 1.5 CMS Framework <ul><li>Ease of use </li></ul><ul><li>End-user </li></ul><ul><li>Webmaster </li></ul><ul><li>Designer </li></ul><ul><li>Developer </li></ul><ul><li>Content management </li></ul><ul><li>Keep it small and simple </li></ul><ul><li>Be flexible and agile </li></ul><ul><li>Designed to be extendible </li></ul><ul><ul><li>Templates (look-and-feel) </li></ul></ul><ul><ul><li>Language </li></ul></ul><ul><ul><li>Modules </li></ul></ul><ul><ul><li>Components </li></ul></ul><ul><ul><li>Plugins </li></ul></ul><ul><li>Use the 80/20 rule </li></ul><ul><li>Reduce choices </li></ul>
    13. 13. Let’s have a look at the impact of such a major framework change
    14. 14. Going from…
    15. 15. To…
    16. 16.
    17. 17. Project Impact <ul><li>Starting from Joomla! 1.0.x and </li></ul><ul><li>Existing user base </li></ul><ul><li>Existing extensions </li></ul><ul><li>Existing documentation </li></ul><ul><li>Existing perception </li></ul><ul><li>Why should I migrate? </li></ul><ul><li>When should we migrate? </li></ul><ul><li>How can we migrate? </li></ul><ul><li>What does the new framework offer? </li></ul><ul><li>… migrating to </li></ul><ul><li>New support model required </li></ul><ul><li>New documentation required </li></ul><ul><li>90% of extensions could be re-used with legacy layer, but re-write to new MVC structure is preferred (native) </li></ul><ul><li>Is the new framework stable enough? </li></ul><ul><li>Are there any native Joomla! 1.5 extensions out there? </li></ul>Impact of the framework change
    18. 18. Impact for the community <ul><li>Freedom of choice: </li></ul><ul><ul><li>Stay with 1.0.x platform </li></ul></ul><ul><ul><li>Use backward compatibility layer </li></ul></ul><ul><ul><li>Use the full potential of the new framework </li></ul></ul><ul><li>Removal of some (technical) barriers </li></ul><ul><ul><li>Accessibility </li></ul></ul><ul><ul><li>Web-standards </li></ul></ul><ul><ul><li>No need for core hacking </li></ul></ul><ul><ul><li>Scalability </li></ul></ul><ul><ul><li>Etc. </li></ul></ul><ul><li>More involvement </li></ul><ul><ul><li> </li></ul></ul><ul><ul><li> </li></ul></ul><ul><ul><li>Pizza Bug and Fun event(s) </li></ul></ul><ul><ul><li>Joomla! Bug Squad </li></ul></ul><ul><ul><li>Improved attention for security (Joomla! Security Strike Team) </li></ul></ul>Impact of the framework change
    19. 19. When to migrate?
    20. 20. Website impact <ul><li>Don’t migrate… </li></ul><ul><li>When there is no backup </li></ul><ul><li>When the geeks advise you to i.e. there is no specific (business) reason </li></ul><ul><li>When you have not convinced yourself that all extensions work </li></ul><ul><li>When you are not certain the migration delivers visible benefit </li></ul><ul><li>When you have no clue what it takes to migrate </li></ul>Don’t migrate when…
    21. 21. Decide if a migration has added value
    22. 22. <ul><li>In general </li></ul><ul><li>Consider the time required to complete the migration </li></ul><ul><li>Set goals: </li></ul><ul><ul><li>Migrate only </li></ul></ul><ul><ul><li>Migrate and improve </li></ul></ul><ul><ul><li>Only re-use content </li></ul></ul><ul><ul><li>Etc. </li></ul></ul><ul><li>Address technical issues </li></ul><ul><li>Extension compatibility </li></ul><ul><li>Availability of migrator plug-ins for 3 rd party developers </li></ul><ul><li>Infrastructure requirements fit? </li></ul><ul><li>Address non-technical issues </li></ul><ul><li>Make sure content management processes are in place </li></ul><ul><li>Check to ensure that all content has an owner </li></ul><ul><li>Migrate </li></ul><ul><li>Conduct a content audit </li></ul><ul><li>Use the opportunity to migrate to a new site structure if appropriate </li></ul><ul><li>Consider re-writing content if necessary </li></ul>Handle it like a project!
    23. 23. Tools you can use
    24. 24. <ul><li>Manual migration </li></ul><ul><li>Use the Joomla! Migrator tool </li></ul><ul><li>Or just combine both </li></ul>Tools you can use
    25. 25. <ul><li>Prerequisites </li></ul><ul><li>Backup your old site! </li></ul><ul><li>Download the migrator component </li></ul><ul><li>Migration steps: </li></ul><ul><li>Install 3 rd party migrator plug-ins on the old environment </li></ul><ul><li>Create the migration SQL </li></ul><ul><li>Install a fresh copy of Joomla! 1.5 </li></ul><ul><li>Run Joomla! Installation, and use the migration SQL and install </li></ul>
    26. 26. Questions?