Sent by Aaron Mehl on 13 December 2002 09:09
This is the orignal post
>
> Hi I have been trying to design sites using html/xhtml and css. My
> problem has been to much information and not any clear guidlines. What I
> mean is that I have the rules of css and xhtml tags and rules. I have
> read the posts on this group which are reactive for the most part. I have
> surfed the sites Glish E. Meyers, etc. but most of it seems to confuse me.
>
> What I need is a bottom line way of creating pages using CSS that will
> generally work ie. maybe in browser x the color will be slightly
> different or a css nav bar slightly bigger. But not all over the place. A
> one fits all list. This could involve compromise in one aspect of
> standards complience but will work.
>
> What am looking for is a set of Golden Rules that I can start from for
> all times. I am not talking about a book to buy or an article to read but
> something along a chart, maybe more than a page. Too much is said on each
> browser and confuses me and I end up having a page that works in none.
>
> I came up with my outline. Maybe it is missing parts or has extra ones. I
> am making this a personal project, which is to try to make CSS aided
> design simple.
>
> I am throwing this idea out to the discussion group I have grown to
> trust and enjoy reading so much.
> so here goes.
>
These are the answers so far put into the rules if you feel they are put in
wrong (I copied them wrong etc) add your comments
If you feel the idea is not a real golden rule (it only works on browser x)
add your comment
If you feel a rule is missing add it
If you have additional information please add it.
Thanks
Aaron
> --------------------------------------------------------------------------
> I. Xhtml or HTML
Rule one: Use XHTML it works better with CSS
> II. Strict or Transitional -quircks
Using XHTML has more impact on your CSS because its proper
implementation determines whether or not the browser will use quirks
or strict mode to display the page. All browsers will load and
display XHTML, all the way back to IE and NS 3.x. It even loads and
displays just like HTML.
> III. Structural design Divs spans, is there a difference between class
Rule Two: Use Class multiple times within the same page, ID's only once.
> and id (spans are inline when or if should they be used??)
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
A class is a _type_ ("flavor") of an element that can be used throughout a
document (if you declare div.chocolate, you can have any number of <div
class="chocolate"></div>s in your document). An ID is like a name for one
specifice element (declaring div#george, you can only have one <div
id="george"></div>).
DIVs are, theoretically, for DIVisions of content. A SPAN simply SPANS a
set of content. One difference is in their structural role - a DIV is
block-level, getting its own box in the page layout, while a SPAN is
inline. Think of the difference of drawing a square around a paragraph of
text and highlighting a few sentences (if that helps....).
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
Should the html tags be used for structure?
(clarification Ul or h1 I meant having the css use xhtml tags in a non-
stand way
such as turning a list into a table or a table into a list.)
>
IV. Units of Measure what to use and where ems pxs etc
Rule three: For absolute positioning onscreen use px or %,Use em's for
screen text,and pts for print
% might be best simply so that it scales nicely
with however wide the user has his or her browser.
V. Colors to use are we still stuck with web safe or not? Hex names or
color names?
VI. Centering
Rule Seven: text inside a div, set the div to text-align: center;.
Basic centering (margin: auto and the ie hack)
>
VII. Positioning Divs pictures uls ols etc. which it the best way?
Rule Seven: FOr positioning block level elements,
use margins. Use px and absolute positioning
> VIII. muliple style sheet
Rule eight; Use multiple style sheets for modular design and as a work
around for NN$.
> IX. inheritance
Rule Nine: No rules for proper inheritence.
> X.
Rule ten: golden fonts: Georgia, Times New Roman, Times,
serif; and Verdana, Tahoma, Arial, Helvetica,
sans-serif; Trebuchet MS
> Thanks to all
> Aaron
> AM in the AM (PM)
> ______________________________________________________________________
> css-discuss [EMAIL-REMOVED]]
> http://www.css-discuss.org/mailman/listinfo/css-d
> Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
>
AM in the AM (PM)
