
This week's Weekly Drupal is about themes. We've been working with Drupal now for just under 3 months, migrating a flagship site plus 70 affiliate sites into the system as per this page. So, I'm a relative newbie to Drupal.
One of our big tasks in the next few months is to prepare some prototypes of possible new layouts for the homepage of our flagship site. We want to showcase them at our big annual meeting. Yeah, I know what you're thinking: "you're redesigning your site while migrating it to Drupal!" Not exactly. We have an information architecture re-design process running in parallel to our Drupal implementation and migration. Basically, we need to migrate our sites into the system as is and then we can begin to roll out design changes, new features, etc.
So, themes. Well, I'm surely not the only one that finds browsing for themes on drupal.org less than optimal. For instance, I would love to be able to browse by layout style (top tabbed navigation, etc.) and features (supports x or y, is x or y compliant, etc.). So, when I discovered the Theme Garden, I was ecstatic.
The Theme Garden is a site that lets you browse through Drupal themes based on version with the content staying the same - it's the same site - but you can see how the various elements are laid out and displayed. Brilliant. Especially as I'd imagine many folks "shopping" for a Drupal theme have already done wireframing exercises and mockups and pretty much know what they are looking for, the just need to "see" it.
I can also highly recommend reading the Drupal 6 theme guide on drupal.org. One question I have relates to the use of sub-themes. If, for example, we have one flagship site using one theme and some 70-odd affiliate sites using a slight variation on this same theme, it seems we should use sub-themes for the affiliate sites, no? This way the affiliate sites' theme will inherit the style sheets, Javascripts, template files, etc. from the "main" theme or parent theme. What are the advantages and disadvantages of having the subsites use their own theme versus a sub-theme? I'll have to think about that one...
So, for now, our plan is to create 4 different prototype homepages made by choosing 4 Drupal 6 themes and altering them for our purposes. In theory, if all goes well, one of these prototype sites/themes will later become our new site theme. Again, since we're re-building our current theme and site in Drupal already, we'll have to migrate one of these themes into our existing site when we're ready to go live with the changes. First, on our test site and then on the live site. But, we're a long way away from that move. First, we have to get Drupal managing our sites and their content.
The Weekly Drupal is a weekly column on mavergames.net about Drupal from the perspective of a new user. Use this feed to subscribe.
All free Drupal themes
By Michael (not verified)I agree. Searching for themes on the Drupal.org site is a total pain. Theme Garden is an improvement, but it's tedious going from one page to the next, just to see each theme. That's why I created a page that allows people to see all of the free themes on a single page: http://www.ross.ws/themes
Looks nice
By mavergamesWill check out your site. Thanks for the tip.Cheers,Chris
Why am I allowed to post
By Anonymous (not verified)Why am I allowed to post JavaScript? You should fix your input formats, read http://heine.familiedeelstra.com/input-formats-beware
Thanks!
By Chris (not verified)For the heads up on input formats...Still new to Drupal and sorting out permissions, security issues, etc.Cheers,Chris
"Yeah, I know what you're
By Brian Egan (not verified)"Yeah, I know what you're thinking: 'you're redesigning your site while migrating it to Drupal!'"Why is this the general consensus? I've seen this said a lot throughout the Drupal community, but I haven't really heard an ellaboration on this point. As my organization moves to Drupal we've decided to reorganize our IA and create a new design to fit that new IA. Our old site is a total mess, content is out of date, IA is basically non-existent, and there are a number of services we can collapse into Drupal modules + Views/CCK/Taxonomy goodness. Why do people fear a redesign when moving to Drupal? Isn't importing a rusty old site into Drupal just a lot of wasted work?Should I be afraid?Thanks for the info! Brian Egan
Reply
By mavergamesHi Brian,
Huh, I didn't really know it was necessarily said a lot around the Drupal community. It's just been my experience with CMSes generally, and I have always heard/read that it is best practice when implementing CMSes to either redesign your site and then migrate to a new CMS or migrate and then redesign but not at the same time as it can be headache-y.
Of course, in practice, I think many people, me included, are taking advantage of quick and obvious fixes that a new CMS can bring. We are also taking advantage of some "Views/CCK/Taxonomy goodness" as well as the rich RSS aggregation offerings in Drupal. I just think one has to have a pretty good idea of what one wants visually and IA-wise either before or after programming and configuring a new CMS. That's all. If you do, then do it simultaneously if you can :-)
Cheers,
Chris
Post new comment