Home/ Questions/Q 82777
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-10T21:40:12+00:00

We have a large ASP.Net website that has a single css stylesheet which is

  • 0

We have a large ASP.Net website that has a single css stylesheet which is getting out of control.

I am thinking of using the following strategy (taken from http://www.techrepublic.com/article/developing-a-css-strategy/5437796/) which seems logical to me…

you might have one CSS file devoted to sitewide styles and separate CSS files for identifiable subsets of site pages (such as pages for a specific department or pages with a different layout style). For styles that are unique to a specific page, use a separate CSS file for each page (if there are too many styles to fit comfortably in the document header). You link or import the appropriate CSS files for each page, so that you load all the styles needed to display that page, but very few unnecessary styles that only appear on other pages.

Is this a good way to proceed? What are the alternatives?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. I think the best option is to divide css in:

    -layout.css

    -content.css

    Then if you need other more specific you can add more like an css for the ads: ads.css, or one css for a specific section.

    I would also add ie.css for IE css hacks.

    I would not speak about creating one css for only one page: the problem you can have if you use too many css, is that your page will have to do more requests to the server and this will slow your page. This is why i recommend you to implement an HttpHandler which will create a cache copy in only one file of the css you need at the moment. Look here: http://blog.madskristensen.dk/post/Combine-multiple-stylesheets-at-runtime.aspx

    • 0