DrupalCon Chicago 2011 ReportBack (11/03/30 - G. Bedford)


Published on

Reportback on some of the happenings at DrupalCon 2011 from a delegates perspective!!

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
  • NB keynote summary, day stage summary
  • DrupalCon Chicago 2011 ReportBack (11/03/30 - G. Bedford)

    1. 1. Drupalcon Chicago Feedback from the Conference (proof that I actually went) Guy Bedford
    2. 2. Drupalcon <ul><li>3000 attendees </li></ul><ul><li>86 sessions </li></ul><ul><li>24/7 bof rooms </li></ul><ul><li>4,500 wifi devices </li></ul><ul><li>Ignite talks at the day stage </li></ul>
    3. 7. Made with Wordle.com
    4. 10. A (brief) history of Drupal <ul><li>It started as a message board in 1999 at the University of Antwerp </li></ul><ul><li>Soon turned into an experimental platform </li></ul><ul><li>Technologies like moderation, syndication and rating </li></ul><ul><li>Dries was a Java programmer, php was better for keeping it open </li></ul>
    5. 11. <ul><li>551,392 people in 228 countries </li></ul><ul><li>1.7% of websites run Drupal, based on crawler samples of over 100 million sites </li></ul><ul><li>1000+ core contributors, 7000+ modules </li></ul><ul><li>Over 5m visits on Drupal.org monthly </li></ul><ul><li>130k unique visitors each day </li></ul><ul><li>Higher job growth than Wordpress </li></ul><ul><li>“ Drupal is uniquely positioned to be the </li></ul><ul><li>dominant platform for the web” </li></ul><ul><ul><ul><ul><ul><li>-Dries </li></ul></ul></ul></ul></ul>
    6. 12. Tsunami (Snowman) <ul><li>Describes 3 pain points: UX, Api (web services, context), Deployment (better exporting, uuids) </li></ul><ul><li>Argues for framework and product separation </li></ul><ul><li>This to be a new product profile - groups.drupal.org/snowman </li></ul>http://angrylittletree.com/11/01/drupal-8-road- ahead
    7. 13. Dries D8 Initiatives <ul><li>Spoke with many companies about Drupal pain points: Configuration Management, Content Staging, UUIDs and Exportables </li></ul><ul><li>3 year release cycle from D6 to D7 </li></ul><ul><li>Initiatives for D8: Multi-device publishing, Interoperability, Delightful experience, Configuration management, Content staging </li></ul>
    8. 14. Keynote: Clay Shirky Author of: Here comes everybody, Cognitive Surplus
    9. 15. Clay Shirky Keynote <ul><li>Communication between users trumps communication from broadcasters </li></ul><ul><li>Yet we still use old media terms: pc as user, audience from tv and radio </li></ul><ul><li>Exceptional users are the norm </li></ul><ul><li>We’re building communities and initiatives experimentally </li></ul><ul><li>Sites create context </li></ul><ul><li>We’re still figuring out the bigger solutions of pooling resources. Drupal is one of the tools. </li></ul>
    10. 16. Keynote: Jared Spool The unintuitive nature of intuitive designs
    11. 17. The unintuitive nature of intuitive designs <ul><li>Example - Avis website had a form with the asterisk next to the middle name and second address line. </li></ul><ul><li>Good reason, but unintuitive! </li></ul>
    12. 18. <ul><li>Intuitive design is invisible </li></ul><ul><li>It’s personal </li></ul>The unintuitive nature of intuitive designs Current Knowledge Target Knowledge
    13. 19. Target Knowledge < Current Knowledege Target Knowledge > Current Knowledge The unintuitive nature of intuitive designs
    14. 20. <ul><li>Natural product evolution: tech -> features -> experience </li></ul><ul><li>Bring up current knowledge through training </li></ul><ul><li>Lower target knowledge by simplifying the design </li></ul><ul><li>“Watch users interacting with your design at least 2 hours every 6 weeks” </li></ul><ul><li>Change disrupts current knowledge </li></ul>The unintuitive nature of intuitive designs
    15. 21. Mobile
    16. 22. Mobile “ Starting from scratch today, Drupal would be designed for mobile first and desktop second” - Dries
    17. 23. jQuery Mobile <ul><li>Create touch-optimised native-looking apps for the mobile web to work across many devices </li></ul><ul><li>Ajaxes requests with css transitions </li></ul><ul><li>NOT production ready, but one to watch </li></ul><ul><li>drupal.org/project/jquerymobile </li></ul>Demo: http://tha.cm/jqm-demo http://tha.cm/jqm-proj ects
    18. 24. Native Mobile Apps <ul><li>Using Titanium - code in JavaScript </li></ul><ul><li>Plug in with Drupal Services API json/xml API for CMS operations: login, registration, loading content etc. </li></ul><ul><li>http://drupal.org/project/services </li></ul><ul><li>http://civicactions.com/blog/sumit </li></ul><ul><li>Other options: mobify </li></ul>
    19. 25. From Zero to Distribution <ul><li>Drush Make: creates a site from a makefile </li></ul><ul><li>Downloads code (custom or modules) and applies them </li></ul><ul><li>Allows for creating ‘install profiles’ </li></ul>
    20. 26. Leaner techniques for faster websites <ul><li>PHP does garbage collection, costs cpu to manage </li></ul><ul><li>Drupal has heavy memory use </li></ul><ul><li>Use unset function to remove large allocations </li></ul><ul><li>Use lean data structures </li></ul>Memory
    21. 27. Leaner techniques for faster websites <ul><li>Static variable cache http://www.lullabot.com/articles/a-beginners-guide-to-caching-data </li></ul><ul><li>Memcache </li></ul><ul><li>Exportable config (ctools). Allows for sharing static variables with other modules </li></ul><ul><li>Avoid n+1 queries </li></ul>Database
    22. 28. Leaner techniques for faster websites <ul><li>APC </li></ul><ul><li>Minimal number of source files </li></ul><ul><li>Can specify file names in hooks </li></ul><ul><li>Wait to include a function when it’s needed - move 90% into not executed on pageload </li></ul><ul><li>In D7, hook_hook_info allows grouping and informing of includes </li></ul>Source Files
    23. 29. Design in the Browser <ul><li>Clients find it easier to review a working prototype than a photoshop file </li></ul><ul><li>Easier to make some changes </li></ul><ul><li>Stops last minute panic </li></ul><ul><li>Play in CSS in combination with PS </li></ul><ul><li>Modernizr, Selectivizr (ie css3!), Sass, Compass, xrefresh, live reload </li></ul>http://www.thecodingdesigner.com
    24. 30. Drupal Certifications <ul><li>Reputation </li></ul><ul><li>Helps customers </li></ul><ul><li>Helps new ‘drupalistas’ </li></ul><ul><li>Cost a lot to run and take </li></ul><ul><li>Can promote insiders </li></ul><ul><li>Can create wasted work by unrelated organisations </li></ul>Benefits Issues
    25. 31. Certifications History <ul><li>Acquia announced plans in April 2008 </li></ul><ul><li>NobleProg, Gloscon have announced in 2008. Not running. </li></ul><ul><li>oDesk started a Drupal test in March 2009, but this is outdated </li></ul><ul><li>Certified to Rock (April 2010) </li></ul>
    26. 32. The Story of Lullabot <ul><li>Started as a consulting company, not a development company </li></ul><ul><li>Helped companies with developers in Drupal </li></ul><ul><li>Technical architecture, support with lullabot people, developers and communicators </li></ul><ul><li>Training was the next logical step </li></ul><ul><li>And online training from that: drupalize.me </li></ul>
    27. 33. Certification thoughts from Lullabot <ul><li>Lots of varying skills around Drupal, always changing </li></ul><ul><li>Basic certification ignores that - it is more valuable to an outsourcing company, which is not the sort of company they want to be </li></ul><ul><li>Training should focus on empowerment, creating light bulbs </li></ul><ul><li>Simple things like ‘go to your Drupal meetup’ and how to Google! </li></ul>
    28. 34. Introductions Nathan Haug quicksketch Ryan Szrama Ryan Daniel Kudwein sun
    29. 36. Winning with the ecosystem <ul><li>Ecosystems needed for Drupal - Drupal shops, specialist services. </li></ul><ul><li>Lack of talent is the number one obstacle for Drupal adoption worldwide. </li></ul><ul><li>Hire as many people as you can, train them (in only Drupal), and ultimately specialise to get better rates and differentiate yourself. </li></ul>“ The battle of devices has now become a war of ecosystems. Our competitors aren’t taking our market share with devices; they are taking our market share with an entire ecosystem.” - Stephen Elop, CEO Nokia