規劃 SharePoint Server 中跨網站發佈用的製作網站Plan authoring sites for cross-site publishing in SharePoint Server

摘要:了解如何規劃 SharePoint Server 跨網站發佈解決方案的製作網站集合。Summary: Learn how to plan authoring site collections for a SharePoint Server cross-site publishing solution.

當您使用 SharePoint Server 的跨網站發佈時,您可以使用一或多個製作網站集合撰寫及儲存內容,以及使用一或多個發佈網站集合控制網站的設計及顯示內容。本文說明如何規劃跨網站發佈解決方案的製作網站。When you use cross-site publishing in SharePoint Server, you use one or more authoring site collections for authoring and storing content, and one or more publishing site collections to control the design of the site and show content. This article describes how to plan authoring sites for your cross-site publishing solution.

本文是以<SharePoint Server 的跨網站發佈概觀>中的資訊為基礎。閱讀完本文之後,請務必閱讀下一篇文章<規劃 SharePoint Server 中供網站間發佈用的製作網站>。This article builds on the information in Overview of cross-site publishing in SharePoint Server. After you finish reading this article, make sure that you read the next article, Plan publishing sites for cross-site publishing in SharePoint Server.

規劃 SharePoint 製作網站的網站集合和網站結構Plan site collections and site structure for SharePoint authoring sites

製作網站集合必須啟用 SharePoint Server 的 [跨網站集合發佈] 功能。建議您使用「產品型錄網站集合」範本建立製作網站集合,因為使用該範本時,預設會啟用 [跨網站集合發佈] 功能。如果使用未啟用 [跨網站集合發佈] 功能的網站集合範本,則必須啟用此功能。此外,如果使用不會建立發佈網站的網站集合範本 (例如「小組網站」範本),並想使用發佈功能 (例如核准工作流程和排程),也必須啟用這些發佈功能。如需啟用跨網站發佈功能的資訊,請參閱<在 SharePoint Server 中設定跨網站發佈>中的<啟用跨網站集合發佈功能>。如需如何在非發佈網站的網站上使用發佈功能的詳細資訊,請參閱<發佈功能概觀 (SharePoint Server 2010)>。如需如何啟用發佈功能的資訊,請參閱<啟用發佈功能>。如需如何設計跨網站發佈解決方案之邏輯架構的詳細資訊,請參閱<規劃 SharePoint Server 跨網站發佈的邏輯架構>。Authoring site collections must have the SharePoint Server Cross-Site Collection Publishing feature activated. We recommend that you use the Product Catalog Site Collection template to create authoring site collections because the Cross-Site Collection Publishing feature is activated by default when you use that template. If you use a site collection template that does not have the Cross-Site Collection Publishing feature activated, you must activate it. Additionally, if you use a site collection template, such as the Team Site template, that does not create a publishing site, and you want to use publishing features such as Approval workflows and scheduling, you must also activate those publishing features. For information about activating the Cross-Site Publishing feature, see "Activate the Cross-Site Collection Publishing feature" in Configure cross-site publishing in SharePoint Server. For more information about how to use the publishing features on a site that is not a publishing site, see Publishing features overview (SharePoint Server 2010). For information about how to activate the publishing features, see Enable publishing features. For more information about how to design the logical architecture for a cross-site publishing solution, see Plan the logical architecture for cross-site publishing in SharePoint Server.

