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

摘要:了解如何規劃 SharePoint Server 跨網站發佈解決方案的發佈網站集合。Summary: Learn how to plan publishing 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 publishing sites for your cross-site publishing solution.

本文是以<SharePoint Server 的跨網站發佈概觀>中的資訊為基礎。閱讀完本文之後,請務必閱讀下一篇文章<在 SharePoint Server 2016 中規劃跨網站發佈網站的搜尋功能>。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 search for cross-site publishing sites in SharePoint Server 2016.

規劃 SharePoint 發佈網站的網站集合和網站結構Plan site collections and site structure for SharePoint publishing sites

發佈網站集合必須啟用 SharePoint Server 的發佈功能。建議您使用「發佈入口網站集合」範本建立發佈網站集合,因為使用該網站集合範本時,預設會啟用發佈功能。如果使用不適用發佈網站集合的網站集合範本,則必須啟用 SharePoint Server 的發佈功能。如需詳細資訊,請參閱<發佈功能概觀 (SharePoint Server 2010)>。如需如何啟用發佈功能的資訊,請參閱<啟用發佈功能>。Publishing site collections must have the SharePoint Server publishing features activated. We recommend that you use the Publishing Portal Site Collection template to create publishing site collections because the publishing features are activated by default when you use that site collection template. If you use a site collection template that is not for a publishing site collection, you must enable the SharePoint Server publishing features. For more information, see Publishing features overview (SharePoint Server 2010). For information about how to activate the publishing features, see Enable publishing features.

因為發佈網站集合重複使用製作網站的內容和字詞組來顯示內容,所以發佈網站比製作網站更輕型。因此,發佈網站的網站結構通常與製作網站大不相同。發佈網站包含主版頁面、數目有限的版面配置、受管理導覽,以及含有目錄和用來顯示目錄內容之目錄項目頁面的單一頁面庫。系統會根據製作網站上所使用之標示字詞組中的字詞來建立網站的 URL。因此,您不需要手動建立發佈網站的複雜網站結構。Because the publishing site collection reuses content and term sets from the authoring site to show content, publishing sites are much more lightweight than authoring sites. Therefore, the site structure for a publishing site is usually very different from the authoring site. The publishing site contains a master page, a limited number of page layouts, managed navigation, and a single Pages library that contains the catalog and catalog item pages used to show catalog content. The URLs for the site are created based on the terms in the tagging term set used on the authoring site. Therefore, you do not have to manually create a complex site structure for a publishing site.

規劃 SharePoint 發佈網站的安全性Plan security for SharePoint publishing sites

雖然規劃發佈網站的安全性與規劃其他任何 SharePoint Server 網站的安全性一樣,但仍另請考慮下列事項:Although you plan security for publishing sites in the same way that you do for any other SharePoint Server site, also consider the following:

  • 誰是設計者,以及應授與設計者的權限等級為何?因為發佈網站是儲存主版頁面、版面配置及 CSS 檔案的位置,所以設計者必須具有網站的讀取和寫入權限。Who are the designers, and what permission levels should they be granted? Because the publishing site is where master pages, page layouts, and CSS files are stored, designers must have read and write permissions to the site.

  • 是否為允許匿名存取的網際網路網站?發佈網站集合應位於哪個 Web 應用程式,以允許訪客的匿名存取?您必須決定誰應該具有發佈網站所顯示內容的「讀取」權限等級。Is this an Internet site that allows for anonymous access? What web application should the publishing site collection be in to allow anonymous access for visitors? You must decide who should have Read permission levels for content shown on the publishing site.

  • 如果這是網際網路網站,是否必須為設計者設定宣告式驗證?If this is an Internet site, do you have to set up claims-based authentication for designers?

  • 如果這是內部網路或外部網路網站,您必須使用的驗證方法為何?如需使用者驗證的詳細資訊,請參閱<在 SharePoint Server 中規劃使用者驗證方法>。If this is an intranet or extranet site, what authentication method do you have to use? For more information about user authentication, see Plan for user authentication methods 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 發佈網站的設計和品牌Plan design and branding for SharePoint publishing sites

