.NET is the way which deals with header management that deals with working themes, in the ASP .NET has a problem that is big that is the embedment’s of the styles sheets are at the bottom of the header list. If the user uses the master pages that has a header content section then the user is additional CSS or style tags to the header, the master page end up above the standard .css theme file, if the user tries to attempt to add any controls to the page the same thing will happen, whatever the user usages to add any controls to the page it ends
SharePoint is a heavy CSS user, which could be both seen as a curse and a blessing in the same time. Because about all of the SharePoint UI is hard coded in the site definitions, CSS is the best way to operate the changes on the site.
A Share Point 2003 portal contains 7 different style sheets, which make up a total of 7403 lines of code and 1227 style sheet statements. Of these seven, four are hardly ever needed to be edited (menu.css, owsmac.css, owsnocr.css, paystub.css).
The other three style sheets are easy:
sps.css :
Cascading Style Sheets (i.e. CSS) is apparently a collection of pre-structured definitions that state or modify the entire look and feel of the webpage layout. CSS can be used to change the images, texts, tables, headings and other elements of a webpage. While using CSS you can easily modify or pre-assign the different features of a webpage such as employing a style that switches the text color to red and left aligned properties.
Utilizing CSS definitely means saving time on you efforts on webpage creation. Just changing a CSS style amidst creating
RSS/XML