Relaunching the website


Published on

A talk I gave at Drupal Focus on Publishing on re-launching the website notes on the liveblog at

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
  • Brief overview of how we did it and how it has progressed since I’m not a designer but I did find out lots of powerpoint animations to try and make it more exciting! Stop at any point for questions!
  • Launched First Iteration had about 3 pages For a site which was
  • External agency - good at the time as no in house development time but any updates took a long time to action Unknown CMS - no dev team knowledge so couldn’t help Poor SEO - not thought about during development, URLs, duplicate content issues Cost Didn’t do what we needed - not news focussed enough
  • Small in house team - mixture of contract and permanent staff 3½ month build - commercial constraints to launch for Look show Agile - respond to feedback, no set requirements Sprints - 2 week cycles to be responsive
  • Why Drupal for business? Lots of things business looks for when chosing platforms Established - since 2001 Modular - 100’s of contributed modules Community - online, in person, meet ups - IPC goes Support - Paid if wanted (qhich business likes), Acquia (Dries) Adub (Django) Publishing - Econnomist, Turner, BBC, CNN, UN, MTV, IPC Experimental - For us anyway, first IPC internal end to end Drupal project, always want to be trying new things not getting stuck with the old
  • Not an agile presentation but we may be hosting an Agile in Publishing day soon so grab me after if you’re interested Big part of IPC, the way we run BAU and projects now no more Waterfall! Stand ups - communication communication communication
  • User stories are business not technical focussed Best analogy from Peter Brady (Lead Dev on the build) when you’re building a house you don’t build the kitchen first because when you come to build the bathroom you have to rip all the plumbing out and start again. Annoy some agile people but when you’re building from scratch you don’t want to be refactoring every week
  • Very important as this is what drives the url structure and the layout of the sites and it’s one thing we concentrated on from the start Not just for deleting parts of the URL though, helps Google characterise the site
  • Drupal is excellent for this, easily add/remove modules, try out new designs back to agile - not fixed Usability
  • Basic Content Types - Have to start somewhere User Admin - a site is no use if you can’t log in Taxonomy - Categorisation of content Path - SEO friendly URLs
  • CCK - Content Construction Kit allows you to easily produce different content types without any programming Image and ImageCache - Easy uploading, resizing and viewing of images combined with ImageCache to dyanmically resize and cache these images Views - Custom lists and queries Path Auto - Create urls based on node title GA - Build a site but need to track it!
  • Very little custom work to do Competitions - very important, secure data capture, integrate to back of house systems PDM/Marketing IPC - Pagination, node gallery
  • The two most important things to the business at launch - on time and on budget! Can’t give Drupal all the credit as In had a fantastic team working on the project and full editorial support Fast - very, very quick Doubled page impressions in the first hour Number one for fashion - we can claim this as that’s where we are in Google, part down to
  • Every site has bugs when you launch but agile lets you solve that Performance - no master slave replication this makes sysadmin unhappy and then they pester me - don’t know if you’ve been on the receiving end of a sysadmin on call but it’s not fun Rather than reinvent the wheel we just installed pressflow and it comes out of the box Cache router issues - form caching problems, APC - went to community for help and found answer
  • Editorial love it Developers like it but mindset change - can’t just drop any developer in to it, either bring in Druapl expereince but be careful!
  • Bricks are great for building houses but you wouldn’t build a boat out of them
  • Relaunching the website

    1. 1. Relaunching The Website <ul><li>Tom Singer </li></ul><ul><ul><li>Connect/Southbank Technical Team Lead </li></ul></ul><ul><ul><li> </li></ul></ul><ul><ul><li> </li></ul></ul><ul><ul><li>Notes on liveblog (via Drupal Radar ) </li></ul></ul>
    2. 2. First Iteration
    3. 3. First Redesign <ul><li>It was great: </li></ul><ul><li>New look </li></ul><ul><li>Articles </li></ul><ul><li>Galleries </li></ul><ul><li>Videos </li></ul><ul><li>Lots of advertising opportunities </li></ul>
    4. 4. Second Redesign <ul><li>Key principles: </li></ul><ul><li>Small in house development team </li></ul><ul><li>3½ Month Build </li></ul><ul><li>Agile </li></ul><ul><ul><li>Respond to change </li></ul></ul><ul><ul><li>Communication </li></ul></ul><ul><ul><li>Sprints </li></ul></ul>
    5. 5. Framework
    6. 6. Why Drupal? <ul><li>Established </li></ul><ul><li>Modular </li></ul><ul><li>Community </li></ul><ul><li>Support </li></ul><ul><li>Publishing </li></ul><ul><li>Experimental </li></ul>
    7. 7. The Build <ul><li>Stock Drupal </li></ul><ul><ul><li>It just works </li></ul></ul><ul><ul><li>Don’t hack the core </li></ul></ul><ul><li>Agile </li></ul>
    8. 8. Agile <ul><li>User stories </li></ul><ul><li>Burndown </li></ul><ul><li>Small documentation </li></ul><ul><li>Respond to change </li></ul><ul><li>Driven by the business </li></ul><ul><li>Stand ups </li></ul>
    9. 9. Not Agile <ul><li>Blended User Stories </li></ul>
    10. 10. Information Architecture <ul><li>Very important </li></ul><ul><li>/celebrity/rihanna/pictures </li></ul><ul><li>/celebrity/rihanna </li></ul><ul><li>/celebrity </li></ul>
    11. 11. Prototyping
    12. 12. Core Modules <ul><li>Basic Content Types </li></ul><ul><li>User admin </li></ul><ul><li>Taxonomy </li></ul><ul><li>Path </li></ul>
    13. 13. Acquia Modules <ul><li>CCK </li></ul><ul><li>Image </li></ul><ul><li>ImageCache </li></ul><ul><li>Views </li></ul><ul><li>Path Auto </li></ul><ul><li>Google Analytics </li></ul>
    14. 14. Extra Modules <ul><li>Node Gallery </li></ul><ul><li>Cache Router </li></ul>
    15. 15. Custom Modules <ul><li>Competitions </li></ul><ul><li>IPC </li></ul>
    16. 16. Launch <ul><li>On time! </li></ul><ul><li>On budget! </li></ul><ul><li>Fast </li></ul><ul><li>Doubled page impressions </li></ul><ul><li>Number one for fashion </li></ul>
    17. 17. Post Launch Issues <ul><li>No master slave replication :( </li></ul><ul><li>Pressflow </li></ul><ul><li>Cache Router </li></ul>
    18. 18. Feedback
    19. 19. Drupal for Publishing
    20. 20. Photos <ul><li> </li></ul><ul><li> </li></ul><ul><li> </li></ul><ul><li> </li></ul>