在跨網站發佈解決方案中,發佈網站包含設計者所建立並可用於設定網站品牌的檔案及其他資源。下列清單說明設計者必須建立的主要品牌元件。In a cross-site publishing solution, the publishing sites contain the files and other resources that a designer creates and that are used to brand the site. The following list describes the major branding components that a designer must create.

  • 主版頁面 定義網站的組件區塊和共用元素。Master pages Define the chrome and shared elements of a site.

  • 版面配置 網站中特定頁面類型的範本。Page layouts Templates for specific types of pages in a site.

  • 顯示範本 「內容搜尋網頁組件」內所使用的範本,可控制要在搜尋結果中顯示的 Managed 屬性及顯示方式。Display templates Templates used within Content Search Web Parts that control which managed properties are shown in the search results, and how they appear.

一般而言,規劃發佈網站的設計與規劃任何品牌網站的設計完全相同。您應該與設計者合作,收集設計需求、決定所需支援的瀏覽器和裝置,然後建立網站的架構。若要規劃發佈網站的特定 SharePoint Server 部分,請考慮下列事項:In general, you plan the design of the publishing sites exactly as you do for any branded site. You should work with a designer to collect design requirements, decide the browsers and devices that you want to support, and then create a wireframe for the sites. To plan for specific SharePoint Server aspects of the publishing sites, consider the following:

  • 您想擁有多少發佈網站?How many publishing sites will you have?

  • 這些發佈網站想使用多少視覺化設計?How many visual designs will you have for the publishing sites?

  • 需要多少主版頁面?How many master pages are needed?

  • 每個發佈網站所要顯示的目錄內容為何,且其外觀為何?What catalog content will be shown on each publishing site, and how should it look?

  • 您支援的裝置為何,是否需要有不同的裝置通道和主版頁面?What devices will you support, and will you have to have separate device channels and master pages?

如需詳細資訊,請參閱<SharePoint 頁面模型概觀>。For more information, see SharePoint page model overview.

規劃 SharePoint 發佈網站的目錄連線Plan catalog connections for SharePoint publishing sites

當您將發佈網站連線至目錄時,SharePoint Server 會自動建立目錄的結果來源。您也可以執行下列操作:When you connect a publishing site to a catalog, SharePoint Server automatically creates a result source for the catalog. You can also do the following:

  • 將目錄中的標示字詞組整合到發佈網站上的導覽字詞組。Integrate the tagging term set from the catalog into the navigation term set on the publishing site.

  • 建立類別版面配置及目錄內容的目錄項目版面配置。Create a category page layout and catalog item page layout for the catalog content.

  • 設定連至目錄項目頁面的目錄項目易記 URL。Set up a catalog item friendly URL to the catalog item page.

如果您在連線至目錄時,選擇不要將目錄整合到發佈網站,則必須手動執行上述每個工作。If you choose to not integrate the catalog into your publishing site when you connect to a catalog, you must do each of those tasks manually.

如需發佈網站如何連線至目錄的詳細資訊,請參閱<將發佈網站連線到 SharePoint Server 中目錄>。For information about how to connect a publishing site to a catalog, see Connect a publishing site to a catalog in SharePoint Server.

規劃 SharePoint 發佈網站的導覽字詞組Plan navigation term sets for SharePoint publishing sites

當您將發佈網站連線至目錄時,您可以選擇將製作網站中的標示字詞固定到發佈網站的導覽。當您在字詞庫管理工具中檢視「網站導覽」字詞組時,即可設定每個字詞的導覽設定。當您規劃發佈網站的導覽字詞組時,請考慮下列事項:When you connect a publishing site to a catalog, you have the option to pin the tagging terms from the authoring site to navigation of the publishing site. When you view the Site Navigation term set in the Term Store Management Tool, you'll be able to configure the navigation settings for each term. When you plan the navigation term sets for a publishing site, consider the following:

  • 導覽字詞標題是否與原始標示字詞標題相同?如果標題不同,則新標題為何?Will the navigation term titles be the same as the original tagging term titles? If the titles will be different, what should the new titles be?

  • 導覽字詞是否應該顯示在全域功能表及目前導覽功能表中?Should the navigation term appear in the Global and Current Navigation Menus?

  • 導覽字詞應該使用指向字詞導向頁面或其他 URL 的易記 URL,或只是純文字標題?Should the navigation term use a friendly URL that points to a term-driven page, point to a different URL, or just be a text-only heading?