由於跨網站發佈分隔製作環境和發佈環境,因此製作網站的結構可能與發佈網站的結構不同。當您規劃如何結構化製作網站時,請考慮下列清單中的問題。Because cross-site publishing separates the authoring and publishing environments, the structure of an authoring site can differ from the structure of the publishing site. As you plan how to structure authoring sites, consider the questions in the following list.

  • 您應該針對內容使用頁面庫或清單?Should you use a Pages library or a list for content?

    在 SharePoint Server 2010 中,發佈網站使用頁面庫儲存顯示給使用者的 HTML 內容。透過 SharePoint Server 的跨網站發佈功能,您也可以使用清單及其他文件庫儲存在發佈網站上重複使用的內容。當您規劃儲存此內容的位置時,請考慮內容類型及您想使用內容的方式。一般而言,如果您想撰寫 HTML 內容,建議您使用頁面庫而不是清單。比起清單,頁面庫包含下列優點:In SharePoint Server 2010, publishing sites used Pages libraries to store HTML content that was shown to users. By using cross-site publishing in SharePoint Server, you can also use lists and other libraries to store the content that is reused on the publishing sites. When you plan for where you can store this content, consider what the content is and how you plan to use it. In general, if you plan to author HTML content, we recommend that you use a Pages library instead of a list. A Pages library has the following benefits over a list:

    • 您可以建立更「所見即所得」(WYSIWYG) 的製作網頁環境,讓作者概略了解內容在發佈網站上的外觀。You can create a more WYSIWYG environment for authoring pages to give authors an idea of how their content will appear on the publishing site.

    • 您可以搭配頁面庫使用變化和翻譯,以建立多語內容。You can use variations and translation with a Pages library to create multilingual content.

    • 您可以使用核准工作流程路由傳送頁面庫內容以供檢閱及核准。搜尋系統不會編製未核准發佈之頁面的索引,因為這些頁面在發佈後才會標示為主要版本。You can use the Approval workflow to route Pages library content for review and approval. The search system will not index pages that are not approved for publishing because they are not marked as major versions until they are published.

    • 您可以使用排程指定內容何時可用。搜尋系統不會編製未排程發佈之頁面的索引。這是因為這些頁面在發佈後才會標示為主要版本。You can use scheduling to specify when content will be available. The search system will not index pages that have not been scheduled for publishing. This is because pages are not marked as major versions until they are published.

  • 您必須具有多少頁面庫?How many Pages libraries do you have to have?

    使用頁面庫的主要缺點是每個網站只能有一個頁面庫。根據您規劃建立的頁面內容數量,一個大型的目錄在發佈網站上可能很難使用,因為設定顯示內容的查詢會更複雜且更花時間。因此,當您規劃頁面內容時,請考慮要建立的內容數量,以及是否應該將內容儲存在一起。如果您想在不同的目錄中儲存頁面內容,則必須在製作網站階層中建立不同的網站,然後將每個網站中的頁面庫作為目錄共用。接著即可從一或多個發佈網站連線至這些目錄。The primary drawback to using a Pages library is that you can have only one Pages library per site. Depending on how much Pages content you plan to create, a single, large catalog can be difficult to consume on publishing sites because the queries that show content are more complex and time-consuming to configure. Accordingly, when you plan Pages content, consider how much content you will create and whether the content should be stored together. If you want to store Pages content in separate catalogs, you must create separate sites within the authoring site collection hierarchy, and then share the Pages library in each site as a catalog. You can then connect to these catalogs from one or more publishing sites.

    例如,在含有知識庫網站的內部網路案例中,您可能想將疑難排解文章與使用者手冊分開,因為這些文章是由不同的使用者群組所撰寫。在製作網站集合中,您可以建立一個網站在其頁面庫中儲存疑難排解文章,並建立另一個網站在其頁面庫中儲存使用者手冊。將這兩個頁面庫作為目錄共用之後,您可以從相同的發佈網站連線至這些目錄,並使用不同的網頁組件顯示這兩種內容類型。For example, in an intranet scenario in which you have a knowledge base site, you might want to keep troubleshooting articles separate from user manuals because they are authored by different groups of people. In the authoring site collection, you create one site to store troubleshooting articles in its Pages library, and another site to store user manuals in its Pages library. After you share both Pages libraries as catalogs, you can connect to them both from the same publishing site, and show the two types of content by using different Web Parts.

  • 您必須具有多少製作網站集合?How many authoring site collections do you have to have?

    除了決定必須在單一製作網站集合中具有的網站數目之外,您也應該考慮是否必須具有其他製作網站集合。如果內容作者位於具有不同安全性需求的不同群組中,或位於不同的地理位置,則可以使用多個製作網站集合。例如,在外部網路案例中,您可以針對 Active Directory 網域服務 (AD DS) 中特定群組的內部內容作者使用一個製作網站集合,並針對使用表單型驗證連線至網站的外部內容作者使用另一個製作網站集合。您可以在 Web 應用程式與伺服器陣列之間共用目錄,因此不需要將製作網站限制在單一 Web 應用程式或伺服器陣列。請決定您必須具有的製作網站集合數目,然後規劃要在每個網站中包含的目錄。In addition to deciding how many sites you must have in a single authoring site collection, you should also consider whether you have to have additional authoring site collections. You might use more than one authoring site collection if the content authors are in separate groups that have different security requirements, or are in separate geographical locations. For example, in an extranet scenario, you might use one authoring site collection for internal content authors who belong to a specific group in Active Directory Domain Services (AD DS), and a separate authoring site collection for external content authors who connect to the site by using forms-based authentication. Catalogs can be shared across web applications and farms so that you do not have to restrict authoring sites to a single web application or farm. Decide how many authoring site collections you must have, and then plan which catalogs to include in each site.

  • 您是否想使用變化建立多語內容?Do you plan to use variations to create multilingual content?

    您是否必須以多種語言提供內容?即使目前規劃只建立及發佈一種語言的內容,請考慮此商務需求是否在未來可能變更。如果最後有可能需要使用網站變化,則應該現在就規劃使用變化。透過現在設定網站結構以配合變化,您可以在未來為自己及組織節省時間和資源。如果您必須在稍後切換使用變化時變更網站結構,通常會比較困難,而且可能會影響您為網站規劃的 URL。如果您規劃使用變化和跨網站發佈,則必須將每個變化標籤建立為製作網站集合中的個別網站。您可以將每個變化網站中的頁面庫作為目錄共用,然後您可以將每個發佈網站集合連線至符合其地區設定的目錄。如需變化的詳細資訊,請參閱<SharePoint Server 中的變化概觀>。如需如何規劃變化的詳細資訊,請參閱<SharePoint Server 中多語系跨網站發佈網站的規劃變化>。Do you have to provide content in more than one language? Even if you currently plan to only create and publish content in a single language, consider whether that business requirement might change in the future. If you might eventually want to use variations on the site, you should plan for using variations now. By setting up the site structure now to accommodate variations, you can save yourself and your organization time and resources in the future. If you have to change the site structure when you switch to using variations later, it is often more difficult and can affect the URLs that you planned for your sites. If you plan to use variations and cross-site publishing, each variation label has to be created as a separate site within the authoring site collection. You share the Pages library from each variation site as a catalog, and then you connect each publishing site collection to the catalog that matches its locale. For more information about variations, see Variations overview in SharePoint Server. For more information about how to plan variation sites, see Plan variations for multilingual cross-site publishing site in SharePoint Server.

  • 您必須在製作網站上使用的導覽類型為何?What kind of navigation do you have to have on the authoring site?

    雖然您可以在製作網站上使用受管理的導覽,讓製作網站類似發佈網站,但是這麼做可能會讓內容作者感到困惑。建議您在製作網站上使用結構化的導覽,讓作者更容易建立內容。請考慮要在製作網站上建立及儲存的內容類型。大多數的內容是否為儲存在頁面庫中的 HTML 內容?或者您是否想手動建立或匯入清單資料?如果您保持簡單的製作網站及任何清單和文件庫結構,則內容作者可更容易建立內容。Although you can use managed navigation on the authoring site so that the authoring site resembles the publishing site, this can confuse content authors. We recommend that you use structured navigation on the authoring site to make it easier for authors to create content. Consider the kind of content that will be created and stored on the authoring site. Will most content be HTML content that is stored in the Pages library? Or will you manually create or import list data? If you keep a simple structure for the authoring site and any lists and libraries, it makes it easier for content authors to create content.

