Site Announcement: Expect CSS changes and instability

In a big part motivated by eric256, bart and other commentors on the site CSS and its foibles we are starting on a low-intensity project to bring some order and logic to the various CSS tags. This will mean that the occasional CSS bits that you may have employed in the past wont work anymore because the class or id has been renamed. Apologies for this, but you can be fairly confident that if something changes it will have changed for the long term.

Apologies for this but the nature of PM makes it difficult to fix all of this at one go so this stuff will be happening for the next while. Hopefully it wont take too long.

Also you can help us with this by reporting perceived inconsistancies or places where you really wish there was an ID/CLass but isn't. Speaking with eric256 or the other pmdevils is probably a good way to get your ideas reviewed or implemented.

Thanks for your tolerance.

---
demerphq

_{First they ignore you, then they laugh at you, then they fight you, then you win.

-- Gandhi

Flux8}

Comment on Site Announcement: Expect CSS changes and instability

Replies are listed 'Best First'.
Re: Site Announcement: Expect CSS changes and instability by synistar (Pilgrim) on Sep 10, 2004 at 21:52 UTC
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"> ...` [download] and `.table_class { color: blue; background-color: silver; } .nodeclass { color: black; } .contentrow { margin: 1em; } .content { background: silver; } ...` [download] 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> ...` [download] and `.nodetype2 { color: blue; background: white; } .nodetype2 th { background: silver; } .nodetype2 p { color: black; } #This_Node h2 { font-size: 120%; } ...` [download] 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.	[reply] [d/l] [select]

Replies are listed 'Best First'.

Re: Site Announcement: Expect CSS changes and instability
by synistar (Pilgrim) on Sep 10, 2004 at 21:52 UTC

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">
        ...
[download]

and

 .table_class {
    color: blue;
    background-color: silver;
 } 
 .nodeclass { color: black; }
 .contentrow { margin: 1em; }
 .content { background: silver; }
    ...
[download]

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>
        ...
[download]

and

 .nodetype2 { color: blue; background: white; }
 .nodetype2 th { background: silver; }
 .nodetype2 p { color: black; }
 #This_Node h2 { font-size: 120%; }
 ...
[download]

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.

[reply]
[d/l]
[select]