當您設定導覽字詞組時,您可以變更其他設定,例如目標頁面設定、搜尋引擎最佳化及目錄項目頁面設定。如果使用不會建立發佈網站的網站集合範本 (例如「小組網站」範本),然後啟用發佈功能,也必須確定開啟網站集合的受管理導覽。When you configure the navigation term set, you'll be able to change other settings such as target page settings, search engine optimization, and catalog item page settings. If you use a site collection template, such as the Team Site template, that does not create a publishing site collection, and then activate the publishing feature, you must also be sure to turn on managed navigation for the site collection.

規劃顯示 SharePoint 發佈網站中的目錄內容Plan to show catalog content in SharePoint publishing sites

本節說明如何規劃顯示發佈網站中的目錄內容。當您規劃類別頁面和目錄項目頁面時,目錄資料的結構很重要。您想如何在不同的層級中顯示目錄內容,會決定類別頁面和目錄項目頁面上所使用的網頁組件。This section describes how to plan to show catalog content in publishing sites. The structure of the catalog data will be important when you plan the category pages and catalog item pages. How you want to show the content in the different levels within the catalog will determine which Web Parts you use on the category pages and catalog item pages.

規劃類別頁面和目錄項目頁面Plan category pages and catalog item pages

當您設定使用目錄內容的網站時,SharePoint Server 會在您連線至目錄時,自動為您建立類別頁面和目錄項目頁面。本節說明選擇自訂預設頁面或自行建立這些頁面時,所應規劃的事項。如需類別頁面和目錄項目頁面的詳細資訊,請參閱<SharePoint Server 的跨網站發佈概觀>之<SharePoint 跨網站發佈的發佈網站集合>一節中的<類別頁面和目錄項目頁面>。When you set up a site that uses catalog content, SharePoint Server can automatically create a category page and a catalog item page for you when you connect to a catalog. This section describes what you should plan for if you choose to customize the default pages, or create these pages yourself. For more information about category pages and catalog item pages, see "Category pages and catalog item pages" in the "Publishing site collections for SharePoint cross-site publishing" section in Overview of cross-site publishing in SharePoint Server.

規劃類別頁面Plan category pages

當您規劃自訂預設類別頁面或建立自己的頁面時,請考慮內容的結構,並決定要在此結構內不同位置顯示的內容。請考慮下列項目:As you plan to customize default category pages, or create your own, consider the structure of the content, and determine what content you want to show at different points within this structure. Consider the following:

  • 用於目錄導覽的字詞組中有多少層級 (類別)?How many levels (categories) do you have in the term set that is used for catalog navigation?

    如果您想清楚區別目錄中的層級 (類別),可以分別為字詞組中的各個層級建立一個類別頁面。If you want to make a clear differentiation between the levels (categories) within the catalog, you could create one category page per level within the term set.

  • 要自訂預設類別頁面,或建立自己的頁面?Will you customize the default category pages, or create your own?

    如果選擇建立自己的類別頁面,在您連線至目錄並指定要顯示內容的自訂類別頁面之後,您必須在編輯模式下開啟頁面,並設定新增至頁面之任何「內容搜尋網頁組件」的查詢。If you choose to create your own category pages, after you connect to a catalog and specify the custom category page to show content, you must open the page in edit mode and configure the queries for any Content Search Web Parts that you added to the page.

  • 必須向使用者顯示哪些重要內容,以便其瀏覽目錄?What content is important to show for users to easily browse within the catalog?

    當您考慮要顯示的內容時,也應該考慮要包含在類別頁面上的網頁組件。例如,如果使用「精簡搜尋面板網頁組件」和多面向導覽,使用者可以透過篩選目錄中的屬性,輕鬆瀏覽內容。您也可以新增「常用項目網頁組件」,以顯示認定與使用者相關的項目。您也應該考慮是否只想使用「搜尋網頁組件」,還是想包含其他內容網頁組件。如需詳細資訊,請參閱本文稍後的<規劃新增搜尋網頁組件至頁面>。When you think about what content to show, you should also think about which Web Parts you want to include on category pages. For example, if you use a Refinement Panel Web Part and faceted navigation, users can easily browse to content by filtering on properties from the catalog. You can also add a Popular Items Web Part to show items that are perceived to be relevant for the user. You should also consider if you want to use only Search Web Parts, or if you want to include other content Web Parts. For more information, see Plan to add Search Web Parts to pages later in this article.

  • 是否所有類別頁面都可以使用相同設計?Can you use the same design across all category pages?

    如果所有類別頁面不可以使用相同設計,則必須建立使用不同設計的不同頁面。在您連線至目錄並指定要用來顯示內容的類別頁面之後,您必須在編輯模式下開啟頁面,並設定頁面上任何「內容搜尋網頁組件」的查詢。If you can't use the same design across all category pages, you'll have to create separate pages that have separate design. After you connect to a catalog and specify the category page to use to show content, you must open the page in edit mode and configure the queries for any Content Search Web Parts on the page.

  • 您認為維護這些頁面的合理工作量為何?How much work do you think is acceptable when maintaining these pages?

    您擁有的類別頁面愈多,所需執行的維護工作愈多。請限制類別頁面的數目,以減少您必須變更管理的位置數目。The more category pages that you have, the more maintenance work that you'll have to do. Limit the number of category pages so that you reduce the number of places where you have to do change management.

