Learn How and Why Drupal was used for www.gouvernement.fr
Download as PPTX, PDF1 like1,974 views
The French government website www.gouvernement.fr was moved to Drupal in early 2009 from its previous CMS, SPIP, which was outdated, French-focused, and had few people supporting it. Drupal was selected for its modularity, templating, flexible data handling, and role-based permissions. A team including 3 senior Drupal developers, 3 junior developers, testers and a designer migrated over 10,000 content elements from SPIP to Drupal over 5 months. While the site was a success, its workflow was later deemed insufficiently flexible and its multi-node system proved ill-suited to government changes.
Learn How and Why Drupal was used for www.gouvernement.fr
- 1. LEARN WHY AND HOW DRUPAL WAS USED FOR FRENCH GOVERNMENT WEB SITE By Maxim TOPOLOV (@mtopolov) CTO at Adyax (@adyaxcorp)
- 2. 60 awesome Drupal sites in 2010…IPAD CMS (Open Source)55 Drupal experts, 3M€ of revenue
- 3. www.gouvernement.fris THE site of THESE persons
- 4. Prime MinisterFrançois FillonGeneral Secretary(SGG)Serge LasvignesSIG DirectorVéronique MélyThe site ismanaged by the GovernementInformationalService
- 5. Before 2009 URL waspremierministre.gouv.frand site looked… outdated
- 6. And wasusing SPIP as CMS
- 7. SPIP isactuallysomething as French
- 8. SPIP isactuallysomething as FrenchAs this…
- 9. SPIP isactuallysomething as FrenchAs this…This…
- 10. SPIP isactuallysomething as FrenchAs this…This…Or THIS
- 11. … but not as tasty
- 12. Known and supported by few people
- 13. So in early 2009 decisionwas made to :Move to new CMSChange URL to www.gouvernement.fr
- 19. Drupal wasfinallyselectedbecause of…ModularityFlexible dataWorkflowTemplating
- 20. Drupal wasfinallyselectedbecause of…ModularityImagesFlexible dataWorkflowTemplating
- 21. Drupal wasfinallyselectedbecause of…ModularityImagesFlexible dataWeb ServicesWorkflowTemplating
- 22. Drupal wasfinallyselectedbecause of…ModularityImagesFlexible dataWeb ServicesWorkflowTemplatingRoles & permissions
- 23. THE DREAM TEAM :
- 24. THE DREAM TEAM :1 Project Manager (Yves CHEDEMOIS)
- 25. THE DREAM TEAM :1 Project Manager (Yves CHEDEMOIS)3 Senior Drupal developers (ADYAX)
- 26. THE DREAM TEAM :1 Project Manager (Yves CHEDEMOIS)3 Senior Drupal developers (ADYAX)3 Junior / not Drupal developers (SIG)
- 27. THE DREAM TEAM :1 Project Manager (Yves CHEDEMOIS)3 Senior Drupal developers (ADYAX)3 Junior / not Drupal developers (SIG)2 Testers (SIG)
- 28. THE DREAM TEAM :1 Project Manager (Yves CHEDEMOIS)3 Senior Drupal developers (ADYAX)3 Junior / not Drupal developers (SIG)2 Testers (SIG)1 Designer (SIG)
- 29. Hard part : content migration. 10.000 elements (articles, photos, …)
- 30. No structured content in SPIP
- 31. Hard-codedURLs
- 32. SPIP internal codes (likeBBCodes)Hard part 2 : no clearspecifications, no final decisions, changes occuroften.
- 33. Hard part 3 : HIGH PRESSURE !
- 34. Simple organisation :Everydecisioniswritten & validatedSCRUM basedprojectLearn to be HARD and say NO1 persondedicated to migration
- 35. Used Tools : SVN (Source Control)
- 36. Redmine (Project Management)
- 37. Hudson (Deployment system)
- 38. Selenium RC (Automated test)
- 39. Drupal (heh)
- 40. Over-time-hours (many)5 months of hard work
- 43. Power of taxonomies & menus…
- 45. Apache SOLR for Searches
- 46. Biggest bug : Select * fromnodewhere type = ‘ministre’;Without… AND published = 1
- 47. But, workflow doesn’tfit contributorsneeds.Weneed to add more flexibilitylike flags, holydays support…
- 48. And the multi node system forGovernment composition is notAdapated to gov changes…
- 49. After a yearwithout Adyaxexperts, Acquiadid an audit…… and globally no hugeproblemswerefound.
- 52. Enjoyed ? Seeyouat16h00for mynext session to learnhow to handle20 millionsconnected page views per DAYwithDRUPAL