A good SharePoint intranet homepage helps people find common tasks, current news and trusted information. It does not need elaborate custom design. Clear ownership, navigation and publishing discipline matter more than decoration.
For a broad internal audience, start with a SharePoint communication site. Use a team site when the main job is collaboration among members.
Start with user tasks
Ask a small cross-section of people what they come to the intranet to do.
Typical tasks include finding a policy, requesting leave, opening a business system, checking an announcement or locating a contact.
Group the answers into a short navigation structure. Use the words employees use. “Report an IT problem” is clearer than the internal name of the ticketing product.
Create the site and assign owners
You need permission to create the site, or an administrator must create it. Organisations can restrict site creation.
Give the site at least two accountable owners, keep the author group small and use Visitors for the broad reading audience. Review external sharing and sensitivity before publishing internal content.
Microsoft's communication-site walkthrough shows the standard authoring model and web parts.
Build a restrained homepage
A useful first version might contain:
- a short purpose statement
- Quick Links for frequent tasks
- News for current announcements
- Events where dates genuinely matter
- contact information for help
The Hero web part is useful for a few important destinations. Quick Links are better for a larger task list. Avoid several moving carousels.
Use images your organisation is entitled to publish. Add useful alternative text when an image conveys information. Check colour contrast and keyboard navigation rather than assuming a Microsoft theme makes every custom image accessible.
Use templates as a starting point
Microsoft provides built-in templates and sample designs through the SharePoint Look Book. Microsoft's sample-site guidance explains that samples can be added and customised.
A template supplies structure and example content. It does not decide your information architecture, permissions, ownership or content lifecycle.
Apply a template in a test site first. Record what it creates, remove sample material and confirm that it fits tenant policies.
Establish publishing rules
Name the owner and update rule for every homepage component. Decide who publishes news, removes expired announcements, checks Quick Links, reviews navigation and receives error reports.
If page approval is required, configure it before authors publish. Provide a recovery route for absent approvers.
Test with ordinary readers
Give representative users a handful of tasks and observe where they go.
Test on supported browsers and mobile devices. Check that the page makes sense when images do not load and that important links are not visible only through a visual tile.
Run Microsoft's Page Diagnostics for SharePoint on the homepage. Its rules identify likely performance issues on SharePoint pages, but it is not a substitute for user testing.
Launch the smallest homepage that answers the main tasks, then improve it from support questions, failed searches and reader feedback.
This process can produce a clear, supportable site. It does not guarantee engagement, adoption or accessibility compliance. Those outcomes need evidence.
For practical intranet, permission and page-design help, join the SharePoint & Teams Admins Space.