DotNetNuke Skinning Whitepaper (DotNetNuke part)

In DotNetNuke 1.0.0 to version 1.0.10, there is only a relatively simple skin-handling mechanism that allows users to create a less customizable site by modifying the logo, color, and style of the site. However, it is not long before the DotNetNuke development team realizes that such a mechanism does not meet most of the performance layer requirements, and starts several projects to achieve a more dynamic skin solution.

Unfortunately, there are many different views on the best solution, and the progress of the requirements analysis has stalled. Most of these ideas come with a technology implementation and soon a lot of valuable advice about the skin system is presented in the community-all of which have their own strengths and weaknesses. How to choose these solutions as the core program of DotNetNuke is a very stressful thing. In fact, we didn't accept any of the options, around all the business needs, and, as we understand it, we carefully set up an imperfect standard and released a solution for testing, and try to refine it in practice.

DotNetNuke 2.0 has a massive rewrite of the core portal framework that initially modifies only the data access layer and business logic layer, but it is obvious that the presentation layer must be reviewed and rewritten to achieve our goal. DotNetNuke now has a strong skin system that enables the separation of forms and functions (function), and in the next part of the document we will introduce the detailed technical implementation of this skin system.