Goin' mobile. shh, we're talking.


Even though Shannon and I are complete plebes in the mobile world (our ginormous flip phone may be able to do text messaging... we're too scared to try), we still need to keep up with the rest of the world. So, with that in mind, I set out to make a more friendly version of the website for those who have entered the 21st century.

Before starting, I made a list of requirements:

  • HTML5 framework (there's no going back)
  • Same source (I didn't want to maintain two versions of the same content).

Pretty simple. I looked at that, thought about it for a while, and figured that was about it. Off to drupal.org!

Because our site is pretty light already, I decided having a separate install at a subdomain was overkill. And it saves us from having to publish twice. Efficiency and laziness - two sides of the same coin.

So, the obvious choice was Mobile Tools. There are still some issues with the D7 version (specifically, I wrestled with this one), but after some fiddling it all got sorted out. 

The next question was redirect or link. I'd rather give people the choice of which site to browse, so I opted for a link rather than a redirect that wrestles control from you and pushes you into the corner I think you want to go into. I don't really like confrontation.

The next step was to choose / create a theme. I looked at the offerings on drupal.org and decided that none really fit the bill. What I wanted was something with the features of HTML5 Mobile Boilerplate, the excellent Boron (which we used as the initial framework for the main site) and a few things from Basic (mainly phptemplate functions that identify unpublished nodes, give additional suggestions based on node type and path and a few other little goodies). The final theme used Mobile Basic as a jumping off point, then we added the templates from Boron for consistency and wedged in the features we wanted from HTML5 Mobile Boilerplate and Basic. I'm pretty happy with the result.

The only other steps were to fix the CSS, make the images resizable (using the img { max-width: 100%; height: auto; } trick, and decide what to exclude. 

I'll be making the theme available at drupal.org soon.

And, since Shannon won't let me buy all the new devices I need and I feel creepy lingering around at Future Shop testing, let me know if you find anything awry.