Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeDevelopment and...Development and...Building ExtensionsBuilding ExtensionsSkinsSkinsReduction of CSS files in skinningReduction of CSS files in skinning
Previous
 
Next
New Post
9/3/2008 8:57 AM
 

Is there anything that can easily be done, probably in the 5.0 version, to reduce the number and inheritance of CSS files for DNN skinning?  Portal.css has somewhat gone away, but finding and over riding all the CSS classes in DNN skins is a problem for many beginners, and even many of us who are more experienced.  I won't mention my pet peeve that module.css shouldn't really exist but should inherit from the skin/container.  Oh, I guess I just did.  :)

Tahnks,

Jeff

 
New Post
9/3/2008 9:32 AM
 

Jeff, I agree that we inherit to much styles (and default.css should be cleaned up)

The problem here is that this would be a breaking change for existing installations.

So this is a very difficult subject...

I do have a skinobject that removes any stylesheet from the page, you want, I just wonder if that helps for "beginners".

I don't agree with you on module.css.

Some modules need CSS and it's better to have it externallty then inline.

It's more about what some module developers put in there IMO.

 
New Post
9/4/2008 11:42 AM
 

Timo Breumelhof wrote
 

I don't agree with you on module.css.

Some modules need CSS and it's better to have it externallty then inline.

It's more about what some module developers put in there IMO.

I'll go along with that definition.  The times I run into trouble are when a module developer decides that <h1> has a specific style that doesn't match the one I use and assume would be used across the board.  I don't mind module-independent CSS as long as it stickes to what's required.

The other part of this is that most of my compliance issues with Sec 508 (among others) stem from modules, not DNN core.  And again, if the module properly used the CSS that I set up the problem would disappear.

Jeff

 
New Post
9/11/2008 7:49 AM
 

One of the big challenges in an environment like DotNetNuke is that a page is comprised of many different pieces, all written by different developers, designers and admins.  The DNN core obviously cannot write a single stylesheet that serves every module and skin, and skinners have no way to know the requirements of the individual modules.

What might be interesting is to see if we couldn't generate a "master" portal.css that combines all the styles from the active skin and all actively used modules.  If generated, this file could be used instead of the individual default, skin, container, module, portal css files.  There are certainly some issues here in terms of maintenance and how to deal with newly installed modules.

Our current skinning engine is definitely targeted at the typical business user who has little design/CSS experience.  We need things to "just work" as much as we can.  Our challenge now is to provide hooks that allows an administrator take control and remove the "training wheels", recognizing that some administrators may remove the training wheels without fully understanding the implications (we still need dad running along behind the bike for a couple blocks).


Joe Brinkman
DNN Corp.
 
New Post
10/20/2008 8:19 PM
 

Timo Breumelhof wrote

I do have a skinobject that removes any stylesheet from the page, you want, I just wonder if that helps for "beginners".

Hi timo

can you share the skin object  for us, maybe how to implement it? appreciate much your reply.


sunblognuke v5 for dnn

Ultimate Blogging Module for DotNetNuke Platform
The professional provider of DotNetNuke support, skin design and custom module development.

 
Previous
 
Next
HomeHomeDevelopment and...Development and...Building ExtensionsBuilding ExtensionsSkinsSkinsReduction of CSS files in skinningReduction of CSS files in skinning


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.

Copyright 2017 by DNN Corp Terms of Use Privacy
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out