Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

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 ExtensionsSkinsSkinsMinimal Extropy containers results in a lot of H1Minimal Extropy containers results in a lot of H1's
Previous
 
Next
New Post
6/29/2009 6:26 PM
 

Oliver Hine wrote

One of the things on my wishlist is to add Skin and Container settings into the core, similar to the Module Settings bits. I don't see the point in having a million copies of the same skin/container to only adjust a color setting, css class, or html headers. If the core allowed skinners to add settings which the portal administrator/host account could easily override in the skin/page/module settings controls, thing would start to get alot simpler for everyone...

I agree but I would solve it in a different way;

1. CSS variations of a skin, where the ASCX is the same, but there is a collection of extra CSS files that can be selected.

2. The selection of the skin/container should be in the control panel IMO, you have to click too much ATM IMO

3. Per module CSS that get's wriiten to the page head on render and is stored in the module settings

 

 

 
New Post
6/30/2009 3:15 AM
 

Timo Breumelhof wrote
 

 Sebastian Leupold wrote

 

AFAIK, H2 should be placed underneath an H1 tag, providing all modules using H2 wouln't match this requirement.

 

Sebastian, it would "solve"  the issue that you should have only one H1 tag on a page.

We cannot solve all use cases anyway, since there are too many, it's always a compromise.

I am not sure, which rule is more important - I personal prefer to have a "perfect" content structure, which can be easily transferred to a different media. If a page is regarded to be a complete document with title and content, content needs to be structured <h1> (multiple) with h2, h3 associated underneath. on the other hand, if the whole site is being regarded as a document, each page title should be an H1 and each module H2 - i.e. it depends on the skin, how the container shall render its title...


Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
New Post
2/2/2010 12:15 PM
 

You might want to take a look at my entry for the DNN skinning contest when it comes out. It uses HTML 5 semantics to mark up the structure of the page and CSS to render containers according to their location on the page, so you only need to use one container (two if you use the one that marks a container as an HTML 5 "article").

Also, if you look at the demo video of Declan and Vasilis's new skin at http://www.screencast.com/users/liffe..., you'll see how it's possible to build a skin that can be tailored to suit your taste.

 
Previous
 
Next
HomeHomeDevelopment and...Development and...Building ExtensionsBuilding ExtensionsSkinsSkinsMinimal Extropy containers results in a lot of H1Minimal Extropy containers results in a lot of H1's


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.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out