如需如何建立並自訂類別頁面配置的資訊,請參閱<如何為 SharePoint 2013 的目錄式網站自訂頁面配置>。For information about how to create and customize a category page layout, see How to: Customize page layouts for a catalog-based site in SharePoint 2013

規劃目錄項目頁面Plan catalog item pages

當您規劃自訂預設目錄項目頁面或建立自己的頁面時,請考慮下列事項:As you plan to customize default catalog item pages, or create your own, consider the following:

  • 是否以群組的方式顯示項目?Do you want to display items in a group?

    自動建立的目錄項目頁面會在顯示內容時,使用目錄項目重複使用網頁組件。根據預設,目錄項目重複使用網頁組件設定為採用伺服器端轉譯,因此 Google 和 Bing 等搜尋引擎可以找到並記錄目錄中的個別項目。此外,尚未啟用 JavaScript 的使用者 (例如因為協助工具原因而未啟用者) 也可以檢視內容。目錄項目重複使用網頁組件設定為自動記錄流量分析所使用的流量事件。The automatically created catalog item page uses Catalog Item Reuse Web Parts when displaying content. By default, the Catalog Item Reuse Web Part is configured to use server-side rendering, and therefore, search engines such as Google and Bing can discover and log individual items in the catalog. Also, users who haven't enabled JavaScript, for example for accessibility reasons, will be able to view the content. The Catalog Item Reuse Web Part is configured to automatically record the default usage events used by Usage analytics.

    規劃目錄項目頁面要顯示的項目時,請考慮是否以群組的方式顯示項目。以衣服販售網站的網際網路商業案例為例,您可能想在目錄項目頁面上,以群組的方式顯示特定項目的所有尺寸。瀏覽至該目錄項目頁面的使用者即可快速檢視該項目的所有尺寸。 在這種群組案例中,您不能使用自動建立的目錄項目頁面,因為自動建立的目錄項目頁面會採用目錄項目重複使用網頁組件。目錄項目重複使用網頁組件一次只能擷取一個項目,無法一次擷取群組的所有項目。因此,如果您想在目錄項目頁面上,以群組的方式顯示項目,您必須自行建立目錄項目頁面,並且使用「內容搜尋網頁組件」來顯示項目。When you plan to display items on a catalog item page, consider if you want to display an item in a group or not. For example, in an Internet Business scenario where you have a website selling clothes, you may want to group all available sizes of a particular item on the catalog item page. Users who browse to the catalog item page, can then quickly view all available sizes for that item. For this group scenario, you can't use the automatically created catalog item page because it uses Catalog Item Reuse Web Parts. Catalog Item Reuse Web Parts can only retrieve one item at a time, and not a group of items. Therefore, if you want to display items in a group on your catalog item page, you have to create your own catalog item page, and use a Content Search Web Part to display the items.

    注意

    [!附註] 雖然根據預設,「內容搜尋網頁組件」採用用戶端轉譯和 JavaScript 來顯示項目,但會自動使用 XSLT 式伺服器端轉譯,將內容轉譯至 Google 和 Bing 等搜尋引擎。不過,尚未啟用 JavaScript 的使用者 (例如因為協助工具原因而未啟用者),則無法檢視內容。若要確保無論 JavaScript 是否啟用,皆能獨立檢視內容,請考慮將「內容搜尋網頁組件」變更為永遠使用XSLT 式伺服器端轉譯。 > 此外也請注意,「內容搜尋網頁組件」不會自動記錄流量分析的流量事件,不過您可以設定以顯示範本紀錄流量事件。如需詳細資訊,請參閱<在 SharePoint Server 中設定建議和流量事件類型>。Even though the Content Search Web Part by default uses client-side rendering and JavaScript to display search results, it will automatically implement XSLT-based server-side rendering to render content to search engines such as Google and Bing. However, users who haven't enabled JavaScript, for example for accessibility reasons, won't be able to view the content. To make sure that your content can be viewed independently of whether JavaScript is enabled, consider changing the Content Search Web Part to always use XSLT-based server-side rendering. > Also be aware that usage events for Usage analytics are not automatically recorded in the Content Search Web Part, but you can configure the display template to record usage events. For more information, see Configure recommendations and usage event types in SharePoint Server.

    如需目錄項目重複使用網頁組件與「內容搜尋網頁組件」之間差異的詳細資訊,請參閱<搜尋網頁組件及何時使用其他網頁組件>。For more information about the differences between the Catalog Item Reuse Web Part and the Content Search Web Part, see Search Web Parts and when to use the different Web Parts.

  • 是否所有目錄項目頁面都可以使用相同設計?Can you use the same design across all catalog item pages?

    如果所有目錄項目頁面不可以使用相同設計,則必須建立使用不同設計的不同頁面。在您連線至目錄並指定要用來顯示內容的目錄項目頁面之後,您必須在編輯模式下開啟頁面,並設定頁面上任何「內容搜尋網頁組件」的查詢。If you can't use the same design across all catalog item pages, you'll have to create separate pages that have separate designs. After you connect to a catalog and specify the catalog item page to use to show content, you must open the page in edit mode and configure the queries for any Content Search Web Parts on the page.

  • 您認為維護這些頁面的合理工作量為何?How much work do you think is acceptable when maintaining these pages?

    您擁有的目錄項目頁面愈多,所需執行的維護工作愈多。請限制目錄項目頁面的數目,以減少您必須執行變更管理的位置數目。The more catalog item pages that you have, the more maintenance work you'll have to do. Limit the number of catalog item pages to reduce the number of places where you have to do change management.

