When you look at the markup for just about any web page, you’ll see it’s
divided into two major areas - all the code between the and
tags, and all the code between the and tags. The head is for
CSS and Script and Meta code, the body area is for all your text and
graphic content.
A CSS style that targets the body looks like this:
body { font-family: Helvetica; }
This is essentially telling the browser that ALL the text in the of
your page gets styled with Helvetica. This has an obvious time-saving
advantage over repeating the same style for every single instance of text
on your page. It also reduces excessive and unnecessary page code which
really can compound and complicate troubleshooting problems with your site.
Creating a CSS style for the body tag is also extremely easy. When you make
a new style in Freeway Pro’s Style Editor, there are two input fields in
the upper right of the window… marked Tag and Name. By default, FWP
automatically puts a generic style name in the Name field which designates
the new style as a Class Style in CSS parlance. To create a Tag
Stylesimply type the tag
name ( in this case, body ) into the Tag field. Delete anything in the
Name field so it’s empty, then choose whatever attributes you want your
text to have. You are done and good to go.
But what if you want your headers to be different from the rest of the
text? No problem. You can set the styles for them separately using their
tag style names, h1, h2, etc.
In fact, CSS let’s you use shortcuts for Tag styles that share the same
attribute. How would it look?
h1, h2, h3, h4 { font-family: Verdana; }
So just like with the Tag style we made for the body tag, we would type tag
names for this new style into the Tag field of the Style Editor. We can
group all the header tags together, separated by commas, into the Tag field
– h1, h2, h3, h4 – then making sure to delete anything from the Name field.
Finish by selecting the common attributes and be done with it.
You would still need to have the individual header tag styles to be able to
apply them and provide them with non-common attributes like size, but for
the most part styles like these are automatically applied.
–
Ernie Simpson
On Sat, Jun 23, 2012 at 1:18 AM, rebeccintosh
email@hiddenwrote:
Excellent!! Parsing errors are gone. Normally I don’t put a semicolon,
but I was using several Google fonts, and I thought that I was supposed to
copy and paste their code. So your suggestion was great.
Not sure I get what should be done regarding the body tag …
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options