規劃 SharePoint 製作網站的安全性Plan security for SharePoint authoring sites

規劃製作網站的安全性與規劃 SharePoint Server 中其他大多數網站的安全性一樣。請考慮下列問題:You plan security for authoring sites in the same way that you do for most other sites in SharePoint Server. Consider the following questions:

  • 誰應該具有權限建立包含在製作網站中的不同內容類型?Who should have permissions to create the different kinds of content that is contained within the authoring site?

  • 誰應該具有建立頁面內容的權限?Who should have permissions to create Pages content?

  • 同一組人員也可以建立清單內容,或者要由不同的群組負責該內容?Can the same group of people also create list content, or is a separate group responsible for that content?

  • 如果您想使用核准工作流程,應在核准者群組中包含哪些成員?If you plan to use the Approval workflow, who should be included in the Approvers group?

如需安全性的資訊,請參閱<SharePoint Server 中的網站和內容權限規劃>。For information about security, see Permissions planning for sites and content in SharePoint Server.

當您啟用目錄的匿名存取時,可以將製作網站的安全性與其在搜尋中的表示方式分開處理。啟用匿名存取時,發佈網站上的匿名使用者可以搜尋及檢視索引內容。但是,如果您變更目錄中個別項目的權限,搜尋系統會採用這些權限,且匿名使用者將無法使用限制為特定群組的任何項目。這會在您規劃與匿名使用者共用內容時提供更高彈性。When you enable anonymous access for a catalog, security on the authoring site can be treated independently from how it is represented in search. When anonymous access is enabled, indexed content is searchable and viewable to anonymous users on the publishing site. However, if you change permissions to individual items in the catalog, those permissions are respected by the search system, and any items that are restricted to certain groups will not be available to anonymous users. This allows for greater flexibility when you plan to share content with anonymous users.

您也必須規劃授與編目程式存取製作網站集合內容的權限。編目程式使用預設內容存取帳戶。如果預設內容存取帳戶不具有內容的最低「讀取」權限等級,則無法編製內容的索引,且此內容無法供發佈網站集合上的查詢使用。您可以使用預設內容存取帳戶,或使用編目規則指定在編目特定內容時使用其他內容存取帳戶。如需詳細資訊,請參閱<在 SharePoint Server 中規劃編目及同盟>中的<規劃編目程式驗證>。You must also plan to grant the crawler access to content on authoring site collections. The crawler uses a default content access account. If the default content access account does not have at least Read permission level to content, the content is not indexed and is not available to queries on publishing site collections. You can use the default content access account, or you can use crawl rules to specify a different content access account to use when crawling particular content. For more information, see "Plan crawler authentication" in Plan crawling and federation in SharePoint Server.

規劃 SharePoint 製作網站的設計和品牌Plan design and branding for SharePoint authoring sites

如本文稍早所述,製作網站的結構與發佈網站的結構不同。同樣地,這些網站的外觀也可能不相同。如果您想讓內容作者享有製作網站的 WYSIWYG 使用者經驗,您可以使用類似的主版頁面、頁面配置及階層式樣式表設計製作網站。但是,實際發佈網站可能會因為品牌或其他需求而有不同的設計。因此,製作網站不會提供完整的 WYSIWYG 體驗。As was mentioned earlier in this article, the structure of the authoring sites can differ from the structure of publishing sites. Likewise, the appearance of those sites can also be very different. If you want content authors to have a WYSIWYG user experience on the authoring site, you can use similar master pages, page layouts, and cascading style sheets to design the authoring site. However, the actual publishing sites might have different designs because of branding or other requirements. Therefore, the authoring site will not provide a complete WYSIWYG experience.

