Learn How and Why Drupal was used for www.gouvernement.fr

2,886 views

Published on

Gouvernement.fr is the main web site of french government. Decision was made to go on Drupal.

Published in: Technology
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
2,886
On SlideShare
0
From Embeds
0
Number of Embeds
2
Actions
Shares
0
Downloads
13
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide

Learn How and Why Drupal was used for www.gouvernement.fr

  1. 1. LEARN WHY AND HOW DRUPAL WAS USED FOR FRENCH GOVERNMENT WEB SITE <br />By Maxim TOPOLOV (@mtopolov) CTO at Adyax (@adyaxcorp)<br />
  2. 2. 60 awesome Drupal sites in 2010…<br />IPAD CMS (Open Source)<br />55 Drupal experts, 3M€ of revenue<br />
  3. 3. www.gouvernement.fris THE site of THESE persons<br />
  4. 4. Prime Minister<br />François Fillon<br />General Secretary(SGG)<br />Serge Lasvignes<br />SIG Director<br />Véronique Mély<br />The site ismanaged by the GovernementInformationalService<br />
  5. 5. Before 2009 URL waspremierministre.gouv.fr<br />and site looked… outdated<br />
  6. 6. And wasusing SPIP as CMS <br />
  7. 7. SPIP isactuallysomething as French<br />
  8. 8. SPIP isactuallysomething as French<br />As this…<br />
  9. 9. SPIP isactuallysomething as French<br />As this…<br />This…<br />
  10. 10. SPIP isactuallysomething as French<br />As this…<br />This…<br />Or THIS<br />
  11. 11. … but not as tasty<br />
  12. 12. Known and supported by few people<br />
  13. 13. So in early 2009 decisionwas made to :<br />Move to new CMS<br />Change URL to www.gouvernement.fr<br />
  14. 14.
  15. 15. Drupal wasfinallyselectedbecause of…<br />
  16. 16. Drupal wasfinallyselectedbecause of…<br />Modularity<br />
  17. 17. Drupal wasfinallyselectedbecause of…<br />Modularity<br />Templating<br />
  18. 18. Drupal wasfinallyselectedbecause of…<br />Modularity<br />Workflow<br />Templating<br />
  19. 19. Drupal wasfinallyselectedbecause of…<br />Modularity<br />Flexible data<br />Workflow<br />Templating<br />
  20. 20. Drupal wasfinallyselectedbecause of…<br />Modularity<br />Images<br />Flexible data<br />Workflow<br />Templating<br />
  21. 21. Drupal wasfinallyselectedbecause of…<br />Modularity<br />Images<br />Flexible data<br />Web Services<br />Workflow<br />Templating<br />
  22. 22. Drupal wasfinallyselectedbecause of…<br />Modularity<br />Images<br />Flexible data<br />Web Services<br />Workflow<br />Templating<br />Roles & permissions<br />
  23. 23. THE DREAM TEAM :<br />
  24. 24. THE DREAM TEAM :<br />1 Project Manager (Yves CHEDEMOIS)<br />
  25. 25. THE DREAM TEAM :<br />1 Project Manager (Yves CHEDEMOIS)<br />3 Senior Drupal developers (ADYAX)<br />
  26. 26. THE DREAM TEAM :<br />1 Project Manager (Yves CHEDEMOIS)<br />3 Senior Drupal developers (ADYAX)<br />3 Junior / not Drupal developers (SIG)<br />
  27. 27. THE DREAM TEAM :<br />1 Project Manager (Yves CHEDEMOIS)<br />3 Senior Drupal developers (ADYAX)<br />3 Junior / not Drupal developers (SIG)<br />2 Testers (SIG)<br />
  28. 28. THE DREAM TEAM :<br />1 Project Manager (Yves CHEDEMOIS)<br />3 Senior Drupal developers (ADYAX)<br />3 Junior / not Drupal developers (SIG)<br />2 Testers (SIG)<br />1 Designer (SIG)<br />
  29. 29. Hard part : content migration.<br /><ul><li> 10.000 elements (articles, photos, …)
  30. 30. No structured content in SPIP
  31. 31. Hard-codedURLs
  32. 32. SPIP internal codes (likeBBCodes)</li></li></ul><li>Hard part 2 : no clearspecifications, <br />no final decisions, changes occuroften.<br />
  33. 33. Hard part 3 : HIGH PRESSURE !<br />
  34. 34. Simple organisation :<br />Everydecisioniswritten & validated<br />SCRUM basedproject<br />Learn to be HARD and say NO<br />1 persondedicated to migration<br />
  35. 35. Used Tools :<br /><ul><li> SVN (Source Control)
  36. 36. Redmine (Project Management)
  37. 37. Hudson (Deployment system)
  38. 38. Selenium RC (Automated test)
  39. 39. Drupal (heh)
  40. 40. Over-time-hours (many)</li></li></ul><li>5 months of hard work<br />
  41. 41. And somemagiclater…<br />
  42. 42. www.gouvernement.frwas HERE !<br />
  43. 43. Power of taxonomies & menus…<br />
  44. 44. Brightcove for videos<br />
  45. 45. Apache SOLR for Searches<br />
  46. 46. Biggest bug : <br />Select * fromnodewhere type = ‘ministre’;<br />Without<br />… AND published = 1<br />
  47. 47. But, workflow doesn’t<br />fit contributorsneeds.<br />Weneed to add more flexibility<br />like flags, holydays support…<br />
  48. 48. And the multi node system for<br />Government composition is not<br />Adapated to gov changes…<br />
  49. 49. After a yearwithout Adyax<br />experts, Acquiadid an audit…<br />… and globally no hugeproblems<br />werefound.<br />
  50. 50. Any question ?<br />@mtopolov<br />@adyaxcorp<br />www.adyax.com<br />
  51. 51. Thoseslides<br />Will beavailable<br />On slideshare.net<br />
  52. 52. Enjoyed ? Seeyouat16h00<br />for mynext session to learn<br />how to handle20 millions<br />connected page views per DAY<br />withDRUPAL<br />

×