I’m lucky enough to have a very talented team of developers working with me at Cimex. That doesn’t stop us having to use freelancers though and it was for that very reason (and those very few occasions where we forget print stylesheets) that we devised a set of guidelines for all our xHTML/CSS/JS projects.
We’re not claiming to have produced an exhaustive list of best practices here, rather a reference that helps ensure anyone working with us can gauge the quality of the code they’re supplying. For no good reason, other than the fact that I rather like them, I’ve used Jordan’s web reworking of Jan Tschichold’s Penguin Composition Rules as a basis.
Let us know what we’ve missed.
So far 2 people have argued with us about ‘Guidelines for xHTML/CSS/JS projects’. Read what they've said and then add to our woes using the form below.
Love what we’ve said? Think we’re talking nonsense? Don’t worry about being polite, just let us have it. We’re not afraid of telling you that you’re talking crap, so don’t be afraid of telling us the same.
Very nice.
I’d be happy if I received this from an agency as it clearly shows they give a monkeys and know their stuff.
I’m not so sure on Access Keys any more but there are some pretty unhelpful standards in existence. See section 2.4.4
http://www.cabinetoffice.gov.uk/e-government/resources/handbook/html/2-4.asp
Probably a typo but you’ve got an tag in there that isn’t closed. But you may use HTML 4.0 in which case ignore me!
Thanks for comments George. Yep I agree - the UK Government accesskeys standard is a pain. Using numbers implies some kind of sequence but this logic falls apart when sections appear in a different order (almost always) or not at all (again, almost always). I’ve lost count the number of times we’ve been berated for not using the standard and then had to retrospectively explain why not.
Oh and thanks for the pointing out the validation problem…I guess I should have checked it against my own guidelines!