Outer Court

Tech - Posts to comp.infosystems.www.*

From: "Philipp Lenssen" <phil@mrinfo.de>
Newsgroups: comp.infosystems.www.authoring.stylesheets
Subject: Re: "Notes on making classes accessible"
Date: Thu, 24 Aug 2000 19:41:18 +0200
Message-ID: <8o3mns$rtc$10$1@news.t-online.com>
Russell Wickstrom <rwickstrom@bgea.org> schrieb in im Newsbeitrag:
39a5255d$0$13726@wodc7nh6.news.uu.net...
>..
> I think that the argument is being made for a standardization of CSS class
> names, which is a two edged sword...
>..

It would be nice to have some sort of free-to-use guideline, helpful if you
work in a team, read other people's source, exchanging/ distributing
stylesheets, etc. I don't think there should be any "official"
standardization, as in: a certain software/ robot expects this or that class
name.

Here are some typical repeating areas I define for pages, with varying
names:

 - navigation bar in page/ navigational frame in frameset (navbar, navig,
nav, navigation...)
 - main contentual area in page/ content frame in frameset (content, cont,
page, text, textual...)
 - header area in page, or logo/ header frame in frameset (header...)
 - advertising (ad, advert, banner...)
 - copyright information (copyr, coypright...)
 - illustration area, usually left or right of the text-flow (illust,
illustration, pic, image...)
 - related content/ link collection at the end of an article (links...)
 - footnote (footnote)
 - table of contents (toc, TOC)
 - download area (download, file, files...)
 - introduction (intro, introduction)
 - author info/ signature (author)
 - date (date)

--
Philipp Lenssen
M+R infosysteme
http://www.mplusr.de









 
Basic
Goodies
Design
Tech
Email