alt131 - 1:59 pm on Aug 16, 2011 (gmt 0)
Hi joliett89, and welcome to WebmasterWorld
The program itself consist of 126 tempalates that fall together to make a website
A great question because many coders start with templates like this. However I suggest the best place to start is to ask what your end goal is: While 850 lines of css sounds a lot, and probably could be refined, that number of html templates suggests to me the major redundancies, inefficiencies and issues are probably not in the css itself.
So I'd ask why you are doing this, and what you are wanting to achieve.
For example, "efficiency" is currently fashionable, so a search on "minimise css" will produce lots of techniques to minimise/compress existing css that will help increase the page speed score, for example. However, most techniques just squish larger files rather than dealing with the underlying issue - whether large numbers of large files are required in the first place.
Alternatively, if your goal is to produce clean, efficient and simple code, then it would probably be easier to re-write the site rather than try to work around 126 html templates. However, that has a learning curve and depending on your ultimate goal, may not be a good use of your time. A mid-way point might be to move to a more simple template system. Unless you actually need xhtml, I'd also recommend moving to html as well.
In terms of tools to identify redundant css, there are the firefox/firebug extensions "Dust me selectors" and pagespeed's "Unused selectors". However, use with care as they are not 100% reliable.