如需如何建立並自訂目錄項目頁面的資訊,請參閱<如何為 SharePoint 2013 中的目錄式網站自訂頁面配置For information about how to create and customize a catalog item page layout, see How to: Customize page layouts for a catalog-based site in SharePoint 2013

規劃新增搜尋網頁組件至頁面Plan to add Search Web Parts to pages

「搜尋網頁組件」顯示搜尋索引中的內容。「搜尋網頁組件」包含不同的預先定義查詢,例如搜尋的內容類型及搜尋內容的位置。當使用者瀏覽含有「搜尋網頁組件」的頁面時,網頁組件會自動發出定義在網頁組件中的查詢,並在網頁組件中顯示搜尋結果。如果搜尋系統發現新內容,則會在每次檢視頁面時於網頁組件中顯示項目的更新清單。The Search Web Parts show content from the search index. The Search Web Parts have different predefined queries, such as what type of content to search for, and where to search for the content. When users browse to a page that contains a Search Web Part, the Web Part automatically issues the query defined in the Web Part, and the search results appear in the Web Part. As search system discovers new content, an updated list of items appears in the Web Part every time that the page is viewed.

您可以將一或多個「搜尋網頁組件」新增至頁面。當您新增「搜尋網頁組件」時,您可以使用預先定義的查詢,或變更預設查詢設定。您也可以變更結果在網頁組件中的顯示方式,例如指定依價格或常用性排序項目。您可以透過編輯網頁組件並變更其搜尋準則,來變更預先定義的查詢。You can add one or more Search Web Parts to the pages. When you add a Search Web Part, you can use the predefined query, or you can change the default query settings. You can also change how the results appear in the Web Part, for example, by specifying to sort items by price or by popularity. You can change the predefined query by editing the Web Part and changing its search criteria.

