Posts by theme: theming
I am primarily a themer. I am not a designer, and not programmer/engineer, whatever you want to call it. I am, however, what I like to call a “bridge”, a bridge between the design community and the heavy Drupal developer community. I have a background in art as well as business management in information systems (a.k.a. CS “lite”, for business people who can’t program) – so essentially I can talk the talk to both sides.
What I’m most excited about right now is creating themes and bringing designers and themers into the “inner circle” of Drupal without having to teach them how to use the issue queues and it was DrupalCon DC that got me here. I’m super interested in sharing my experiences with Drupal and theming as well as my best practices for doing that, thus this blog post.
I might be going a little far by continuing to call our sustainable method of theming "getting your hands dirty", but it makes me smile. So everyone will have to deal with it for at least 1 or 2 more blog posts.
On that note, I wanted to give the Drupal theming community a couple of examples of approaches we here at Palantir take for implementing a sustainable theme. I’m going to focus specifically on a very recent method we’ve implemented at Palantir for theming Views.
I am primarily a themer. I am not a designer, and not programmer/engineer, whatever you want to call it. I am, however, what I like to call a “bridge”, a bridge between the design community and the heavy Drupal developer community. I have a background in art as well as business management in information systems (a.k.a. CS “lite”, for business people who can’t program) – so essentially I can talk the talk to both sides.
What I’m most excited about right now is creating themes and bringing designers and themers into the “inner circle” of Drupal without having to teach them how to use the issue queues and it was DrupalCon DC that got me here. I’m super interested in sharing my experiences with Drupal and theming as well as my best practices for doing that, thus this blog post.

Springtime is conference season, and this year has been a pretty busy one for us at Palantir. We just got back from Museums and the Web in Indianapolis last week, and it’s already time to start getting ready for next week’s CMS Expo. Fortunately, we don’t have to travel too far this time – it’s being held in Evanston, IL, which is only a few miles from our north Chicago office and also happens to be where a few of us live. CMS Expo is a training and business conference focusing on Drupal, Joomla!, Alfresco and other open source content management products. Along with our friends at Acquia, Palantir will be one of the conference’s sponsors, and a number of us will be presenting sessions as well:
I’ve finally got enough sleep to be able to coherently organize my thoughts after an amazing week at Drupalcon DC. It actually took me 36 hours to get from DC to my new home in Taipei. But now that I’m sleeping more than 3-4 hours a night, I wanted to talk about the mind-bending experiences the Palantir Themers had last week.
Like many web developers, I’ve written a lot of applications from scratch and I inevitably got to that point where I thought, “It will be much better if I write something re-usable that will help me with any application I want to build in the future. I should write my own framework!”
And, that worked out great for a while, until I realized the fatal flaw with my idea was that I had put the emphasis on “re-usable” and had not realized the implicit “I write” part of it. Every little feature my client wants, I have to write myself. oh. joy.
So, since I was also really damn tired of having to tweak my clients’ content (“Add bike shed to the 4th paragraph and make that text blue…”), I started evaluating open-source CMSes, the usual suspects: Typo3, Mambo (soon to be Joomla), and Drupal (4.6, btw.)

It was pretty clear, coming from the I-need-a-framework mind set, Drupal was the right choice. Good code with a backwards-compatibility-leads-to-crufty-APIs attitude. And 3 years ago today, I signed up as Drupal user 32095.
And, I did get some well-written code that fixed my DIY-misadventures. But great code turned out to be the least of what I received that day. When you join the drupal community, you get people, not just code. Brilliant, funny, heart-warming, pain-in-the-ass, cheeky, supportive, cranky, witty, lovely people. So much more than what I was looking for.
So, on the third anniversary of my joining Drupal.org, let me say thank you! Thanks, everybody!
Back in June I wrote about how to theme correctly in Drupal (Sustainable Markup: How to be a themer in Drupal). At that time I was working on a new website for Graycor, a leading provider of construction, maintenance and facilities services throughout the U.S., Canada and Mexico. So much of what I wrote about in my last blog entry relates specifically to the newly launched (August 25, 2008) Graycor site.
We set 3 goals for ourselves before we started the prototype build out:
- Avoid using tpl.php files where ever possible.
- Create default CSS styling and reuse as much as possible, "Theme" don't "Skin"
- Leverage the Drupal admin everywhere we could.
And we did just that. We succeeded in reaching our 3 goals on this site.
Let me break down for you what we did...
I’ve been thinking a lot lately about how we could be doing things better and not just in the Drupal way. But Drupal is what I’ve decided to focus on first. I’ve been wracking my brain over how we can improve our process, how we can build more efficient sites faster and better for the client, and how we can give ourselves a tool kit. And then it hit me, we’ve been approaching designs in Drupal all wrong this last year. Don’t get me wrong, we didn’t do anything "wrong", we just didn’t make it easier on ourselves.
We’ve been a Drupal shop for over a year now and we are definitely still maturing our Drupal approach. We are still cutting our teeth, so to speak. And I think that we may be reinventing the wheel all too often.
