You are hereDrupalCon - Wednesday
DrupalCon - Wednesday
From an HTML/CSS Template to a Drupal Theme
This session explored how to convert a HTML/CSS template or "prototype" into a working Drupal theme. I was particularly interested in attending this session, as we had hit some stumbling blocks in this area on our last Drupal project; we had to spend a lot of time reworking our prototypes to make them into a working Drupal theme, and I was interested in others' approaches to the issue.
One of the suggestions made by the presenter, Hans Rossel, was to only create the basic framework or structure of the page first, and not to spend time creating detailed markup and CSS for the actual components, since that won't match what Drupal will provide. Very good advice.
Trellon: How Earth Day Handled 80 Million Hits in 2 Days
This was a fascinating presentation about how Trellon, having inherited the Earth Day website one week before Earth Day itself ("the largest secular holiday in the world, celebrated by more than a half billion people"), managed to make it scale to handle 80 million hits on Earth Day (which occurred over 48 hours, when you take time zones into consideration).
Originally, Trellon was not supposed to be involved in a development capacity at all, but they did some basic load testing and discovered that the Earth Day site was going to crash pretty much instantly under any load. In fact, the Earth Day website had never survived Earth Day; the logs they had from the previous year stopped at 10am, because that's when the server melted. So with just two days left, they hacked and slashed their way to a scalable solution.
The result? For the first time ever, the Earth Day website survived the onslaught intact, with an average page response time of under 4 seconds.
Keynote: Rasmus Lerdorf on PHP 5.3, and Drupal Performance
Despite the lambasting, Rasmus conceded that stuff like that was really just a drop in the bucket, and that to really improve Drupal performance, key functions (like drupal_render) would need to be re-implemented in C.
After his presentation, there was a questions period from the audience. One that in particular got probably the biggest laugh of the entire conference was "How do you stay excited about PHP after working on it for so long?" Rasmus' answer: "I've never been that excited about PHP. So it's easy to keep that level of motivation..." Rasmus views PHP as a pragmatic tool that works well enough to get the job done, and doesn't see the need to improve it, unless he personally needs it to be better.
The entire video of Rasmus' keynote can be viewed at DrupalRadar.
Met Dries Buytaert!
I happened to be sitting quite close to Dries during Rasmus' keynote, so after the presentation was completed and everyone was filing out of the auditorium, I took the opportunity to ambush Dries.
I thanked him for creating Drupal, he very modestly replied that it was really everyone else's work that had gotten Drupal to where it was today. I told him that I found his keynote speech from the previous day very inspiring, that I was glad some people were thinking so far ahead into the future.
He asked about what I'd used Drupal for, so I mentioned a couple of sites including transalta.com, then proceded to tell him about Evans Hunt and VisitCalgary.com. He suggested I submit it to be featured on Drupal.org, something I certainly plan on doing in the near future.
On the Importance of DONE: Scrum & Drupal at the Economist
This was an excellent presentation put on by The Economist, whose website is built in Drupal. It discussed their agile development approach, with a particular focus on the meaning of "done" (implemented, verified, and validated). I very much appreciated their discussion of developing individual features using Drupal on a one-at-a-time basis, which they termed "thin vertical slices". This really resonated with the approach that we've found to work best on Drupal projects. I took extensive notes on this session.
A Template Approach: Cut Your Design Time Down by 200%
Despite the mathematical impossibility of the title (which was apparently pointed out to the presenter several times by well intentioned geeks) this was a session with a title too interesting to pass up.
The session essentially focused on a Fireworks driven approach to both IA and Design, using Fireworks for "greyboxing" the IA, using a template that defines most common Drupal features that often go overlooked in a design (such as the View / Edit tabs, etc).
I took video of this session, and they also have a good webpage about these concepts up at ChapterThree.
Drupal Performance: Then, Now, & The Future
This was a presentation jam-packed with valuable information about technologies that can be used to improve the performance of your Drupal site. I took very detailed notes. The technologies covered included: Memcache, Boost, Cache Router, Auth Cache, Pressflow, Devel, Xdebug, KCachegrind, MacCallgrind, MySQL's slow query log (Tuning-primer.sh, Mk-query-digest, and Mtop), MyISAM/InnoDB, MariaDB, MongoDB, Varnish, PHP APC, and Pantheon.
Use SimpleTest!
SimpleTest is an automated functional testing suite built into Drupal 7 core, which is used to run all commits to the core codebase through a gauntlet of 23,000+ (and counting) test cases.
SimpleTest can also be used to verify the functionality of 3rd party modules, and is definitely something I want to start doing myself on my own Drupal projects to help test the project's custom code. I took video of this presentation.
An Evening on the Town
We left the bar sometime after 1am, and after parting ways with Justin and Floris I walked back to my hotel.
Post new comment