<html><body><span style="font-family:Verdana; color:#000000; font-size:10pt;">That was a very informative article. Thanks Nicolas!<br><br>
<blockquote webmail="1" style="border-left: 2px solid blue; margin-left: 8px; padding-left: 8px; font-size: 10pt; color: black; font-family: verdana;">
<div >
-------- Original Message --------<br>
Subject: Re: [consulting] Drupal-friendly Graphic Design (new subject)<br>
From: Nicolas Borda <forums@ipwa.net><br>
Date: Tue, March 10, 2009 4:47 pm<br>
To: A list for Drupal consultants and Drupal service/hosting providers<br>
<consulting@drupal.org><br>
<br>
<br>
On 10 Mar 2009, at 19:42, Eric Broder wrote:<br>
<br>
> So far I detect one main idea coming through: advise the graphic <br>
> designer on what default "out of the box" implementations look <br>
> like, possibly by building a prototype first and then telling the <br>
> graphic designer to use it as an architectural outline.<br>
><br>
> Are there other methods you might suggest? Is it helpful to give a <br>
> graphic designer a list of readily available variables to play <br>
> around with? Or to present a choice of basic layout structures that <br>
> are easy to implement in Drupal?<br>
<br>
<br>
I would suggest reading this great article<br>
by Young Hahn:<br>
<br>
<a href="http://www.developmentseed.org/blog/2009/mar/01/limitations-drupal-" target="_blank" mce_href="http://www.developmentseed.org/blog/2009/mar/01/limitations-drupal-">http://www.developmentseed.org/blog/2009/mar/01/limitations-drupal-</a> <br>
theme-layer<br>
(<a href="http://tinyurl.com/bvhwat" target="_blank" mce_href="http://tinyurl.com/bvhwat">http://tinyurl.com/bvhwat</a>)<br>
<br>
In this article he point out three common<br>
"mistakes" designers make when designing<br>
Drupal themes:<br>
<br>
1. Moving something out of its vertical stack.<br>
2. Changing the formatting of a core element.<br>
3. Expecting visual consistency across different modules.<br>
<br>
I think he makes very valid point in this<br>
article. I used to tell designers to make<br>
any design they want and I would be able<br>
to theme it, and use to design myself with<br>
that principle. I have learned that although<br>
most things can be done, like Young says<br>
some things can be hard to do, hard to<br>
maintain, and can be done with Drupal<br>
friendly alternatives. Is it really in your client's<br>
best interest having things in the design that<br>
will be costly, when you can provide<br>
alternatives that will look just as good and<br>
be less expensive to theme. I guess it also<br>
depend on the budget and the brief for the<br>
project.<br>
<br>
<br>
_______________________________________________<br>
consulting mailing list<br>
consulting@drupal.org<br>
<a href="http://lists.drupal.org/mailman/listinfo/consulting" target="_blank" mce_href="http://lists.drupal.org/mailman/listinfo/consulting">http://lists.drupal.org/mailman/listinfo/consulting</a><br>
</div>
</blockquote></span></body></html>