即使您不想將發佈網站上所使用的相同品牌套用至製作網站,只要您想使用頁面庫內容,仍必須規劃作者將使用的基本頁面配置。當您規劃製作網站的設計時,請考慮下列問題:Even if you do not plan to apply the same branding to the authoring site that you use on the publishing site, if you plan to use Pages library content, you still have to plan for the basic page layouts that authors will use. As you plan the design of the authoring site, consider the following questions:

  • 您必須具有哪些網站欄?您可以將網站欄作為頁面欄位新增至頁面配置以保留更多內容,例如受管理的中繼資料。What site columns must you have? Site columns can be added as page fields to page layouts to hold additional content, such as managed metadata.

  • 您必須具有哪些內容類型?您可以建立使用「文章頁面」內容類型的自訂內容類型,作為上層內容類型。您可以將網站欄新增至自訂內容類型,這些網站欄會作為頁面欄位包含在您使用自訂內容類型建立的任何頁面配置中。What content types must you have? You can create custom content types that use the Article Page content type as the parent content type. You can add site columns to the custom content type, which will be included as page fields in any page layouts that you create by using the custom content type.

  • 是否可以使用預設主版頁面?您可以使用預設主版頁面,或建立要在製作網站上使用的新主版頁面。Can you use the default master page? You might use the default master page, or create a new master page to use on the authoring site.

  • 您必須具有哪些頁面配置?您可以建立包含特定頁面欄位的自訂頁面配置。例如,在含有知識庫的內部網路案例中,您可以為疑難排解指南和使用者手冊建立不同的頁面配置。What page layouts must you have? You can create custom page layouts that contain specific page fields. For example, in an intranet scenario in which you have a knowledge base, you might create separate page layouts for troubleshooting guides and user manuals.

有關製作網頁的資訊,請參閱<SharePoint 網頁模型概觀>、<Plan content types and workflows in SharePoint 2013>、<規劃網頁 (SharePoint Server 2010)>和<規劃網頁製作 (SharePoint Server 2010)>。For information about authoring web pages, see SharePoint page model overview, Plan content types and workflows in SharePoint 2013, Plan Web pages (SharePoint Server 2010) and Plan Web page authoring (SharePoint Server 2010).

規劃 SharePoint 製作網站上用於標示內容的字詞組Plan term sets for tagging content on SharePoint authoring sites

您可以使用字詞組標示目錄內容,例如製作網站上的頁面或清單項目。如此一來,字詞即可協助將內容分類至不同的階層。稍後會在發佈網站上使用相同的字詞發出查詢、顯示類別和目錄項目頁面的相關資訊、建立易記 URL,以及進行受管理的導覽。當您規劃用於標示內容的字詞組和字詞時,請考慮階層的結構方式。您可以將多個標示字詞組的字詞合併為一個自訂字詞組,以便在發佈網站上進行導覽。您不需要為製作網站上的標示字詞組建立一個高度複雜的結構。此外,請考慮 URL 在發佈網站上的外觀,以及規劃建立可協助使用者找到想要搜尋之目標的字詞。例如,如果您的第 1 層字詞稱為 Computers,底下的第 2 層字詞稱為 Laptops,且目錄項目名稱為 CM61438,顯示該模型的頁面易記 URL 會是 http://contoso.com/computers/laptops/CM61428。如需詳細資訊,請參閱<[Plan terms and term sets in SharePoint Server 2013](http://technet.microsoft.com/library/7f8f6beb-aaa6-4277-b522-d28a5b746087%28Office.14%29.aspx)>和<[規劃 SharePoint Server 中的導覽字詞組](plan-navigation-term-sets.md)>。You use term sets to tag catalog content such as pages or list items on the authoring site. By doing this, terms help categorize the content into a hierarchy. These same terms are later used on the publishing site to issue queries, show information about category and catalog item pages, create friendly URLs, and for managed navigation. When you plan the term sets and terms to use for tagging content, consider how you want the hierarchy structured. You can combine terms from more than one tagging term set into a single customized term set for navigation on the publishing site. You do not have to create a single, highly complex structure for the tagging term set on the authoring site. Also consider how you want the URLs to look on the publishing site, and plan to create terms that will help users find what they want. For example, if you have a level 1 term called Computers, and underneath that, a level 2 term called Laptops, and the catalog item name is CM61438, the friendly URL for the page that shows that model will be http://contoso.com/computers/laptops/CM61428. For more information, see Plan terms and term sets in SharePoint Server 2013, and Plan navigation term sets in SharePoint Server.

如需建立標示內容之字詞組的資訊,請參閱<在 SharePoint Server 中設定跨網站發佈>中的<建立及管理在撰寫網站上標示內容的字詞組>。For information about creating term sets for tagging content, see "Create and manage term sets for tagging content on authoring sites" in Configure cross-site publishing in SharePoint Server.

