SharePoint templates provide starting layouts for intranet sites and pages, so teams can begin with a structure suited to a common business purpose instead of designing every element from scratch. They may be useful to site owners, intranet teams and internal communicators planning homepages, department spaces or employee information. Dougie Wood [MVP] presents ten SharePoint design examples, including business, healthcare and employee-onboarding layouts.
The examples are design starting points rather than a claim that SharePoint has introduced a new feature. The publisher's description frames them as ways to organize a SharePoint environment, build internal communication hubs and create team-focused dashboards. It says the designs use native SharePoint intranet features and standard web parts, rather than relying on expensive third-party software.
The examples span several needs: a general SharePoint homepage, a hub, learning and development, human resources, financial services, healthcare and employee onboarding. The description also names a premium healthcare example and a premium homepage, so the examples are not all presented as free. The material does not give prices or specify what is included in any free or premium offering.
It helps to distinguish a site template from a page template. A site template is a starting point for an entire site, while a page template provides a layout for an individual page or news post. The research notes describe both Microsoft-provided templates and templates saved by an organization, but the supplied sources do not verify the current Microsoft gallery or the exact templates available in any tenant.
These layouts are relevant to SharePoint site owners and people responsible for intranet design, employee communications or departmental workspaces. A team setting up onboarding, for example, could use an employee-focused layout as a planning reference; a communications team could consider a homepage or hub structure. The examples can inform site architecture, but the material does not establish that a particular layout is right for every organization.
The description says the designs use native SharePoint features and standard web parts. It does not list prerequisites, required permissions, a SharePoint plan or license, or supported regions. It also does not establish whether a linked template can be imported directly, whether it requires a particular product, or what customization is available. Check the relevant template provider's instructions and your organization's SharePoint policies before using a design.
The supplied material does not identify a preview or rollout stage for a Microsoft feature. It describes design examples and references a site offering templates; it does not confirm broad availability of those external templates or make a claim about the state of Microsoft's template gallery. There is no official Microsoft source URL in the supplied source list to verify licensing or availability.
Use a template as a starting point for decisions about the purpose of a site, its audience and the information it needs to present. The examples point to several common starting categories, but the description does not provide a verified, step-by-step installation procedure or specific menu paths. Treat the categories below as planning choices, not guaranteed import options.
Microsoft's general template guidance in the research notes describes a separate site-template route through Settings > Apply a site template, and a page-template gallery when creating pages or news posts. Those notes say an applied site template can provide structure and sample content, while pages created from a page template can be edited independently of the original. Because the supplied source list has no Microsoft documentation link, verify these instructions in your environment before relying on them.
The main practical limitation is the gap between seeing a design and knowing how to deploy it. The description lists template categories and says the video reviews configurations, but the supplied transcript is empty. It therefore does not provide a reliable written record of individual setup steps, exact web part configurations, or what a user must click to install each design.
Nor does the material establish the terms behind “free,” the differences between free and premium examples, or whether all named designs remain available. It gives no licence details, tenant requirements, support commitments or customization instructions. Check those points with the provider before using an external template, and confirm that its content and design meet your organization's accessibility, branding and governance needs.
For Microsoft-provided templates, the research notes describe site and page template options, including organization-saved designs, but they do not supply official Microsoft URLs to substantiate current behavior. That leaves open which options are enabled in a given tenant and what permissions are needed. The safest takeaway is to use the examples as design references and verify implementation details in your own SharePoint environment.
The description names business homepages, a hub, learning and development, human resources, financial services, healthcare and employee onboarding layouts.
The title and description promote free templates, but the examples also include premium healthcare and homepage designs. The supplied material does not explain pricing or terms.
A site template is a starting point for an entire site; a page template starts an individual page or news post. The research notes describe both, but no official Microsoft source URL was supplied to verify current behavior.
The supplied material does not specify a required SharePoint license, permissions or tenant configuration. Check the template provider and your organization's SharePoint policies.