If at all possible don't use class names that describe the way something
looks, but more what the thing actually is. I find that using names that
discribe the style of something will almost always come back to bite
you. And depending on how large you project is, it can bite pretty hard.
I was
I try to avoid words like left and right. I use navOne, navTwo for primary
and secondary navigation. It works quite well for me.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
On Behalf Of James Oppenheim
Sent: Thursday, 29 September 2005 11:25 PM
To:
I like to opt for naming conventions that work across all pages of the
site and all layouts where possible. The suggestions mentioned by
others of nav and navSub are ones I always use.
Be careful though not to get carried away with content specific
naming. Giving a column an id of 'news' rather
Whilst it won't affect accessibility or usability for the end user
(afaik) the class and id names should have semantic meaning indicating
there logical function - rather than id=rightColumn you might use
id=localNavColumn if the function of the column was to contain local
nav. This means if
James Oppenheim wrote:
I tend to use underscore for class and id, try very much to stay away
from two word file names.
This is a question (discussion?) that comes up every couple of months
here on the list - ultimately, I reckon you'll get as many
'conventions' in use as you've offered
James,
Read this:
http://www.westciv.com/courses/free/week_05/managing_files.html
and Tantek's presentation today at WE05, especially meaningful class names part
http://tantek.com/presentations/2005/09/elements-of-xhtml/
Cheers, Irina.
On 9/30/05, NickGleitzman [EMAIL PROTECTED] wrote:
James
