I help organizations to unlock the power of SharePoint
SharePoint Online site owners can build branded intranet homepages with standard web parts, custom images, lists, and navigation, without custom code or third-party add-ons. The approach is useful for intranet owners and page editors who need to make key information easy to find for employees. SharePoint Maven Inc demonstrates these design techniques through examples tailored to different organizations.
The examples use familiar SharePoint components in different combinations rather than relying on a unique application for each industry. Homepages can bring together a welcome message, news, events, employee information, quick links, metrics, and resources. The content and visual style change to match the organization, while many of the underlying web parts remain the same.
Custom-designed images are one way to create visual tiles for projects, bids, departments, practice areas, or common resources. An image web part can display each tile and link it to a library, site, or other destination. That makes a visually prominent homepage element useful as navigation, not just decoration.
Other examples use native page features for specific tasks. A SharePoint list can show upcoming law-firm dates, while the Countdown Timer web part can count down toward an event or count up from a past date. The Hero web part can present images and calls to action as a carousel.
This approach is aimed at people who create or maintain SharePoint intranet pages, including site owners and page editors. The examples are framed around construction and engineering, marketing, law firms, car dealerships, manufacturing, universities, and retail stores. Their layouts are starting points: the same design can be adapted for another industry or organization.
The demonstrated pages use out-of-the-box SharePoint web parts and do not use custom code, SPFx, or third-party web parts. The presenter says no additional licenses are needed for the designs and that a Microsoft 365 license is sufficient. One exception to the general no-extra-license framing is the FAQ example: the presenter says Copilot is required to create that FAQ.
Some parts require content preparation rather than development. For example, custom tiles, banners, and employee recognition graphics need images created for the organization. News and events can be maintained using their respective SharePoint web parts, while a list can hold structured dates. The university example uses hub navigation to connect the homepage with other sites.
Across the examples, branding comes from the images, content, and arrangement of web parts. The manufacturing design, for instance, uses background imagery and coordinated colors to create a darker visual style; this is a design treatment rather than a separate SharePoint light-or-dark mode.
Some visual elements that look like live content are custom images. The People & Culture example uses a custom image for new hires or work anniversaries because, as the presenter explains, SharePoint does not have a web part for displaying birthdays and anniversaries. Those details therefore need to be represented in the image rather than automatically rendered by a dedicated web part.
That distinction matters when information changes frequently. An image-based tile or recognition panel needs its image updated when its content changes, whereas news and events can be maintained in their respective web parts, and dates can be recorded in a list. Choose the component based on how often the information changes and who will maintain it.
The layouts are examples, not a single required site structure. A tile can link to a separate site or a library, and hub navigation can connect multiple sites. Before building a homepage, decide which destinations employees need, which content should be editable by page editors, and whether a visual image or a structured list is the better fit.
The examples use standard SharePoint web parts and do not use custom code, SPFx, or third-party web parts. Custom images can provide branded tiles and banners.
It can count down to a future date or count up from a past date. Examples include a deadline countdown and elapsed time since the last accident.
A SharePoint list can show dates such as hearings and trials. The examples also use the Events web part to display events.
The presenter says Copilot is required to create the FAQ example.