Hi,
I made a css customization to the content on front page. But then the content area on other pages (like blog and product pages) changed as well.
Is it possible to style the content area, only on a specific page? I also wonder this for example the widget-pad. Maybe I don't want some widgets to be styled, but when I style them it's all or none...
Thanks!

Yes, it is possible to change the style of a content area on a specific page. The same goes for a specific widget in a sidebar. For example, if you want to change the content area (the main content column on the left side of the page) on specifically the homepage, you'd use this CSS:

For the regular pages, you need to use that specific page's page ID for the body tag selector (as shown above in the About Us example - since the ID for that page is 874). To find it, you can view your source and look at the class tag at the top of the page.

Thanks a ton for providing this info. It is helping me as well, as I have left sidebar for navigation that I want to be a unique color. However, is there a way to set the background color for the top level page and have it inherrit on only the child pages of that particular section (without having to do something like the following)?

You can target child pages by using another body class. If you inspect your body classes on your child page, you will see there is a class that identifies the parent page id like so: "parent-pageid-14". You can use this class to target all the child pages of that parent page all at once.

As for targeting widgets on individual pages, you'd have to prefix it with the proper body class and then target the specific widget, they have unique IDs.

BTW, I recently wrote a plugin that allows you to add custom styles to any individual page or post! I'm sure you'd find it useful if you do a lot of special styling for different pages. It lets you write your own custom CSS/LESS that is only loaded on that page, so you don't have to worry about messing with body classes. It doesn't however handle groups of pages (like child pages), that would still have to be done using the parent-pageid-X body class. It's linked down in my signature below if you're interested in learning more about it.