1. Impact of a CMS framework change

• Holland Open

Amsterdam, Netherlands

20 September 2008 2.

Wilco Jansen

Development Working Group Coordinator

Senior project manager at Atos Origin

Pleased to meet you! 3.

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...

Todays program 4. What is a CMS? 5. What is a CMS Framework? 6. Meet Joomla! 7.

Joomla is easy to install

Joomla runs on many platforms

Joomla is easy to extend

Joomla is multi-lingual (including RTL)

Joomla is easy to administer

Joomla allows you to create virtually any kind of look-and-feel (also following web standards)

Joomla is build to scale

Joomla supports rapid development

The Joomla! Promotional talk 8.

4.750.000 visitors and 21.000.000 page hits past month

1.365.000 posts, 295.000 topics and 220.000 users in our forum

590.000+ downloads of Joomla! 1.5 in 2 months after release (6.5 million in total, excluding mirrors)

82.000 registered developers and 2.255 registered projects on Gforge

3.747 registered (active) projects on our extensions site

60+ supported languages

Some statistics 9. Joomla! In perspective Wordpress 2,55% Joomla 0,76% Drupal 0,15% Source: CMS research Jansen IT Services 2008 10. The Joomla! Framework change

Joomla! 1. 0 .x

Codebase originally released under GPL in 2002/2003 by Miro

Joomla! 1.0.0 released on September 2005 (fork from Mambo 4.5.3)

Mainly procedural oriented

Build for PHP 4.x and MySQL 3.x

Joomla! 1. 5 .x

Full re-write of the codebase

Joomla! 1.5.0 released 22 January 2008

Fully object oriented and pattern based

MVC implemented

Made out of application and CMS framework part

90% backward compatible with 1.0.x compatibility layer

11. Joomla! 1.5 architecture

Framework principles

Pragmatic Programming Concepts

Object Oriented API

Modularized Design

Focused on content management

Build for PHP 4 and upwards compatible with PHP 5

Fundament for easy removal of backward compatibility and move to PHP 5.2+ and MySQL 4.1+

Framework concepts

Decouple as much as possible

Use design patterns where possible

Dont repeat yourself (DRY)

Remember the big picture

Create declarative interfaces

12. Joomla! 1.5 CMS Framework

Ease of use

End-user

Webmaster

Designer

Developer

Content management

Keep it small and simple

Be flexible and agile

Designed to be extendible

• Templates (look-and-feel)

• Language

• Modules

• Components

• Plugins

Use the 80/20 rule

Reduce choices

13. Lets have a look at the impact of such a major framework change 14. Going from 15. To 16. 17. Project Impact

Starting from Joomla! 1.0.x and

Existing user base

Existing extensions

Existing documentation

Existing perception

Why should I migrate?

When should we migrate?

How can we migrate?

What does the new framework offer?

migrating to

New support model required

New documentation required

90% of extensions could be re-used with legacy layer, but re-write to new MVC structure is preferred (native)

Is the new framework stable enough?

Are there any native Joomla! 1.5 extensions out there?

Impact of the framework change 18. Impact for the community

Freedom of choice:

• Stay with 1.0.x platform

• Use backward compatibility layer

• Use the full potential of the new framework

Removal of some (technical) barriers

• Accessibility

• Web-standards

• No need for core hacking

• Scalability

• Etc.

More involvement

• documentation.joomla.org

• community.joomla.org

• Pizza Bug and Fun event(s)

• Joomla! Bug Squad

• Improved attention for security (Joomla! Security Strike Team)

Impact of the framework change 19. When to migrate? 20. Website impact

Dont migrate

When there is no backup

When the geeks advise you to i.e. there is no specific (business) reason

When you have not convinced yourself that all extensions work

When you are not certain the migration delivers visible benefit

When you have no clue what it takes to migrate

Dont migrate when 21. Decide if a migration has added value 22.

In general

Consider the time required to complete the migration

Set goals:

• Migrate only

• Migrate and improve

• Only re-use content

• Etc.

Address technical issues

Extension compatibility

Availability of migrator plug-ins for 3 rdparty developers

Infrastructure requirements fit?

Address non-technical issues

Make sure content management processes are in place

Check to ensure that all content has an owner

Migrate

Conduct a content audit

Use the opportunity to migrate to a new site structure if appropriate

Consider re-writing content if necessary

Handle it like a project! 23. Tools you can use 24.

Manual migration

Use the Joomla! Migrator tool

Or just combine both

Tools you can use 25.

Prerequisites

Backup your old site!

Download the migrator component

Migration steps:

Install 3 rdparty migrator plug-ins on the old environment

Create the migration SQL

Install a fresh copy of Joomla! 1.5

Run Joomla! Installation, and use the migration SQL and install

26. Questions?