「搜尋網頁組件」使用「顯示範本」控制結果在網頁組件中的顯示方式。顯示範本是 HTML 檔案,可指定搜尋結果中所要顯示的 Managed 屬性,也可以指定這些屬性的顯示方式。例如,顯示範本可以指定 Managed 屬性 PublishingImage 顯示 100x100 像素的圖片,並指定在圖像左側以粗體顯示 Managed 屬性 Title。The Search Web Parts use display templates to control how the results appear in the Web Part. Display templates are HTML files that specify which managed properties from the search result to show, and also how these properties should be shown. For example, a display template could specify that the managed property PublishingImage shows a 100x100 pixel picture, and the managed property Title appears in bold to the left of the image.

如需如何建立並自訂顯示範本的資訊,請參閱<SharePoint 2013 設計管理員顯示範本For information about how to create and customize display templates, see SharePoint 2013 Design Manager display templates

搜尋網頁組件及何時使用其他網頁組件Search Web Parts and when to use the different Web Parts

以下表格說明網頁內容管理案例中普遍使用的「搜尋網頁組件」。如需生產力搜尋案例中普遍使用之搜尋網頁組件的資訊,請參閱<在 SharePoint Server 中管理搜尋中心>。The following table describes Search Web Parts that are commonly used in web content management scenarios. For information about Search Web Parts commonly used in a productivity search scenario, see Manage the Search Center in SharePoint Server.

搜尋網頁組件Search Web Parts

