Well I did think that. The CSS table will have something like 40 fields which relate to 40 CSS properties. I just need to give the client as much control of the CSS styles of their website as much as possible and figured that by putting the css properties in one single table at least would be more organised then say having a "logo" table with around 40 CSS properties (but then only a few would actually be used for the Logo).
Another approach I thought would be to have a logo table which then links to another table that then stores the ID for a CSS table which is more compacted, like....
Then this approach would mean that the Logo Table may use say 5 records from the Linking table...would this be less bloated approach??