Cascading Style Sheets: The Definitive Guide 2nd edition.

September 20th, 2009

Cascading Style Sheets: The Definitive Guide 2nd Edition by Eric Meyers

Cascading Style Sheets can put a great deal of control and flexibility into the hands of a Web designer–in theory. In reality, however, varying browser support for CSS1 and lack of CSS2 implementation makes CSS a very tricky topic.

Cascading Style Sheets: The Definitive Guide is a comprehensive text that shows how to take advantage of the benefits of CSS while keeping compatibility issues in mind.
The book is very upfront about the spotty early browser support for CSS1 and the sluggish adoption of CSS2. However, enthusiasm for the technology spills out of the pages, making a strong case for even the most skeptical reader to give CSS a whirl and count on its future. The text covers CSS1 in impressive depth–not only the syntactical conventions but also more general concepts such as specificity and inheritance. Frequent warnings and tips alert the reader to browser-compatibility pitfalls.

Entire chapters are devoted to topics like units and values, visual formatting and positioning, and the usual text, fonts, and colors. This attention to both detail and architecture helps readers build a well-rounded knowledge of  CSS and equips readers for a future of real-world debugging. Cascading Style Sheets honestly explains the reasons for avoiding an in-depth discussion of the still immature CSS2, but covers the general changes over CSS1 in a brief chapter near the end of the book.

When successfully implemented, Cascading Style Sheets result in much more elegant HTML that separates form from function. This fine guide delivers on its promise as an indispensable tool for Website Design CSS coders.

Topics covered:

HTML with CSS
Selectors and structure
Units
Text manipulation
Colors and backgrounds
Boxes and borders
Visual formatting principles
Positioning
CSS2 preview
CSS case studies

Validation of HTML/CSS at W3 Standards

January 19th, 2009

Validation of HTML/CSS at W3 Standards

Never leave an
HTML
error on your web page. Open and check your
website in different web browsers. Make sure
things are aligned well, there is no font
missing and colors are visible.

If your site has
HTML
errors, the
Search engine spider
might not be
able to crawl properly. Also the usability
of your site will decrease. So it’s better
to keep a check on the code. Make it error
free.

Top 3
Reasons your code should be error free
:

  1. Search engine spiders won’t be
    able to
    crawl
    your site easily. They
    calculate page download time. So you
    might receive a lower  SEO score.
  2. Browsers behave very different for
    single
    code
    . Check code for IE and a
    Firefox user might receive an error or
    might not be able to view the page at
    all. This can result into higher bounce
    rates.
  3. You will get negative points, if you
    have
    broken links
    in your site. Also
    if the links lead to pages that does not
    exist at all.

Tip:
How to find broken links in your blog or
website

The best way
to check that your code is correct
:
Read the rest of this entry »

Using the CSS3 opacity directive

May 20th, 2008

Using the CSS3 opacity directive is easy and it’s completely future-proof, assuming that it’s accepted without changes, which is probably a safe bet. Unfortunately, this only targets modern browsers, such as current versions of FireFox, Opera, Safari & Netscape (which accounts for roughly 30% of our current traffic).
Unfortunately, if a browser doesn’t render opacity properly, the results are awful. Visitors might not be able to SEE the content you have, under a nearly transparent element, if their browsers don’t understand the directive! Not very accessible at all.
When you use opacity, it’s important to insure that the majority of visitors browsers will render it properly. The first step, is getting Internet Explorer to play nice.
The good news is that Internet Explorer already has a proprietary CSS extension that duplicates the opacity directive. IE has a way of creating effects using visual filters and transitions. (You can demo all the variations of filters and transitions at this demo site).
I wouldn’t normally recommend using these IE-only CSS extensions for your website seo, but there’s one extension that will mimic the CSS3 opacity directive and it comes in handy here. It’s called the “Alpha Filter” and it can be easily applied in CSS file.  Read the rest of this entry »

CSS Validation Service

January 31st, 2006

FAQ Index


  1. What are Cascading Style Sheets?
  2. Why do style sheets exist?
  3. Why use style sheets?
  4. Who defines the CSS standard? Is it one person? A
    company?
  5. What can be done with style sheets that can not be
    accomplished with regular HTML?
  6. Is there anything that CAN’T be replaced by
    style sheets?
  7. How do I design for backward compatibility using style
    sheets?
  8. What browsers support style sheets? To what extent?
  9. Do any WYSIWYG editors support creation of CSS? Any text
    editors?
  10. Can you use someone’s style sheet without permission?
  11. What does the “Cascading” in “Cascading Style Sheets”
    mean?
  12. Which style specification method should be used? Why?
  13. What are the advantages and disadvantages of the
    various style specification methods?
  14. As a reader, how can I make my browser recognize my
    own style sheet?
  15. How do you override the underlining of hyperlinks?

1. What are Cascading Style Sheets?
A Cascading Style Sheet (CSS) is a list of statements (also known as
rules) that can assign various rendering properties to HTML elements. Style
rules can be specified for a single element occurrence, multiple elements,
an entire document, or even multiple documents at once. It is possible to
specify many different rules for an element in different locations using
different methods. All these rules are collected and merged (known as a
“cascading” of styles) when the document is rendered to form a single style
rule for each element.
2. Why do style sheets exist?

SGML (of which HTML is a derivative) was meant to be a
device-independent method for conveying a document’s structural and semantic
content (its meaning.) It was never meant to convey physical formatting
information. HTML has crossed this line and now contains many elements and
attributes which specify visual style and formatting information. One of the
main reasons for style sheets is to stop the creation of new HTML physical
formatting constructs and once again separate style information from
document content.
3. Why use Style Sheets? Read the rest of this entry »