E-mail List Archives
Thread: Managing CSS
Number of posts in this thread: 3 (In chronological order)
From: Priyabrat Mishra
Date: Thu, Jan 05 2006 3:40PM
Subject: Managing CSS
No previous message | Next message →
Hi
I need a Solution with concern to Strategizing CSS as well as Managing
Mimimum CSS files in long run.
Coming to the subject which bothers me a lot all the time is i have
separated the CSS for Presentation and the content layer
I have multiple product lines to manage and each product has atleast 5
different things to offer,
My present hierarchy structure goes this way
Product 1
|--default.css
|--Templates
Offer 1.htm
Offer 2.htm
Offer 3.htm Offer 4.htm
|--------CSS
Offer 1.css
Offer 2.css
Offer 3.css
Offer 4.css
But this will definitely get complicated when the Product lines grows as
well as their offerings
Looking for an Accessible as well as easy to manage CSS Management Solution,
please help
- Priyabrat
From: Patrick H. Lauke
Date: Thu, Jan 05 2006 4:20PM
Subject: Re: Managing CSS
← Previous message | Next message →
Not really an accessibility issue, so you may well be served better on
other, more general web standards lists, but...
Priyabrat Mishra wrote:
> Coming to the subject which bothers me a lot all the time is i have
> separated the CSS for Presentation and the content layer
>
> I have multiple product lines to manage and each product has atleast 5
> different things to offer,
Do the product pages really have nothing in common with each other and
you therefore need completely separate css files for each one of them?
Surely you can just define a single stylesheet at least for the common
look and feel, and even define a few classes for common things (a
product thumbnail, a feature list, whatever) that can be kept in a
single css that is referenced by all offer pages?
P
--
Patrick H. Lauke
___________
re
From: Joshue O Connor
Date: Fri, Jan 06 2006 3:40AM
Subject: Re: Managing CSS
← Previous message | No next message
Patrick H. Lauke wrote:
> Do the product pages really have nothing in common with each other and you therefore need completely separate css files for each one of them?
Surely you can just define a single stylesheet at least for the common look and feel, and even define a few classes for common things
(a product thumbnail, a feature list, whatever) that can be kept in a single css that is referenced by all offer pages?
Patrick makes a very good point here Priyabat. The issue does not have to be as complex as you fear. Use elements that are common to all pages in your template(s) and then classes for various individual styles as needed. The sky is the limit with what you can do when you break down your designs like this, and this approach will make your project more manageable as it expands in size.
Keeping your designs uncluttered, clean and simple will also help you.
Have a look at the CSS Discuss list for more detailed info on a variety of CSS related issues . You can subscribe here:
http://www.css-discuss.org/mailman/listinfo/css-d/
HTH
Josh
> Not really an accessibility issue, so you may well be served better on
> other, more general web standards lists, but...
>
> Priyabrat Mishra wrote:
>
>> Coming to the subject which bothers me a lot all the time is i have
>> separated the CSS for Presentation and the content layer
>>
>> I have multiple product lines to manage and each product has atleast 5
>> different things to offer,
>
>
> Do the product pages really have nothing in common with each other and
> you therefore need completely separate css files for each one of them?
> Surely you can just define a single stylesheet at least for the common
> look and feel, and even define a few classes for common things (a
> product thumbnail, a feature list, whatever) that can be kept in a
> single css that is referenced by all offer pages?
>
> P