規劃 SharePoint 製作網站的目錄內容Plan catalog content for SharePoint authoring sites

目錄包含跨網站集合重複使用的內容。您可以使用頁面庫中的 HTML 內容、清單中的資料,或資產庫中的圖片和視訊等資產。例如,在網際網路商務案例中,您可以使用清單顯示產品型錄;或在內部網路案例中,您可以使用頁面庫顯示知識庫文章目錄。在任一範例中,您也可以具有與內容相關聯的資產,例如產品的圖片或說明疑難排解步驟的影片。本節說明如何規劃製作網站中的不同目錄內容類型。Catalogs contain the content that is reused across site collections. You can use HTML content in a Pages library, data in a list, or assets such as pictures and video in an asset library. For example, in an Internet business scenario, you might use a list to show a catalog of products, or in an intranet scenario, you might use a Pages library to show a catalog of knowledge base articles. In either example, you might also have assets that you want to associate with content, such as pictures of products or videos that explain troubleshooting steps. This section describes how to plan for different kinds of catalog content in an authoring site.

如需如何將文件庫或清單啟用為目錄的資訊,請參閱<在 SharePoint Server 中設定跨網站發佈>中的<以目錄共用文件庫或清單>。For information about how to enable a library or list as a catalog, see "Share a library or list as a catalog" in Configure cross-site publishing in SharePoint Server.

規劃頁面庫Plan Pages libraries

決定要在一或多個頁面庫中儲存內容,以及分隔內容的方式之後,請考慮下列問題:After you decide whether to store content in one or more Pages libraries, and how to divide content between them, consider the following questions:

  • 要與頁面庫內容相關聯的字詞組為何?What term set will you associate with Pages library content?

    如果使用頁面庫,您必須規劃至少將一個受管理的中繼資料網站欄新增至「頁面配置內容類型」,然後將網站欄連結至標示字詞組。當內容作者建立使用該內容類型的新頁面時,可以選取要用於標示頁面的字詞。例如,在內部網路知識庫案例中,您可以使用名為「文章類型」的標示字詞組,其中包含「疑難排解指南」和「使用者手冊」的不同字詞。您可以建立網站欄「文章類型」並連結至「文章類型」字詞組,然後將其新增至「文章頁面」內容類型。當內容作者建立新頁面時,必須從可用的「文章類型」字詞清單中選擇字詞。若將頁面庫作為目錄共用,則必須選取受管理的中繼資料欄,以作為發佈網站上的導覽字詞組。如需詳細資訊,請參閱本文稍早的<規劃 SharePoint 製作網站上用於標示內容的字詞組>。If you use a Pages library, you must plan to add at least one managed metadata site column to a Page Layout Content Type, and link the site column to a tagging term set. When a content author creates a new page that uses that content type, they will be able to select a term with which to tag the page. For example, in the intranet knowledge base scenario, you might have a tagging term set that is named Article Types that contains separate terms for Troubleshooting Guides and for User Manuals. You can create a site column called Article Type that is linked to the Article Types term set, and add it to the Article Page content type. When a content author creates a new page, they must choose a term from the list of available Article Types terms. When the Pages library is shared as a catalog, you have to select that managed metadata column as the one to use as a navigation term set on the publishing sites. For more information, see Plan term sets for tagging content on SharePoint authoring sites earlier in this article.

  • 您還必須將哪些其他欄位新增至「頁面配置內容類型」?What other fields must you add to the Page Layout Content Type?

    除了規劃標示欄位以便導覽之外,您還應該考慮要新增至「頁面配置內容類型」的其他任何欄位。這些欄位可以是連結至其他字詞組之其他受管理的中繼資料欄位,或其他類型的欄位 (例如超連結、數字,以及日期和時間)。發佈頁面內容類型預設包含 [頁面內容] 欄位。 這可讓內容作者使用 RTF 編輯器將 HTML 和圖像插入頁面。您可以根據建立的內容,建立包含不同欄位的不同頁面配置。例如,在內部網路知識庫案例中,您可以為包含 [套用到] 或 [文章編號] 等欄位的「疑難排解文章」使用一種頁面配置,並為包含 [產品名稱] 或 [型號] 等欄位的「使用者手冊」使用另一種頁面配置。當您規劃頁面庫內容時,請決定需要的其他網站欄和內容類型、需要的頁面配置,以及哪些欄位應移至哪個頁面配置。如需詳細資訊,請參閱 SharePoint 2013 頁面模型的概觀In addition to planning the tagging field for navigation, you should consider any other fields that you want to add to a Page Layout Content Type. These can be other managed metadata fields that are linked to other term sets, or other kinds of fields, such as hyperlinks, numbers, and dates and times. By default, publishing page content types contain a Page Content field. This lets content authors insert HTML and images onto a page by using a rich text editor. You can create different page layouts that contain different fields, based on the content that is created. For example, in the intranet knowledge base scenario, you can use a page layout for Troubleshooting Articles that contains fields such as Applies To or Article Number, whereas you can use a page layout for User Manuals that contains fields such as Product Name or Model Number. As you plan Pages library content, decide what other site columns and content types are needed, what page layouts are needed, and which fields should go in which page layout. For more information, see SharePoint page model overview.

