DotNetNuke Skinning Whitepaper 翻译记录(文件组织部分)

翻译：

文件组织

 

皮肤可以应用到主机、站点或者频道级别。皮肤也可以应用到模块级别，但这时我们称其为容器。所有的皮肤文件保存在portals文件夹下。有一个名为_default的特殊文件夹代表主机的文件夹，然而每一个站点都有在以他们在数据库中的ID为名字的单独文件夹。这样的结构使得整个网站中需要读写权限的文件夹集中到一个单一的文件夹里。同时使得文件的物理组织和应用程序当中的逻辑应用联系起来，这样就不需要外部数据库支持就可以管理两者之间的关系。

皮肤和容器可以包含不限数量的子文件夹– 每个文件夹代表构成皮肤必须的一个文件包。子文件夹以皮肤的名称来保存。使用名称增加了不同皮肤间重名的可能性，然而这样当你直接通过文件系统管理文件的时候就不必考虑要和外部数据源保持一致的问题。

原文：

File Organization

 

Skins can be applied at a host, portal, or tab level. Skins can also be applied at the module level; however, in this case we refer to them as Containers. All skin files are organized under the Portals folder. A special _default subfolder is used to designate the Host directory tree; whereas, each portal has its own directory tree named according to its ID in the database. This structure centralizes the “write-access” requirements to a single folder structure in your website. It also ties the physical organization of files with their logical usage within the application which means there is no external database required to manage the relationships.

   

Skins and Containers can contain an unlimited number of subfolders – each subfolder representing a package of files necessary to render a skin. Subfolders are stored according to skin name. Using a name may increase the chance of naming collisions between skins but it also allows you to manage your files directly on the file system without worrying about reconciling the changes to an external data source.

DotNetNuke Skinning Whitepaper 翻译记录：
DotNetNuke Skinning Whitepaper 翻译记录(简介部分)
DotNetNuke Skinning Whitepaper 翻译记录(术语与win客户端程序部分)
DotNetNuke Skinning Whitepaper 翻译记录(技术部分)
DotNetNuke Skinning Whitepaper 翻译记录(定义部分)
DotNetNuke Skinning Whitepaper 翻译记录(DotNetNuke部分)
DotNetNuke Skinning Whitepaper 翻译记录(总揽部分)