As per TechNet, the standard cross-site publishing architecture in SharePoint 2013: Content is created in libraries and lists that are shared as catalogs in the authoring site collection(s). The search system crawls the content and builds the search index. A user views a page on a publishing site, which triggers queries from Search Web Parts and results are returned from the search index, and shown in Search Web Parts on the page.

One Authoring Site Collection, Many Publishing Site Collections (1:1,1:n)

Examples of single source search solution architectures include:

  • Data silos to be syndicated to many different sites: For example press releases may be syndicated anonymously to the public web site, intranet site, and appropriate client extranet portal. They will be authored by select few with permissions in the Press Releases site.
  • Syndicating knowledge from existing legacy / custom / enterprise applications: For example a Document Management System, Exchange, ERP or CRM tools.

Many Authoring Site Collections, One Publishing Site Collection (n:1, n:n)

Examples of multiple source search solution architectures:

  • Governance requirements dictate security trimming is critical: Rolling up reports & data from many SharePoint sites containing sensitive data.
  • Syndicating knowledge within legacy SharePoint portals to Next-Gen User Experiences: Your organization invested in SharePoint with the 2007 or 2010 release, your collaboration portals are being used, but you need a better user experience.
  • User-centered portals aggregating complex collaboration site architectures in a structured manner. Delve follows this pattern by aggregating data from all Office 365 properties that it believes are relevant to the user to build a personal UX.

Multilingual, Asset Sites and Extranets

A more practical architecture using search to syndicate intranet knowledge through a firewall to extranet / public websites.

  • Use of SharePoint Publishing Variations & Workflows to author multi lingual content into list items. Building on OOTB Strengths.
  • Syndication of content into portals for .com, .fr sites: By separating into separate site collections we have opportunity to better support each languages branding needs (EX// RTL, LTR).
  • Use of shared assets site to host all public / extranet content: We host all asset content (images, documents, etc.) on a public site collection called assets which is also available to content authors for contributions.
  • Sites exposed by domain on port 80/443 through firewall.
  • Limitation: Search does not index web parts so of limited use to authoring process.

Recent Insights

Microsoft 365 Capacity: SharePoint Online & One Drive Boundaries & Limits

We’ve got two official languages in Canada: French & English. SharePoint Online Multilingual Support plays an important role in presenting the right language to the right user. In this blog post we outline the features, and some of the challenges we’ve faced in building Modern Multilingual SharePoint Online sites.

read more

Matthew Stark

Matthew Stark is the founder of Making Things Work, has over 16 years experience in the enterprise Information Technology space, is an avid sailor, hockey fan, and a proud father of one.