DotNetNuke Skinning Whitepaper (definition section)

Translation: Definition

Another important aspect to consider in any skin solution is the definition of the skin author. Who will create skin? What technology suits them better. What kind of design tools are used in their daily work. Demand analysis in this area has far-reaching implications for determining how the skin is defined.

Although ASP.net's user-control technologies provide us with strong core support, they are relatively new technologies for Microsoft's platform. Some design tools (such as. FrontPage, DreamWeaver, etc.) already provide support for user control technology. But in this concept for some professional web designers are still unfamiliar. aside, the user control contains a property that is not known to the designer in the ASP.net server-side control. The risk of a web designer disrupting or removing important server-side controls must be avoided. Basically we want web designers to choose their own tools to design skins and keep separate from the user controls.

The conclusion is that the final skin solution should allow web designers to create skins through simple and basic techniques. HTML is the most basic common language for the World Wide Web and is widely supported by Web design tools. The only problem is that HTML is static-and Web applications require dynamic elements.

Summarizing the above description of the solution, it is useful to allow designers to insert markers in HTML instead of dynamic content. This provides a good abstraction of forms and functions (fuction). The skin file does not affect the application logic when it is modified. Application logic can also be redefined without affecting the user interface. The only problem is that the additional business layer lowers the performance of the application.