Here are my 2 cents on the topic (although you probably already know this stuff). I hope that this adjustment tries to minimize the number of classes being used. For example, instead of applying classes to each individual element in a menu like so:
<table class="table_class"> <tbody class ="nodeclass" id ="This_Node"> <tr> <th class="nodetitle">Node Title</th> </tr> <tr class="contentrow"> <td class="content"> ...
and
.table_class { color: blue; background-color: silver; } .nodeclass { color: black; } .contentrow { margin: 1em; } .content { background: silver; } ...
A class or id should be applied to the container element and child elements should be styled appropriately, like so:
<table class="nodetype2"> <tbody id ="This_Node"> <tr> <th>Node Title</th> </tr> <tr> <td><p> ...
and
.nodetype2 { color: blue; background: white; } .nodetype2 th { background: silver; } .nodetype2 p { color: black; } #This_Node h2 { font-size: 120%; } ...
This allows you to restyle much more flexibly and lightens the amount of markup you have to put in your page. Now obviously some tagging of sections using spans and divs with classes will still be necessary but it should be avoided when possible.
In reply to Re: Site Announcement: Expect CSS changes and instability
by synistar
in thread Site Announcement: Expect CSS changes and instability
by demerphq
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |