Ok, so I'm a fairly new user of DNN and this forum...so this may have been discussed/addressed previously, but wherever that may have been, I can't find it.
From everything I've seen in DNN, it seems to treat CSS as an afterthought. I come from a tableless layout world where I have no interest in filling my code with completely unnecessary tables. I enjoy the power, nay, the absolute control, of creating and implementing CSS-driven layouts and skins.
With that being said comes my biggest frustration thus far with DotNetNuke.
I would really, really, REALLY like to find a way to disable default.css and portal.css on the portal level. I realize I can "empty" portal.css, but then my DNN portal is just referencing an empty file.
When I create a skin, I use skin.css as my master css file and want to keep it that way, period. That way, if I decide to release a new skin, my old vs. new css don't intermingle and interfere with one another.
What I've found thus far is a good third of my time developing a skin is spent overriding stupidly named classes in default.css.
Again, for those of us (or just me) who design a beefy stylesheet-driven layout, is there a way to just not include default.css and portal.css? It seems like a big waste of time writing overrides for something that [IMO] didn't need to be there in the first place.
Any comments/discussion/further questions/help is greatly appreciated.