如需詳細資訊,請參閱<規劃網頁 (SharePoint Server 2010)>和<規劃大型頁面庫 (SharePoint server 2010)>。For more information, see Plan Web pages (SharePoint Server 2010), and Plan for large Pages libraries (SharePoint Server 2010).

規劃清單內容Plan list content

當您規劃使用清單維護目錄內容時,請考慮下列問題:When you plan to use lists to maintain catalog content, consider the following questions:

  • 您想要使用多少清單?How many lists do you want to use?

    根據資料的結構,考慮使用多個清單來建立及維護目錄內容。如果用來表示目錄項目的屬性在不同的資料類別之間大不相同,則應該考慮使用多個清單。例如,表示洗衣機的屬性與表示 MP3 播放器的屬性大不相同。在此情況下,請考慮為洗衣機建立一個清單,並為 MP3 播放器建立另一個清單。Depending on the structure of the data, consider using several lists for creating and maintaining catalog content. You should consider using several lists when the attributes that are used to represent catalog items vary greatly between the different categories of data. For example, attributes representing washing machines are very different from the attributes representing MP3 players. In this case, consider creating one list for washing machines, and another list for MP3 players.

  • 您必須具有哪些網站欄以表示目錄項目?Which site columns do you have to have to represent the catalog items?

    當您在 SharePoint 清單中建立及維護目錄內容時,清單中的一個項目會表示一個目錄項目 (例如單一產品或特定事件)。不同的項目會有代表項目屬性 (Property) 的屬性 (Attribute),例如產品的品牌、色彩及大小,或事件的日期、時間及地點。若要新增清單中的這些屬性,您必須建立代表不同屬性的網站欄,例如品牌、色彩、重量、日期、時間及地點。When you create and maintain catalog content in SharePoint lists, an item in the list represents a single catalog item — for example, a single product or a specific event. The different items have attributes to represent properties of the items, such as brand, color, and size for products, or date, time, and place for events. To add these attributes in the list, you have to create site columns that represent the different attributes, such as Brand, Color, Weight, Date, Time, and Place.

    當您規劃要代表目錄內容的網站欄時,請考慮要顯示的內容,以及不同的目錄項目在發佈網站上的顯示方式。您不需要在發佈網站上顯示清單中的所有網站欄。但是,您可以使用所有網站欄中的資訊來排序目錄項目必須顯示的方式。例如,您可以使用「庫存量」網站欄中的資料來排序目錄項目,以在顯目的位置顯示庫存量最大的項目。When you plan the site columns that you want to represent the catalog content, consider both what you want to show, and how the different catalog items appear on the publishing site. You don't have to show all site columns from the list on a publishing site. However, you can use the information from all site columns to sort how catalog items must appear. For example, you can use the data in a site column named Amount in stock to sort catalog items so that the items with the greatest amount in stock appear in a prominent place.

    重要

    建議您建立網站欄,而不是清單欄。系統會為網站欄、分類欄及索引清單欄自動建立 Managed 屬性。此外,請注意所有自動建立的 Managed 屬性皆屬於文字資料類型。如需詳細資訊,請參閱<在 SharePoint Server 中自動建立 managed 的屬性>。We recommend that you create site columns and not list columns. Managed properties are automatically created for site columns, taxonomy columns, and indexed list columns. Also be aware that all automatically created managed properties are of the text data type. For more information, see Automatically created managed properties in SharePoint Server.

  • 清單需要哪些內容類型?What content types do you want for lists?

    如果您具有多個清單,建議您為每個清單建立一種內容類型,然後將此內容類型與適當的網站欄建立關聯。If you have several lists, we recommend that you create a content type for each list, and then associate the appropriate site columns to this content type.

  • 您要作為目錄共用的每個清單所需使用的字詞組為何?What term set do you want to use for each list that you will share as a catalog?

    如本文稍早的<規劃 SharePoint 製作網站上用於標示內容的字詞組>中所述,您可以使用字詞組將目錄內容分類至不同的階層。若要對清單內容使用標示字詞組,您必須具有「受管理的中繼資料」資料類型的網站欄,並連線至標示字詞組。As described in Plan term sets for tagging content on SharePoint authoring sites earlier in this article, you use term sets to categorize the catalog content into a hierarchy. To use tagging term sets for list content, you must have a site column that is a Managed Metadata data type, and is connected to the tagging term set.

  • 您要輸入清單中的資料是否一致?Is the data that you will input into a list consistent?

    您也應該規劃策略,以確定目錄清單資料是否一致。目錄清單資料在不同時間通常會由不同的使用者來維護,這會增加資料不一致的情況。例如,假設您有一個網站欄「色彩」,並想從外部系統匯入個別項目的色彩資訊。外部系統中的值會隨色彩的撰寫方式而有所不同 (BLUE、Blue、blue)。請確保資料一致,再將資料匯入 SharePoint 清單。在此範例中,您會確定所有色彩名稱皆以 Blue 來表示。You should also plan a strategy to make sure that catalog list data is consistent. Catalog list data is often maintained by different people over a long time, and this can increase the inconsistency of the data. For example, let's say that you have a site column named Color, and you want to import the color information for individual items from an external system. The values in the external system vary in how the color is written (BLUE, Blue, blue). Before you import this data into a SharePoint list, make sure that the data is consistent. For this example, you make sure that all color names are represented as Blue.

    除了保證資料一致性之外,您還應該確定用於標示目錄內容之受管理的中繼資料欄位是必要欄位。遺失此欄位的資料會導致在發佈網站上顯示的內容不正確。In addition to guaranteeing data consistency, you should also make sure that the managed metadata field that is used to tag catalog content is a required field. Missing data from this field may cause content to appear incorrectly on the publishing site.

