Jen Strickland wrote:
> I have an application that I've built css files for, and I'd like to
> make them more organized. Does anyone have any guidelines for how to
> approach it?
One of the best I've come across and one I've started to pattern my
large sets of CSS after as much as I can is
Hey there,
I have an application that I've built css files for, and I'd like to
make them more organized. Does anyone have any guidelines for how to
approach it?
Thanks,
Jen
__
css-discuss [cs...@lists.css-discuss.org]
http:
On 1/28/06, Bill Moseley <[EMAIL PROTECTED]> wrote:
>
> which I don't want to effect other elements.
>
Is it possible to simply add an ID to the table element, and edit the CSS
file appropriatly?
table#specifictable th {
border-bottom: 1px solid #666;
}
___
On Mon, Jan 23, 2006 at 09:19:18AM -0500, Adam Kuehn wrote:
> You have just violated the CSS Specification, and compliant browsers
> are therefore free to ignore green.css. [1] Included CSS files must
> come at the beginning of a stylesheet, before any property/value
> declarations, not at the
>>Of course there's no one-right-way to do this, but here's what I would
>> suggest. Have one master CSS file, say style.css, that every page
>> references. Inside the style.css, put everything that is common across
>> all brandings. You may even want to put the default branding in this
>> file. Th
At 05:37 AM 1/21/2006, Jesse Skinner wrote:
>Bill Moseley wrote:
> > I just looking for a few tips on how to organize CSS files.
>
>Of course there's no one-right-way to do this, but here's what I would
>suggest. Have one master CSS file, say style.css, that every page
>references. Inside the style
On Jan 20, 2006, at 9:38 AM, Bill Moseley wrote:
> I just looking for a few tips on how to organize CSS files.
I kinda like how the CSS for most Ruthsarian Layouts is organized:
http://webhost.bridgew.edu/etribou/layouts/index.html
My personal technique is to link from index page like so:
...
Bill Moseley wrote:
> I just looking for a few tips on how to organize CSS files.
>
> First, I'm ending up with quite a few css files for
> all the parts that might get replaced. Is it reasonable to separate
> the css into small files like that?
>
> Second, I can see where there could be a lot o
This is a sanity check (mine, not yours ;)
I just looking for a few tips on how to organize CSS files.
I've got an application that can be branded. CSS and templates to
generate the html are searched for in a $PATH-like way.
For example, a "green" branded version might request:
/green/css/
