[thelist] [OT] Web designer wanted - Kensington, London

Ian Anderson ian at zstudio.co.uk
Wed Jul 5 08:18:55 CDT 2006


Hi all,

apologies for the geocentric post, but I have taken a permanent position as Technical Director with an online magazine based here in London, and I am looking for one or more web designers to work with us on a regular but freelance basis. This would be office-based.

If you're interested, please see [1] for more details.

Thanks!

Ian
thefirstpost.co.uk

[1] http://www.thefirstpost.co.uk/pages/recruitment/web_designers.php


<tip type="Simple CSS tips" author="Ian Anderson">
CSS is good, but it's really dangerous in large sites. For instance, you could change a generic tag to make one page better, and in the process break other pages that you haven't visited for months.

You might want to use contextual selectors to restrict the scope of formatting when you're working with tag selectors. For instance, this is the sort of thing that gets you into trouble:

h2 {margin: 10px;}

If you use classes on the body tag to denote templates within the site, you can use contextual selectors to restrict the scope of formatting decisions:

.marketing h2 {margin-left:10px; font-size:14px;}
.store h2 {margin-left:0px; font-size:18px;}

You can apply the same principle by applying IDs to specific page regions:

#footer a {font-size: 9px; color: #555;}

It helps if you keep all the related selectors together in a named section of the style sheet.

This approach helps to minimise the inappropriate use of classes, such as:

<h2 class="serif14padded">

Because you can simply have
<body class="marketing">
<h2>...</h2>

When you do need to use classes, remember that if need be you can apply more than one class, separated by spaces:

e.g. <p class="first dropcap">

And when naming classes or IDs, if you can keep formatting-specific information out of the name, so much the better

Good names: .first, .byline
Bad names: .leftcol, .serif12
</tip>





More information about the thelist mailing list