Products

Evoq Content Overview Content Creation Workflow Asset Management Mobile Responsive Personalization Content Analytics SEO Integrations Security Website PerformanceEvoq Engage Overview Community Management  Dashboard  Analytics  Member Profile Gamification Advocate Marketing Community Engagement  Ideas  Answers  Discussions  Groups  Wikis  Events Mobile ReadyDNN Support PackagesEvoq: CMS FeaturesEvoq OnDemandCompare DNN's CMS Products

Solutions

Content Management SystemMulti-Channel PublishingDigital MarketingOnline Community ManagementIntranet Software SolutionOur CustomersPrime

Resources

Test DrivesSchedule A DemoDocumentation CenterWebinarsWhite PapersProduct ManualsRequest PricingData SheetsCase StudiesEvoq Preferred Products Content Management Ecommerce Forms Identity Management and Authentication Site Management Social Themes

Partners

DNN Partners Partner Directory Become a DNN Partner Partner Program Overview  Hosting  Implementation  ISV  Training  Competencies

Community

Participate Ask a Question Forums Community Showcase DNN MVP  Program Overview  Lifetime MVPs  Honorary MVPs Subscribe to DNN Digest Advisory Groups  Awareness Advisory Group  Developer Advisory Group  Partner Advisory Group  Technology Advisory GroupLearn Documentation Wiki Community Blog Video Library Project History Development RoadmapDownload DNN Store Language Packs Manuals Nightly BuildsSecurity Policies Security Center

Blog

About

News Press Releases News Coverage Press KitCareersContact DNN

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
HomeHomeUsing DNN Platf...Using DNN Platf...Skins, Themes, ...Skins, Themes, ...A little guidance on portals/skin levelsA little guidance on portals/skin levels
Previous
 
Next
New Post
1/31/2013 11:10 AM
 
Stuart Fraser


Joined: 1/2/2013
Posts: 294

Hi, my apologies in advance if these questions seem stupid.
I am just working my way through a DNN 6 skinning pdf and understand the layout concepts no prob, but could some one just give some guidance as to the different  levels of skins.
At Portals level I have 2 folders default and 0 ???.
In my DNN 7 site I have a number of skins under the default portal folder
         i.e Default, Aphelia, Gravity etc as well as other folders like templates, containers etc  

Under the portal 0 folder I have another set of skins, templates, containers etc, 

When I installed some free skins they went under the 0 portal folder?

I am just having some problem getting my head around these diferent levels and what each level actually does

  1. i.e  what is a default skin and what is site skin??.
  2. For example If I was creating a new skin/layout which portal level do I do it under.
  3. Can I just add new folders and files to create a new skin in my VS DNN Dev solution and DNN will be able to use it.
  4. Can I edit a skin CSS direct and see the results onn a page using it (tried it but nothing happened).
  5. If I create a new skin layout do I also have to create a new container??

I know it is probaly easy when you know how but it is unlike any other template system I have used.
 
New Post
1/31/2013 12:55 PM
 
April Spence


devcentral.f5.com
Joined: 11/4/2005
Posts: 562
Not a stupid question at all. Because of DNN's skin hierarchy this trips up a lot of designers. This video should help quite a bit:

http://www.youtube.com/watch?v=dsXX5t...

This is also a good guide:

http://dnngallery.com/blog/id/245/dot...

To answer your questions:

1. the default skin is on the DNN instance level and can be used and accessed from all portals. DNN ships with a _default skin which is used when no other skin can be found. The skin for a portal is used on each individual site and is typically on available to that site (if installed correctly).
2. Create a skin in the portal you are working on /portals//0/skins/skin.ascx.
3. Yes
4. Yes
5. not required to create a new container...but typically you would want your containers to follow along with the look of the skin.

One note...I usually try and put everything in the skin.css including container styles.

Steven Webster
Manager, Community Platform
F5 Networks, DevCentral
 
New Post
2/1/2013 3:59 AM
 
Stuart Fraser


Joined: 1/2/2013
Posts: 294

First of all,  thank you very much for your reply and useful video help.
DNN is a bit different to any other CMS and as many of the tutorials are for older versions it can be hard to not only follow the guides but get your head around the concepts , so help from you guys is billiant,

The word Portal is throwing me a little and could do with a clarification on what it is, for example  If I was setting up several DNN websites for different clients of our organisation do I:
1. Install several DNN 7 websites (one for each customer) this would be my understanding?.

2. Or one DNN instance running several sites, this may sound silly but I have read some comments that were hinting at this or at least that was how I percieved it. I dont see how this would work but hey?

I am sure those videos will shed some light,  however, I installed Chis Hammonds Multifunctional template as a learning tool using the host extensions install wizard and this template appears under the default skins section.
Should I have installed it using the Admin install wizard and why / what is the difference?
 
New Post
2/1/2013 7:14 AM
 
Mark Eckeard


Joined: 1/19/2004
Posts: 924
A portal is a child, or sub-site of the main install of DNN. In my case, I have my intranet as the main install and created portals for each department within my company (HR, Marketing, etc). However, it's still a single install of DNN.

Here is my "main" URL:

http://intranet

And here are the portals I set up:

http://intranet/marketing
http://intranet/hr

So this is a single install of DNN with 2 portals.

With that said, if each customer of yours doesn't mind being a child of your main site, I'd go that route. Otherwise I would possibly consider splitting them up but it could depend on the requirements from those customers.

Mark
 
 Page 1 of 1
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Skins, Themes, ...Skins, Themes, ...A little guidance on portals/skin levelsA little guidance on portals/skin levels


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