Hello,

We had a skin designed by an outside company and the default.css entries are causing a big mess. Is there a way I can just disable default.css in this specific skin? If not, any tips? It seems like the major trouble are all the default entries that apply directly to HTML elements (which I'm not sure why DNN even has). I'd hate to spend a ton of time trying to figure out everywhere default.css is influencing something in the design and then override it.

Thanks,

Mike

Thanks Richard... The files all work normally outside of DNN. Also, I can pretty clearly see where the default.css entries are causing trouble - I just don't want to go and add exemptions for everything if I don't have to. I feel like it should be pretty straightforward to disable the default stuff - is it not? Also, many skins now use bootstrap or Foundation, which often after their own form decorations and things... so I feel like the default stuff is even less important. When I just delete the reference out of the produced HTML, then everything looks great.

So is there just some way to get DNN to stop linking to default.css? I guess I don't get why I'd want it... especially when it's causing trouble.

Thanks,

Mike

Hello,

Yes - I see... They sort-of did. It was always part of the plan that we'd internally convert it into a skin - we liked their designs but they didn't have a background with DNN.

Still, I think it hurts the DNN ecosystem when people can't take relatively standard HTML templates and easily convert them into DNN without a bunch of headaches. The move to an ascx file is tough for a lot of people - but I get that as a reality of .Net stuff. But, the CSS just seems like an unnecessary headache. Much of the trouble is that there seem to be a lot of entries for basic HTML elements - not just dnn-specific classes. One I ran into right away was this one:

html, body, div, span, applet, object, iframe,h1, h2, h3, h4, h5, h6, p, blockquote, pre,a, abbr, acronym, address, big, cite, code,del, dfn, em, img, ins, kbd, q, s, samp,small, strike, strong, ub, sup, tt, var,b, u, i, center,dl, dt, dd, ol, ul, li,fieldset, form, label, legend,caption, article, aside, canvas, details, embed,figure, figcaption, footer, header, hgroup,menu, nav, output, ruby, section, summary,time, mark, audio, video {
margin: 0;
padding: 0;
border: 0;
font-size: 100%;
font: inherit;
vertical-align: baseline;
}

I just don't see any reason why this stuff would be included in a default css file. I'd totally get it if DNN wanted to have a css-reset.css file or something. But if you can't disable it, why is this here? Admittedly, this isn't really my area, but it seems that in a world of great competition for CMS systems and a move to a more agnostic design, that DNN would want to avoid creating extra work for people trying to develop DNN skins and modules.

Mike