DotNetNuke Skinning Whitepaper (Skin package part)

A skin or container package consists of a large number of documents that form a complete skin:

*.htm, *.html file--the skin definition file used to create *.ascx files in the skin upload mechanism.

*.ascx file--the skin mechanism must format and precompile the HTML file to create a user control that defines the skin.

*.CSS file--The style sheet file that corresponds to the skin.

*.gif, *.jpg, *.jpeg, *.png--a graphic file in the skin.

*.*--Other resource files that are used in your skin (note that you need to allow uploads in the site upload file extension settings.) ）

A skin package can contain multiple skin files, which allows designers to create multiple skin lines that have the same picture but differ slightly in layout. Obviously, when you're going to make changes to the regular presentation layer, the more skin files you have, the more work you need.

Most "package" systems use the concept of a file list to identify the various files in a package and define additional parcel attributes. While this concept facilitates the performance of raw data, additional creation and maintenance work is introduced. For product maintenance, our main view is that simply compressing these files into a single compressed package is more beneficial than introducing a list.