So, one of the more, actually possibly the MOST frustrating thing about the blog module, for me of course... is the fact that module.css is constantly getting the beat down from either my skin.css file or my portal.css file.

I look through the ViewBlog.ascx file, then modify the CSS styling from the module.css file to change the styles, only to find that nothing changes, and I actually have to dive into the ascx files and modify with in-line CSS.

Doesn't this defeat the purpose of have a style sheet for the module in the first place?

Do I need to put a <p></p> class in my module.css file so the skin.css file doesn't overwrite my styles when browsers see the <p> tags in a blog entry?

What am I missing that might make blog module styling simpler?  Then, by the way, every time the module is upgraded, I lose my styling.

P.S. > To those who love and support and admire the blog module, this is exactly the type of thing that has, for years, prevented me from using the module to a greater extent... It has seemed SO behind the times in SO many ways... that even though I love DNN, I love the community, and I want to see these projects succeed, I hesitate to implement some of the functionality because it ends up taking sooo much time to work through issues that ought to have been in place from the start.

I had the same issues, I created a special container for use with the blog module, and used the container's css to achieve what was required