Begining the switch from themes to css

A lot of css files in my _theme directory

[watercrazed]

I am looking a migrating away from themes to css

(also from frontpage navagiation to included pages, but that is problably best saved for another post - but I can't help an aside - What would you do first?)

I have a number css files in my _themes directory I don't do or want do anything fancy with my site design I would like to have one css file with the absolute minium styles in it. In addition to modifing the standard html tag H1..h6, body text, etc.. I think I would be happy with about 8 font, background etc related styles.

Do I need to keep these?

color0.css
color1.css
custom.css
graph0.css
graph1.css
theme.css
uwm-1000.css This is the one that is tied to the theme I am using.

Can I delete them? what do they do? I do not see them in the pages - a Find command in htlm mode does not bring them up but the uwm-1000.css shows up in a view source code as part of the theme tag.

the site is over 700 pages it just kinda grew over the last four years.

Or is the race not worth the rabbit, (should I find a project with a better payoff for the effort required.)

Add the asp shopping cart and it is about 3000 pages.

Any suggestions?

[bill]

You can certainly use elements of the generated styles if you like, but I get better results writing everything from scratch. (The TopStyle editor is a great tool and integrates directly into FP to take over the CSS editor functions.) You may want to make a local test copy of your website and play with styles (and includes) there. Writing your own CSS file is a leaning experience but you'll be glad you did it in the end.

[watercrazed]

I am pretty comfortable with the idea of writing my own. My concern is getting rid of the auto generated css and where and how to let FP know that this is the css file to use.

[watercrazed]

It kinda looks like I have to get rid of themes to make that work. Is that true? Any resoures for deleting themes from a large fp site? It tends to time out with any major changes.

[bill]

Do a site-wide Find & Replace to remove the FP generated CSS links and replace them with a link to your own. You'd want to do this on a test site to make sure you get it right.