如需如何建立跨網站發佈之清單內容的資訊,請參閱<在 SharePoint Server 中設定跨網站發佈>中的<使用 SharePoint 清單建立目錄內容>。For information about how to create list content for cross-site publishing, see "Create catalog content by using SharePoint lists" in Configure cross-site publishing in SharePoint Server.

規劃使用產品型錄網站集合Plan to use the Product Catalog site collection

「產品型錄網站集合」範本可用來建立網站,以撰寫、儲存及維護用於目錄案例的任何資料類型。此網站集合範本包含最適合維護清單中之目錄內容的產品型錄清單範本。根據預設,當您建立產品型錄網站集合時,會自動建立以產品型錄清單範本為基礎的產品清單。產品清單會預先設定為使用圖像內容類型的產品。使用圖像內容類型的產品具有相關聯的網站欄,如下表所述。The Product Catalog Site Collection template is intended to be used to create sites in which to author, store and maintain any type of data that is used in a catalog scenario. The site collection template includes a Product Catalog list template that is optimized for maintaining catalog content in a list. By default, when you create a Product Catalog site collection, a Products list based on the Product Catalog list template is automatically created. The Products list is preconfigured with the Product with Image content type. The Product with Image content type has site columns associated with it, as described in the following table.

使用圖像內容類型之產品中的網站欄Site columns in the Product with Image content type

網站欄名稱Site column name 網站欄類型Site column type
職稱Title
單行文字Single line of text
項目號碼Item Number
單行文字Single line of text
群組編號Group Number
單行文字Single line of text
語言標記Language Tag
選擇Choice
彙總圖像Rollup Image
發佈圖像Publishing Image
項目類別Item Category
受管理的中繼資料Managed Metadata

此外會建立名為「產品階層」的字詞組。此字詞組與「項目類別」網站欄相關聯。In addition, a term set named Product Hierarchy is created. This term set is associated with the Item Category site column.

如需效能考量,請參閱<設計大型清單並使清單獲得最大效能 (SharePoint Server 2010)>。For performance considerations, see Designing large lists and maximizing list performance (SharePoint Server 2010).

規劃資產庫內容Plan asset library content

