Dnn skin application and production FAQs

Although I have been in contact with dnn for some time, there are still some mistakes in skin application and production. Therefore, I wrote the experience in the form of Q &, hope it will be helpful to people later!
Application Section:
Question 1: What is dnn skin?
A: dnn skin, in short, is the appearance of the website. With Skin technology, you can easily change the appearance of your website. The introduction of skin allows you to create a beautiful site without having to have the knowledge of art engineers, because you can download your favorite skin from a skin website and load it to your site, it is as convenient as buying clothes.
Question 2: Can a website use only one dnn skin?
A: A website can use multiple or even multiple skin sets. Each webpage can correspond to one skin. This skin can be multiple skin sets from a host or site.
Question 3: How to specify a skin for each webpage?
A: Log on as an administrator, open the page of the skin style you want to specify, click "edit", enter the editing status, and click "Advanced Settings ", in "Page skin", select the desired skin and save the settings.
Question 4: What is a dnn container?
A: Simply put, the dnn container is the skin of the dnn module.
Question 5: Can all website modules use the same dnn container?
A: The website module can correspond to a container, which can be multiple containers from the host or site.
Question 6: How do I specify a container for each module?
A: Log on as an administrator, click "Settings" of the corresponding module to enter the setting status, click "page settings", and select the container you need in the "Module window, save the settings.

Development Section:
Question 1: Is the skin developed using HTML or ascx?
A: skin can be developed both in HTML and in ascx. According to my observation, the mechanism of dnn to generate skin is as follows. First, check whether there is HTML in the skin bag. If yes, convert it to HTML and skin. XML combination to generate ascx. If no, It extracts ascx, so the final result is the same. Dnn actually uses ascx.
Question 2: If HTML is used for development, what files should be included in the skin package?
A: HTML is used for development. The skin package should contain at least one HTML file and skin. XML, skin. CSS: an image file with the same name as HTML. If you use image resources, you need to include the corresponding image.
The HTML file describes the location of each function tag, such as: Where the copyright statement is placed; skin. the XML file declares the functional tags required for the skin package. Skin. CSS is a stacked style sheet file that defines various styles. html images with the same name are used for skin preview.
Question 3: What files should be included in the skin package if it is developed using ascx?
A: Developed Using ascx, the skin package should contain at least one ascx file and skin. CSS, an image file with the same name as HTML. If you use image resources, you must also include the corresponding image.
The ascx file declares the functional tags to be used and the location of each functional tag, for example, where the copyright statement is placed, and skin. the XML file declares the functional tags required for the skin package. Skin. CSS is a Cascading Style Sheet file that defines various styles. images with the same name as ascx are used for skin preview.
Question 4: How do I know the meaning of each function label?
A: In the dnn technical document, there is a document specifically about skin development, dotnetnuke skinning guide. Its appendix B specifically describes the meaning of each function label.
Question 5: Can I write contentpane: 2 in HTML? Why?
A: You can instantiate it directly, for example, x1contentpane and x2contentpane... xncontentpane.