Im talking about the real world

Lets asume that you are a skindeveloper. Selling skin to a market.... A new browser come to market, lets call it IE 8. As a good skindeveloper you make a new release of your skin handling some isssues regarding the new browser, maybee you will handle the 120 DPI or something. You release the new skin to market.

All customers get the new skin and install it. Whops...the skin.css is overwritten.

You cant assume that you have controll over every intallation. Im talking about how to make DNN better for the ecosystem.

Jan

Dave I use portal.css in those case I am sure the value will not effect other parts of the installation. Thats not possible in all cases

The reason of new feature to make portal.css optional is also an argument.

This post is about Skinning enhancement not how we do it today by adding .css here and there ...... The reson for having module.css per portal is obvious.

Today an admin have access to skin.css portal.css container.css but NOT module.css.

No I am not talking about a skin I sell. I am talking about a skin anybody sell. And I am not talking about any admin making changes in the skin they buy from a vendor.

IM talking about customers who have a skin, install a module with a module.css that they dont feel fit to there skin in some point. The customer have no skill so contact the host (superuser) or maybee a skinner nearby and ask for a change. As the module is used by alot of portals changing the module.css is not an option. So ok the skinner could change the portal.css... Yes its an option. But as I tryed to say it could have inpact on other areas in the portal and adds yet another http request on each page load(DNN-8098). Furthermore the skinner have to find out what is included in module.css to solve the issue for the customer.

The skinner have no access to module.css from file manager.

Portal.css (if loaded DNN-8098) loads for every page module.css loads for those page that have module.css

So what I try to say is: To enhance DNN skinning it would bee good to have the module.css or better Modulename.css located uder the portal folder eg module.css per portal.

Yes.. if a new release of the module installs it will need actions but that could bee solved too (as portal.css)

I agree that good that admin cant change module.css in DNN today but im not talking about today im talking about enhancements.

Yes I support your intial enhancement too.

Jan