類別Category 網頁組件Web Part 描述Description
內容彙總Content Rollup
內容查詢Content Query
請勿用於跨網站發佈。使用「內容搜尋網頁組件」,或「搜尋導向內容網頁組件」類別中的其中一個網頁組件。Do not use for cross-site publishing. Use the Content Search Web Part or one of the Web Parts in the Search-Driven Content Web Part category.
內容搜尋Content Search
請使用此網頁組件來顯示目錄頁面上的目錄內容。您也可以使用該組件,以群組的方式顯示目錄項目頁面上的項目。在「內容搜尋網頁組件」 (CSWP) 中,您可以選取結果來源,以便指定搜尋的內容。您也可以使用「關鍵字查詢語言」,為查詢新增更多篩選器和搜尋字詞。 Use this Web Part to display catalog content on a category page. You can also use it to display items in a group on your catalog item page. In the Content Search Web Part (CSWP), you can select a result source to specify which content should be searched. You can also use Keyword Query Language to add more filters and search terms to the query.
根據預設,此網頁組件使用用戶端轉譯,也就是說,您可以使用顯示範本中的 JavaScript 自訂搜尋結果的顯示方式。為了讓 Google 和 Bing 等搜尋引擎可以找到並記錄目錄中的各個項目,CSWP 會在將內容轉譯至搜尋引擎時,自動採用 XSLT 式伺服器端轉譯。 By default, this Web Part uses client-side rendering, which means that you can use JavaScript in the display template to customize how search results should be displayed. To enable search engines such as Google and Bing to discover and log individual items in the catalog, the CSWP will automatically implement XSLT-based server-side rendering when rendering content to search engines.
由於轉譯發生的位置在瀏覽器,因此需要較少的資源,這是另一個使用用戶端轉譯的好處。如需頁面新增 CSWP 時效能考量的資訊,請參閱<評估 Web Content Management 的容量和效能 (SharePoint Server 2013)Another benefit of using client-side rendering is that the server requires fewer resources because the rendering happens in the browser. For information about performance considerations when you add a CSWP to a page, see Estimate capacity and performance for Web Content Management (SharePoint Server 2013)
> [!NOTE]> 因為內容搜尋網頁組件會使用 JavaScript 來顯示的內容,尚未啟用使用者 JavaScript,例如協助工具考量,將不能夠檢視內容。若要確定您的內容可檢視獨立是否已啟用 JavaScript,請考慮變更一律使用 XSLT 型伺服器端轉譯內容搜尋網頁組件。附註指出使用 XSLT 型伺服器端轉譯通常需要更多伺服器資源可能會降低效能。> [!NOTE]> Because the Content Search Web Part uses JavaScript to display content, users who haven't enabled JavaScript, for example for accessibility reasons, won't be able to view the content. To make sure that that your content can be viewed independently of whether JavaScript is enabled, consider changing the Content Search Web Part to always use XSLT-based server-side rendering. Note that using XSLT-based server-side rendering often require more server resources and may reduce performance.
搜尋Search
精簡搜尋面板Refinement Panel
此網頁組件會將精簡器新增至頁面。您可以使用此網頁組件新增獨立精簡器及多面向導覽精簡器。 This Web Part adds refiners to the page. You can use this Web Part to add stand-alone refiners and refiners for faceted navigation.
您必須啟用 Managed 屬性作為精簡器,此網頁組件中才能顯示任何精簡器。如需詳細資訊,請參閱<在 SharePoint Server 中設定精簡器和多面向導覽>。 You must enable managed properties as refiners before any refiners will display in this Web Part. For more information, see Configure refiners and faceted navigation in SharePoint Server.
分類精簡搜尋面板Taxonomy Refinement Panel
此網頁組件合併精簡搜尋與受管理導覽,並可用來為目錄內容增加強大的搜尋導向導覽體驗。此網頁組件只能搭配受管理導覽使用,並且必須與頁面上的其他「搜尋網頁組件」(例如「內容搜尋網頁組件」) 相關聯。此網頁組件可讓您根據目前導覽字詞顯示精簡器,以篩選相關聯網頁組件中的搜尋結果。「分類精簡搜尋面板網頁組件」中顯示的精簡器是目前導覽字詞的子精簡器。當使用者按一下精簡器時,會據以篩選相關聯網頁組件中的搜尋結果。此網頁組件之所以特別強大的原因,在於顯示精簡器時,會將使用者之前的查詢或精簡搜尋列入考量。 This Web Part combines refinement with managed navigation, and can be used to add a powerful search-driven navigation experience to the catalog content. It can only be used in combination with managed navigation, and must be associated with another Search Web Part on the page, such as a Content Search Web Part. It enables you to filter search results in the associated Web Part by displaying refiners based on the current navigation term. The refiners shown in the Taxonomy Refinement Panel Web Part are child refiners of the current navigation term. When a user clicks a refiner, the search results in the associated Web Part are filtered accordingly. What makes this Web Part especially powerful is that it accounts for previous queries or refinements made by the user when displaying the refiners.
> [!IMPORTANT]> 我們不建議您在具有 200 個以上的導覽節點底下它] 頁面上使用分類精簡搜尋面板網頁組件。大量的導覽節點可能會導致緩慢的伺服器回應時間並減少輸送量。如需詳細資訊,請參閱< Estimate capacity and performance for Web Content Management (SharePoint Server 2013)> [!IMPORTANT]> We don't recommend that you use the Taxonomy Refinement Panel Web Part on a page that has more than 200 navigation nodes under it. A large number of navigation nodes may cause slow server response times and decrease throughput. For more information, see Estimate capacity and performance for Web Content Management (SharePoint Server 2013)
搜尋導向內容Search-Driven Content
文章Articles
顯示與「文章頁面」內容類型相關聯的項目。Shows items that are associated with the Article Page content type.
目錄項目重複使用Catalog Item Reuse
只有當不想以群組的方式顯示目錄項目時,才在目錄項目頁面上使用此網頁組件。此網頁組件使用伺服器端轉譯,因此 Bing 或 Google 等搜尋引擎才可以找到並記錄目錄中的各個項目。此網頁組件也設定為自動記錄流量分析使用的預設流量事件。 Only use this Web Part on a catalog item page when you don't want to display your catalog items in a group. This Web Part uses server-side rendering so that search engines such as Bing or Google can discover and log individual items in the catalog. It's also configured to automatically record the default usage events used by Usage Analytics.
此網頁組件的設定稍微不同於其他搜尋網頁組件。此網頁組件的多數設定都在目錄項目頁面的 HTML 頁面配置檔案中執行,而且只能顯示一個 Managed 屬性。因此,針對每個您想要顯示於目錄項目頁面的 Managed 屬性,您都必須在 HTML 頁面配置檔案中新增一個目錄項目重複使用網頁組件。此外,您必須直接在目錄項目頁面上,新增一個目錄項目重複使用網頁組件,作為網頁組件,並在該網頁組件中,設定應該擷取的目錄項目查詢。HTML 頁面配置檔案中新增的目錄項目重複使用網頁組件應設定為重複使用此查詢所擷取的資料。 The configuration of this Web Part is somewhat different from the other Search Web Parts. Most configuration of this Web Part is performed in the HTML page layout file of the catalog item page. The Web Part can only display one managed property. Therefore, for each managed property that you want to display on your catalog item page, you must add one Catalog Item Reuse Web Part to the HTML page layout file. In addition, you must add one Catalog Item Reuse Web Part as a Web Part directly on the catalog item page. In that Web Part, you configure the query for the catalog item that should be retrieved. The Catalog Item Reuse Web Parts that were added in the HTML page layout file are configured to reuse the data that are retrieved by this query.
目錄項目重複使用網頁組件不會使用顯示範本來顯示內容,反而格式才是以 Managed 屬性為基礎,例如 DateHTMLThe Catalog Item Reuse Web Part doesn't use display templates to show content. Instead, formatting is based on the managed property type, for example Date or HTML.
如需如何自訂使用目錄項目重複使用網頁組件之目錄項目頁面配置的資訊,請參閱<如何為 SharePoint 2013 中的目錄式網站自訂頁面配置For information about how to customize a catalog item page layout that uses Catalog Item Reuse Web Parts, see How to: Customize page layouts for a catalog-based site in SharePoint 2013
如需在頁面新增目錄項目重複使用網頁組件時效能考量的資訊,請參閱<評估 Web Content Management 的容量和效能 (SharePoint Server 2013)For information about performance considerations when you add a Catalog-Item Reuse Web Part to your page, see Estimate capacity and performance for Web Content Management (SharePoint Server 2013)
符合標記的項目Items Matching a Tag
顯示以字詞標示的項目。Shows items that are tagged with a term.
圖片Pictures
顯示與「圖片」或「圖像」內容類型相關聯的所有項目。Shows any items that are associated with the Picture or Image content type.
常用項目Popular Items
使用此網頁組件可顯示符合一組準則的最常用項目。例如,您可以將此網頁組件新增至類別頁面,以顯示「類別中最常用的項目」。Use this Web Part to show the most popular items that satisfy a set of criteria. For example, you can add this Web Part to a Category page to show "Most popular items in category."
最近變更的項目Recently Changed Items
顯示最近變更的項目。此網頁組件可協助使用者追蹤網站或文件庫中的最新活動。Shows items that were recently changed. This can help users track the latest activity on a site or in a library.
建議項目Recommended Items
使用此網頁組件可根據使用者先前與網站的互動方式來顯示內容建議。例如,您可以將此網頁組件新增至目錄項目頁面。如果使用者檢視特定項目,此網頁組件會顯示使用者先前檢視的其他項目,例如「檢視此項目的使用者也檢視這些項目」。Use this Web Part to show content recommendations based on how users have previously interacted with the site. For example, you can add this Web Part to a catalog item page. If a user views a specific item, this Web Part will show other items that users have previously viewed, such as "Users who viewed this item also viewed these items."
預設會將查詢限制為目前網站的建議項目。您可以將此設定變更為根據 URL 中 Token 的建議項目,也可以限制查詢特定 URL 或內容類型。By default, the query is restricted to recommended items for the current site. You can change this setting to recommended items based on a token from the URL, and also restrict the query to a specific URL or content type.
視訊Videos
顯示與「視訊」內容類型相關聯的所有項目,並依檢視次數排序項目。Displays any items that are associated with the Video content type. It will sort items by number of views.
網頁Web Pages
顯示衍生自「頁面」內容類型的所有項目。Displays any items that are derived from the Page content type.
Wiki 頁面Wiki Pages
顯示與「Wiki 頁面」內容類型相關聯的所有項目。Displays any items that are associated with the Wiki Page content type.

如需如何新增並設定搜尋網頁組件的資訊,請參閱<在 SharePoint Server 中設定搜尋網頁組件>。For information about how to add and configure Search Web Parts, see Configure Search Web Parts in SharePoint Server.

另請參閱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 authoring 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)