當您規劃在內容中使用資產時,請記住需要及不需要編製索引的項目。搜尋系統會編製某些欄位 (例如文字和 HTML 欄位) 的索引,但是不會編製資產 (例如圖片、音訊及視訊檔案) 及檔案 (例如 Word 文件或 PDF) 的索引。這些檔案會視為二進位大型物件 (BLOB),並儲存在 BLOB 快取 (而不是搜尋索引) 中。這表示這些檔案在發佈網站上的顯示方式與其他內容不同。當您規劃製作網站的資產庫內容時,請考量下列清單中的問題。When you plan to use assets in content, remember what is and is not indexed. The search system indexes some fields, such as text and HTML fields, but does not index assets such as pictures, audio and video files, and files such as Word documents or PDFs. These files are considered binary large objects (BLOBs), and are stored in the BLOB cache, not in the search index. This means that they will not be shown on the publishing site in the same manner as other content. As you plan the asset library content for authoring sites, consider the questions in the following list.

  • 資產庫的位置為何?Where should the asset library be located?

    若要在內容中使用資產,製作網站集合和發佈網站集合必須具有資產庫的存取權。資產庫的位置會視您要建立的網站類型,以及解決方案架構而定。如果發佈網站的使用者可以具有製作網站集合的「讀取」權限等級,則可以將資產庫儲存在製作網站集合。但是,如果發佈網站上的使用者不可以具有製作網站集合的「讀取」權限等級,則必須在使用其他權限等級的不同網站集合上建立資產庫。例如,在發佈網站上的使用者只能具有匿名存取權的網際網路案例中,應該將資產庫儲存在不同網站集合中設定為允許匿名存取權的個別 Web 應用程式。但是,在發佈網站上的使用者可以具有讀取權限的內部網路案例中,可以將資產庫儲存在製作網站集合中。當製作網站和發佈網站的資產庫儲存在不同的網站集合時,請務必將資產庫新增至製作網站的 [建議的內容瀏覽器位置] 清單,讓內容作者可以從資產庫尋找項目,並將項目插入其內容中。如果您規劃搭配資產庫使用圖像轉譯,則必須在裝載圖像的網站集合上啟用及設定轉譯。To use assets in content, authoring site collections and publishing site collections must have access to the asset library. The location of the asset library depends on the kind of site that you want to create, and the solution architecture. If the users of the publishing site can have Read permission level on the authoring site collection, the asset library can be stored on the authoring site collection. However, if users on the publishing site cannot have Read permission level on the authoring site collection, the asset library must be created on a separate site collection with different permission levels. For example, in an Internet scenario in which users on the publishing site have only anonymous access, the asset library should be stored on a separate site collection, in a separate web application that is configured to allow anonymous access. However, in an intranet scenario in which users on the publishing site can have read access, the asset library can be stored in the authoring site collection. When the asset library is stored in a site collection separate from both the authoring and publishing sites, make sure that you add it to the list of Suggested Browser Content Locations for the authoring site so content authors can find and insert items from the asset library into their content. If you plan to use image renditions with the asset library, renditions must be enabled and configured on the site collection that hosts the images.

  • 資產庫是否必須作為目錄共用?Does the asset library have to be shared as a catalog?

    如果要儲存在資產庫中的資產使用標示字詞組中的字詞標示,且您希望能夠根據這些字詞查詢資產,您可以將資產庫作為目錄共用。例如,如果您有多個發佈網站想根據特定類別顯示圖片或視訊,則必須將包含這些資產的資產庫作為目錄共用。如果您想允許發佈網站上的匿名使用者,請確定匿名使用者可以存取資產庫。If the assets to be stored in the asset library are tagged with terms from a tagging term set, and you want to be able to query assets based on those terms, you can share the asset library as a catalog. For example, if you have one or more publishing sites that you want to show pictures or videos based on certain categories, the libraries that contain those assets must be shared as catalogs. If you want to allow anonymous users on the publishing site, make sure the asset library is accessible to anonymous users.

  • 快取資產的位置為何?Where will assets be cached?

    當您規劃在內容中使用資產時,也請規劃快取資產檔案的位置。一般而言,請務必啟用發佈網站的 BLOB 快取。BLOB 快取會從資料庫擷取 BLOB 檔案,再儲存在前端網頁伺服器目錄中,供使用者使用,以提升網站效能。如此會降低網路流量及資料庫伺服器負載。如需詳細資訊,請參閱<在 SharePoint Server 中規劃快取及效能>。When you plan to use assets in content, also plan for where the asset files will be cached. In general, always enable the BLOB cache for publishing sites. The BLOB cache improves web site performance by retrieving BLOB files from the database and storing them in a directory on the front-end web server where they are served to users. This reduces the network traffic to and load on the database server. For more information, see Plan for caching and performance in SharePoint Server.

  • 資產檔案的大小為何?How big are the asset files?

    如果您想在內容中使用非常大的檔案 (例如視訊),您應該規劃資產庫所在之伺服器上的上傳檔案大小上限。如此可讓您上傳比 SharePoint Server 所允許的預設設定更大的檔案。如需 BLOB 快取、位元速度節流設定及上傳檔案大小上限的詳細資訊,請參閱<在 SharePoint Server 中規劃快取及效能>。If you plan to use very large files such as videos in content, you should plan to increase the maximum upload file size on the server where the asset library is located. This will allow you to upload files that are larger than the default setting permitted by SharePoint Server. For more information about the BLOB cache, bit-rate throttling, and maximum upload file size, see Plan for caching and performance in SharePoint Server.

如需如何規劃資產庫的詳細資訊,請參閱<在 SharePoint Server 2013 中規劃數位資產庫>。For more information about how to plan for asset libraries, see Plan digital asset libraries in SharePoint Server 2013.

另請參閱See also

概念Concepts

在 SharePoint Server 中發佈至網際網路、內部網路及外部網路網站的功能概觀Overview of publishing to Internet, intranet, and extranet sites in SharePoint Server

規劃 SharePoint Server 的網際網路、內部網路及外部網路發佈網站Plan for Internet, intranet, and extranet publishing sites in SharePoint Server

規劃 SharePoint Server 的跨網站發佈Plan for cross-site publishing in SharePoint Server

SharePoint Server 的跨網站發佈概觀Overview of cross-site publishing in SharePoint Server

規劃 SharePoint Server 跨網站發佈的邏輯架構Plan the logical architecture for cross-site publishing in SharePoint Server

規劃 SharePoint Server 中供網站間發佈用的製作網站Plan publishing sites for cross-site publishing in SharePoint Server

在 SharePoint Server 2016 中規劃跨網站發佈網站的搜尋功能Plan search for cross-site publishing sites in SharePoint Server 2016

在 SharePoint Server 中設定跨網站發佈Configure cross-site publishing in SharePoint Server

評估 Web Content Management 的容量和效能 (SharePoint Server 2013)Estimate capacity and performance for Web Content Management (SharePoint Server 2013)