Models of Web Community Design
As a project leader, you want to moderate the interaction among websites in a web community and to develop a full-scaled structure that has a scope of whole picture than to design details.
However, according to previous experience, many students would have difficulties to comprehend the complications. If you do not have a full vision in your mind yet, you may go to 'Website Structure' in the first place then come back latter.
Web Community Structure 網群結構
Web Community is organized by 'Main Web' and 'Sub Webs', or by 'Portal Web' and 'Satellite webs'. The former usually refer that webs are established in a same host, while the latter may include webs in different hosts.
There are 2 models for web community structure: hierarchical model and relational model.
Hierarchical Model 網群階層模式設計
Physically, all sub webs are the subdirectory of the main web. It is the reason the main web is used to be named as 'Root Web'.
The advantage of this model is easy to grant authorization by hierarchical levels.
It is proper for organizations require:
-High necessity of monitoring and control.
-High consistency of the style of presentation and its synchronic change.
Most of intranet in business are by this model.
Physically, main web and sub webs are relational virtual directories. They do not have a upper or lower relationship to each other, though they may look like that. The webs only share some same "relations" such as virtual directories, redirections( scripts, or pages with meta tags). It is used to have a parallel physical structure, however, it could even be totally independently existing in different drives, hosts, even places.
The main web is a virtual portal under this model.
The advantage of this model is easy to develop loose collaboration by flexible missions.
It is proper for organizations designate:
-Low requirement of monitoring and control.
-Encouraging pluralistic styles among the sub webs.
This model is fit for loose communities, free lancers, .experimental activities, and non profit organizations.
Hybrid models 網群混合模式設計
Visual Virtual Structure Design 虛擬結構設計
Step 1: IIS
Define a Virtual Directory such as "VSite"
to a Physical Folder such as "PFolder" which could be any where.
Step 2: Expression Web/SharePoint Designer
Create a Sub Server Expression Web as "VSite" under the Virtual Root Web.
You have a "VSite" under the Virtual Root Web that is different from the "PFolder" under any Physical Directory.
Physical Structure Design 實體結構設計
EXAMPLE: Common websites
Their physical structure is the same as the Path of their URL address.
Hybrid Design Effects 綜合效果
It is a good idea to prevent internet attacks.
For example, Code Red and its derivatives are used to be a very famous virus that will replace the homepage of targeted website. However, it is not able to do it, if the web community has a hybrid design.
Canonical Page/ Canonical URL
When you have too many virtual addresses for single page, use "canonical URL" to improve the performance of SEO.
<link rel="canonical" href="http://Server/Path/Canonical Page.htm" />
html5 的<link> 是變動較大的一個標籤，其中 rev (reverse relation) 屬性已經取消，與前版相容性要注意。
rel 屬性可以用在多個標籤，表示 relation 關聯的意義。
注意："canonical" 是 Google 結合業者創造的值，不是 html5 的制定值，但可與 html5 相容。
在網頁的 <head> 部分加入 <link> 元素和 rel="canonical" 屬性與值，將該網頁指定為搜尋引擎使用的標準網頁。如此只會為其中一個版本建立索引並納入搜尋結果中，可提高這個網頁在搜尋結果中的順序」。
在每個非標準 HTML 網頁中的 <head> 部分加入 rel="canonical" 連結，如上例。
是建議，這個新選項可讓網站擁有者建議 Google 將哪一個版本的網頁視為標準網頁。Google 確定哪些網址集包含完全相同的內容的同時，會考量此建議和其他資訊，並計算出與這些網頁關聯性最高的網址，顯示在搜尋結果中。
進階：使用 HTTP 標頭：Link 法
以上限制以HTML為標準網頁。若要使用其他檔案類型，如pdf，要改用 Link rel="canonical" HTTP 標頭法，如下所示：
link: <http://Server/Path/Canonical Page.pdf>; .rel="canonical"
HTTP Redirects <httpRedirect>
ID of USER group.
If you will use either intranet or LAN to maintain the site, the Autonomy folders have to be set as shared folders.
For intranet, the encoding of special symbols are different. Such as: the & is different from %26 for intranet address while it is the same for internet address.
Expression Web/SharePoint Designer
ID of ADVANCED PRODUCERS.
Root and Web Server Extension
The Virtual Root could be any web at any place.
However, you want to install the web server extension to the Physical Root. Thus, the physical root should be a web instead of a folder.