[thelist] Coding standards....

tim tim at hyperlinkage.com
Thu Dec 7 15:01:25 CST 2006

Matt Warden wrote:
> Actually, the main problem is that it misses the entire point of
> "class", which is to group semantically similar elements.

Quite so.  This is exactly why it's so difficult to maintain HTML that 
uses this naming scheme, and precisely why semantic naming is essential.

As far as the original post on coding standards, I would actually 
consider writing down some standard ID and class names to use in your 
markup.  This makes chunks of HTML and CSS easily reusable between 
projects.  You should also look at Microformats and consider whether any 
of those standards are useful to your company.

Additional things I might suggest for your coding standards:

   * Which markup and CSS standard you will be using

   * CSS is not optional!

   * What level of WCAG compliance

   * Do you allow Flash/Javascript/AJAX?

   * File names (e.g. lowercase, hyphens between words, .html)

   * Directory naming (e.g. all CSS to go in /css/ directory)

You could also look at Yahoo's graded browser support if you are 
interested in including browser testing in your standards.


More information about the thelist mailing list