DotNetNuke 5 User's Guide Get Your Website Up and Running读书摘录4
Host Skin
The Host Skin option allows you to choose the primary skin that a DNN instance will use. By choosing either the Host or Site radio button, you will populate the drop-down list with skins. Skins at the host level are available to all websites within a DNN instance, whereas skins installed at the site level will be available only for the individual portal. We will look at skin installation in Chapter 4. For now, you won’t have any skins installed other than the four skins provided by default from the DNN installation (see Figure 3-15). The Preview link next to the drop-down list will take you to a page previewing the skin selected in the dropdown list. A quick tip regarding the preview mode; this does not save your changes. You still need to change your settings by clicking on Update at the bottom of the Host Settings page to save the skin change, or any other changes you’ve made to the page.
SEO – Search Engine Optimization
Throughout the book, we will mention the term ‘‘search engine optimization,’’ otherwise known as SEO. SEO is the theory and process of optimizing the content of your web pages and website for better indexing by the various search engines, such as Google, Microsoft’s Live Search, and Yahoo! This is done to try to make your pages show up higher in the search result listings, thus driving more traffic to your site. SEO is an art of its own, but we will try to point out elements within DNN that can assist you with better optimizing your website for the search engines.
Portal Skin
The Portal Skin setting defines the default skin that your portal will use. Defining the default portal skin is an important part of the configuration process, as this is the skin that will be used on all pages of your website that don’t have their own skin defined in the Page Settings. (Page Settings are discussed later in this chapter.) You should choose the most common skin that pages on your site should use. This will allow you to save on the amount of work necessary because you won’t have to configure most pages on your site manually, only the skin settings for pages that don’t use the portal skin.
Portal Container
The Portal Container setting defines the default container that the modules on your portal will use.
This setting will apply to all modules on your site, although you can override this setting in a couple of places. On individual pages, in the Page Settings, you can set a default container for the page; this would override the default container from the Site Settings. For individual modules on a page, you can also override the container in the Module Settings. We will cover Module Settings later in this chapter.
Edit Skin
The Edit Skin setting is definitely one of the most misunderstood options in DNN. In previous versions of DNN, this setting was called the Admin Skin. Although the name has changed, the functionality provided is still the same. To understand this, first consider how DNN handles and loads modules. In most cases, DNN will load multiple modules on a page, either into a single pane or into multiple panes. Every module has a View control, the default interface that users will see when they load a page that has the module on it. Most modules will also have a Settings control, in which you can configure the settings for the module, as well as an Edit control, in which you can interact with the content/functionality that the module provides. When you edit the module or go to the settings for a module, DNN will load only that particular control on the page. You will notice when you do this that all the other modules that were on the page go away. You can tell when your DNN site is loading an individual control by looking at the URL of the page; you will likely see ‘‘CTL’’ in the URL. For example, in the default configuration, DNN will load the Login
control using this functionality when you click on the Login link on your page. When we are on our home page, if we click on the Login link, we get a URL of the following format:
http://dnnbook/Home/tabid/38/ctl/Login/Default.aspx
Notice the /ctl/login/ section of the URL. This is a query string parameter telling DotNetNuke to load the Login control. You will notice similar functionality if you click on the Register link from your home page; DNN will load the Register controls.
http://dnnbook/Home/tabid/38/ctl/Register/Default.aspx
The edit and settings functionality for modules, along with the login and register controls, are loaded in the Edit skin, defined with the Edit Skin setting. In many cases, having the Edit Skin and the Portal Skin be the same is perfectly acceptable, although in other cases you might find that you want a cleaner, more concise (less graphics, panes, etc.) skin when you are editing or changing the settings for a module. You will also see this Edit Skin when you add/edit pages within DNN later in this chapter.
Edit Container
The edit container, like the edit skin, is used in the case where DNN is loading only a particular control. In most cases, this is only something administrators will see; however, as we’ve pointed out with the Login and Register links, it is possible that other users will see this container as well.
logo的目录
Appearance中的logo是存放在E:/webroot/DnnDemo/Portals/0文件夹下面的，即使我们上传本地文件作为网站的logo，它也会先将文件复制到E:/webroot/DnnDemo/Portals/0下载作为logo。
Home Directory
The Home Directory option is not a setting you can configure after the creation of a DNN portal, but it is something you can change during the portal-creation process. For your purposes, the Home Directory setting tells you where the files for this individual portal exist, from the root of your DotNetNuke folder. In Chapter 2, we created our DNN site in this directory:
c:/inetpub/wwwroot/DotNetNuke/
The Home Directory shows our portal’s directory is in Portals/0/, which equates to the local web server path of: C:/inetpub/wwwroot/DotNetNuke/Portals/0/
