I have three DNN skins but they are similar. The difference is the style of ContentPane. Is there any way to create some "master" skin with header and footer and three subskins with different styles of Content pane? Because it's a bad idea to create skins which have 99% same markup, the only difference is content pane style.
You could abstract the Header/Footer sections out in to their own ASCX files (referencing those from the main SKIN files), and then just have the Pane portion of the file be the differing part.
The other option would be to have One skin, with three different Panes, and instruct your users which PANE they should use in which scenario.
Related
I am new to DotNetNuke and come from a WP/Drupal background. I can't find any documentation on what I feel should just be a simple thing to do.
I need to have three different layouts, a Homepage layout which just uses a simple 12 column gird.
An InteriorA page where it uses a 9 col grid with a 3 col
Then an InteriorB page where it uses a 3-3-6-12 grid.
I dont see where I build and save these templates in code, then where to assign them to the pages I want to use them on.
Following up on the previous answer, resources available to you include the Xcillion theme that is provided with DNN installs. You will find the entire skin in /Portals/_defauilt/skins/Xcillion.
The "page layouts" are the .ascx files. The details of the layout are the "content panes" included in the .ascx files. They are the divs with IDs and the runat-server attribute.
You can define the layouts using different skin files, and then put content (modules) in the content panes that you would like to use. In other words, you can include the 3 layout possibilities in one .ascx, and place content appropriately.
The DNN Wiki has http://www.dnnsoftware.com/wiki/dotnetnuke-skins, with covers the basics of theming. You should be able to find more resources by Googling. One great resource on theme construction is DNN Hero's tutorials from DNN Creating. Start at dnnhero.com. This is a subscription service, though.
The location of these file is usually in a folder such as below:
\Portals_default\Skins
There are also skins which may be installed on a "portal" level:
These would be seen here:
\Portals\0\Skins
In here you should find a folder which is the name of the skin - And then the ASCX files for each individual skin file.
I has some problem, can anyone help?
how to change DNN 7 Mega2DNN to Standard DNN menu.
so it is one column going down
Thanks
The DDR Menu uses templates to conteol its behavior. Mega2DNN is one such template?
Assuming that the template is specified in your skin file, that's where you replace Mega2DNN with another template. Look at a skin file from the Gravity skin as an exmaple.
You will find a small collection of templates at http://dnnddrmenutemplates.codeplex.com/
The DNN Wike has a section on the DDR Menu, including a discussion of creating and configuring templates.
You may find it easy to modify an existing template, or you can create one from scratch. As for getting started, the ULTokens template creates a simple unordered list of links that you can style. The Superfish template creates a horizontal menu with dropdowns.
DNNCreative.com, a subscription site, has a nice tutorial
I've learned from THIS question that Skins, Containers and Modules are ASCX files but they weren't explained well. What are the differences of the these ASCX files?
Containers are "styling" for modules, but mainly just think of them as a Wrapper.
Modules provide Content and Functionality on your DNN website. The simplest way to think of a container, is to draw a box around the Content/Functionality in a module, that is your container.
If you notice the "careers 2.0" section of Stack Overflow on the right side of this page, the Careers 2.0" area at the top would be the module's title, while the list of jobs inside of that box would be the content provided by the module itself.
The skin provides the layout for a page. It will have sections to which modules can be added, called panes (e.g. ContentPane, LeftPane, HeaderPane, etc.).
Skins and containers are design elements, whereas modules provide functionality.
I'm new to Prism and have a conceptual question.
What I want to build is a Silverlight app that can load its layout (and the modules that are used) from a config file. Imagine I have a number of modules (e.g. a Chart, a Treeview and a Newsticker) and I want to use my config file to determine which of those are visible in my app and also where they are located on screen.
So if I want to have an app with just a Graph and a Treeview but not a Newsticker, would it be enough to just create an XAML file that contains views to those two modules? Would this XAML file be the shell?
Could I then have different XAML files/shells/config files to "generate" different looking applications at startup?
I don't need to switch layouts at runtime, I just want to be able to easily configure my application to use a different set of modules. I would appreciate pointers in the right direction.
Here are some approaches that I found:
http://blog.roundthecampfire.net/2011/10/creating-composable-ui-with-f-and-prism.html
http://www.dotnetpatterns.net/content/147-Lesson-2-Prism-creating-a-dynamic-region-layout-with-templates
I want to know about Drupal 7 module "Panels", and to know how to work on it, how it is useful in creating panes and customising it.
like the right top side in the below website. http://www.newsclick.in.
I would recommend you to look at this screencast:
http://dev.nodeone.se/node/770
Not just Panels but also how it works with page manager and views.
Kristoffer is correct. Looking at the right side of the website you linked, a lot of the functionality is found in views. You might use panels to handle appearance and views to address content. They work together very well. If your new to Drupal, I suggest you focus on the functionality and deal with the appearance after. Nodeone also has an excellent video series on Views called "Taming the Beast" which you will want to study before attempting to link views and panels.
Panels are mostly used to create customized layouts for multiple uses. You can create a page having different regions. It has a drag and drop content manager. Please read Panels module