The CSS Wizardry build-along is go!

Written by Harry Roberts on CSS Wizardry.

Okay, so you decided it wouldn’t be boring and that I’m not big-headed in thinking that people might actually want to watch me coding, so I’m quite excited to announce that the build-along will be going ahead!

Entry is now closed. Thanks all who sent in a PSD, watch this space for a launch article.

Obviously there need to be some terms and conditions. Apologies if these seem a little harsh(ly worded) but they are as follows:

• PSDs only. Sorry, I don’t work with Fireworks enough to make me quick enough for this type of exercise.

• The PSD I choose is my choice. I am only doing one and it’ll most likely be one that’s fun but not mountains of work; I need to be able to do it in a night.

• CSS and HTML only. No Javascript as I don’t know Javascript; you would not want me even attempting it!

• The code I provide will be final. Progressive enhancement will be used, it won’t look the same in every browser, you won’t get to make any change requests or ask for bug fixes after the fact. Naturally I’m going to do a good job, you won’t end up with any messy code, but as this is entirely free I can’t take instruction.

• If you’re, for whatever reason, unhappy with the outcome I’m afraid you’re stuck with it… Whether the final page goes into production or not is entirely up to you.

• The PSD must be all above board; I won’t be building you a new adult dating site ;)

• This one is entirely your responsibility but I strongly advise you are fully transparent if your PSD will be sold on to a client. I have no qualms with you making a profit on my work but make sure your client is cool with it, especially when their site design will be being made totally public.

I’m keen to keep this as informal as possible, but the format will take:

1. If you want me to build your PSD please email a full-size JPG of your design by Wednesday 2 November 2011 to harry at csswizardry dot com with the subject line Build-along. This subject line is vital as I’m going to set up a Gmail rule to group stuff. Any non-conforming emails might get overlooked.

2. I’ll look at the JPGs and choose one to build. I’ll announce the person I choose in a blog post and also email them directly, at which point they reply with their actual PSD file. If your PSD didn’t get chosen then I will not email you I’m afraid; that’d take forever!

3. The PSD must be properly constructed. I don’t want to be battling with any Layer 12 Copy 4 v2 stuff!

4. Make sure you provide any font-files or Typekit etc information if your design uses them.

5. I’m most likely going to be building the PSD on Friday 4 November 2011. The reason for this is that if it keeps me up into the early hours then I’d rather that was on a weekend rather than a work-night. This does mean that if you want to follow along then you’ll have to be in on a Friday evening, no pub!

6. I’ll announce the URL in a blog post and Twitter, you can follow along live.

7. The code will be getting committed to GitHub, too, so make sure you’re okay with that!

This all seems a bit formal, I realise, but it really won’t be. I just need to make sure I have all the stuff in the right place at the right time!

Pop any questions in the comments and I’ll update the post as necessary. Please hashtag any and all tweets about the event with #buildAlong.

So, in summary:

1. Get a nice, neat, tidy PSD together.

2. Send me a JPG of it as per the exact email rules.

3. I’ll announce whose PSD I’ll be building in a blog post.

4. Be around at about 7pm UTC (Dublin, Edinburgh, Lisbon, London) on Friday 4th November to watch along as I code.

5. You will get a HTML/CSS single page template emailed back to you once it’s done.

Right, get emailing me!

Update

While there are loads of you interested in watching this event, no one has sent in a PSD. Not one! Mention this to friends, your boss, your designer, anyone. Without a PSD the build-along can’t run :(

By Harry Roberts

Harry Roberts is an independent consultant web performance engineer. He helps companies of all shapes and sizes find and fix site speed issues.

Did this help? We can do way more!