Paid affiliate advertisement

Themer to convert a PSD to D6 theme (zen-based, ideally)

leenwebb - October 27, 2009 - 20:08

We develop a lot of sites in Drupal, and we have been doing all of our own theme coding. But we're busy (!), so we're looking for someone who can take these PSDs and convert them to nice friendly D6 themes for us.

Overall Attitudinal and Philosophical stuff:

  • You must be fastidious with your coding. By this we mean "anal and/or perfectionist". If your friends/partners/etc regularly watch you do something and say, "OMG IT'S FINE" but you just have to tweak *one more thing*, you're our kind of people.
  • The final product should look exactly like the PSD.

Drupal stuff:

  • We'll give you a PSD and a dump of our drupal DB (and a list of modules used). The front page of this site could be done with a separate page-front.tpl or it could be done with blocks. The main content pages have pretty simple styling, and there's a sidebar with styled blocks in it as well.
  • We generally base our themes on Zen (though we're open to other themes if you have good reason)
  • We know that websites always change, and 3 months from now my client is going to want to add another XYZ to the site. Therefore it's very important to make CSS that is flexible and re-usable. For example: we love to use the block_class module so that we can give a block a class of "green-outline" rather than apply the green outline style to block-user-0 -- it is much easier to reuse the "green-outline" class on new content than to go find the block name and add it to the CSS.
  • NO separate Drupal admin theme! We want the site theme to function as the admin theme as well.

XHTML/CSS stuff:

  • All XHTML and CSS must be commented and have class and id names that are intuitive and make sense (like, real words and stuff).
  • XHTML markup must be as flexible as possible, using table-less layouts whenever possible.
  • XHTML 1.0 transitional or better, validated by W3C.
  • The code itself should be indented/nested for easy reading.
  • Rollovers (or images with multiple states) should use one image file with multiple positions.

CSS stuff:

  • Needs a nice-looking print.css, though it doesn't have to match the site exactly.
  • classes and ids must be commented, with a table of contents at the top of each css file.

We do a lot of work with agencies that require sites to be Section 508 compliant:

  • title tags are needed for non-text, non-img, or non-labelled information
  • always use alt tags in images
  • the site score for the Functional Accessibility Evaluator (http://fae.cita.uiuc.edu/) needs to be "Almost Complete" or better.
  • data row headers must be th tags

Sites need to work and look perfect in:

  • Firefox 2 and 3
  • IE7, IE8
  • Safari
  • Opera
  • Google Chrome
  • Drupal administration needs to work and look good in all of the above except Safari.

Sites need to look decent and be functional in: IE6. That is the pits, but such is life.

Sorry for being so detailed up there, but we're looking for someone that we can form a relationship with and work with over lots of projects.

We *prefer* fixed-price contracts, but we understand if you can't fix a price until you've done a couple of sites "our way". Please email me with questions/estimates/etc.

Thanks,
Eileen

 
 

Drupal is a registered trademark of Dries Buytaert.