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

HomeHomeUsing DNN Platf...Using DNN Platf...Skins, Themes, ...Skins, Themes, ...Making a skin, or modding a skin?Making a skin, or modding a skin?
Previous
 
Next
New Post
10/30/2008 4:35 PM
 

I need to create a skin for DNN.  I am working with a team of 5 other people to develop a site through DNN and all of us are new to DNN.  So my question is:  Would I be better off to create a skin from scratch or mod an existing skin?  Time is an issue (isn't it always?), but it's not a make-or-break constraint at this point, so please take that into consideration as well.

Also, can anyone recommend a nice tutorial for creating skins?

 

Thanks.

 
New Post
10/31/2008 5:12 AM
 

IMHO it is usually much easier to tweak an existing skin that developing a new one from the ground - except you are already an experienced skinner. Check out available skins to find one, which has a page layout, which meets your requirements.


Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
New Post
10/31/2008 7:54 AM
 

Until you know w hat you're doing, modify existing ones.  There is skinning documentation in the docs for DNN, but you really want a subscription to DNNCreative.com.  Also might check Packt's DNN Skinning book.

Jeff

 
New Post
10/31/2008 12:01 PM
 

DNNCreative is an excelent starting point.   Skinnning does though, for a novice, cause some confusion that isn't really needed.  I had, and still have trouble from time to time.

Some advice from my failuers :->

1) Make sure you have a solidly installed Development environment.  Google Michael Washington, he has step by step instructions on setting up your dev environment up best.

2) Forget about the source code version of DotNetNuke right now, you don't need it for anything at this time.  Just use the install version on your dev env.  it's quick, easy to install, and if you screw it up you don't have to wait a month....But do follow michaels instructions to the letter.

3) Post any and all questions in here!! Seriously, everyone is very friendly here....we want more poeple using this :->

For skinning specifically, the problem learning it is that most of us already know alot of HTML, and at first glance it looks super easy, so we blaze through the instructions, miss something, then spend hours hunting down what we missed.

Instead, do this, create a simple HTML doc with 1 table, put all the tokens in it and a content pane.  Copy the XML file from the included skins into your folder wiht your HTML file.  throw it in a zip, and upload it to your development copy of DNN and load it.

Then open Virtual Web developer, tweak the HTML, go back to IE, parse skin package, look at it, tweak some more, parse again.

 

Also, there is a debate on whether to skin using ascx or html with some people.  I say use HTML and XML to create your skins.  ascx sounds like a good way, but you end up typing alot more than needed.  HTML is the way to go, and use the parser.  Thats the way the smart people who actually made this program intended, I"m sure they have good reason for that :->

 

 


Josh Martin

 
New Post
11/4/2008 3:05 AM
 

Josh Martin wrote
 

Instead, do this, create a simple HTML doc with 1 table, put all the tokens in it and a content pane.  Copy the XML file from the included skins into your folder wiht your HTML file.  throw it in a zip, and upload it to your development copy of DNN and load it.

Then open Virtual Web developer, tweak the HTML, go back to IE, parse skin package, look at it, tweak some more, parse again.

 

If you are starting out dont start with tables start with tableless skins directly. Make sure it looks perfect and is valid in firefox and then pull out your hair trying to make it work in IE :)

 

Josh Martin wrote
Also, there is a debate on whether to skin using ascx or html with some people.  I say use HTML and XML to create your skins.  ascx sounds like a good way, but you end up typing alot more than needed.  HTML is the way to go, and use the parser.  Thats the way the smart people who actually made this program intended, I"m sure they have good reason for that :-> 

 

Well after you upload is converted to scx anyway so why not code directly in it . You dont need to worry about xml settings and because youa re using ascx you can also directly code in it to include tabid or tabname with request.querystring to give a bit more functionality to your skin

 

my 2 cts

 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Skins, Themes, ...Skins, Themes, ...Making a skin, or modding a skin?Making a skin, or modding a skin?


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