Drawing the line with CSSLocked
I follow the articles about using CSS with much interest, as I have been a fan since I started out with HTML six or so years back. But where does one draw the line between using CSS or HTML tags?
My number one and two reasons for using CSS is the separation of style for modular reuse and maintainability. When ones client’s decision to revise their corporate ID results in their primary corporate color changing from #000066 to #000033 you will understand why.
But how far does one take this?
A simple example: A page I’m working on has the first phrase of certain paragraphs bolded to emphasis a change in topic. The HTML could simply be this…
WHAT IS IT: Performance Testing is…
HOW: Testing is…
OR, this could be done as follows with all styling specified in the style sheet (not given)…What is it:
Performance Testing is…How:
My preference is for the later as it gives tremendous control. But, it does feel over engineered and I begin to wonder what fate holds for the and
As for the
tag, which could justifiably go the same route, one must still remember the role it, and possibly the tag, plays in search engine ranking. Given that the default
settings are most likely completely different from what the designer has imagined this would require stripping it of all it’s styling first so as to make a clean start.
Is complexity the cost of reuse and maintainability? And at what point does one jump into separating all content into XML and using XSL to render the page? (Assuming that if one is working in a CMS it can handle this!)
I’m not where I want to be but the journey sure is interesting…