New resource center page to help build your modern intranet on SharePoint in Office 365October 31, 2018
Modern SharePoint is ready, and we’re here to help you get there.
It’s time. It’s time to improve the performance from your intranet. It’s time to put the power of all your content, people and information in the pocket of each and every employee – especially when they are mobile. It’s time to improve your return on investment. Build your modern intranet on SharePoint in Office 365 and get the benefits of investing in business outcomes – reducing IT and development costs, increasing business speed and agility, and up-leveling the dynamic and welcoming nature of your intranet.
To learn more and take action, we invite you to visit and share the NEW “Build your modern intranet on SharePoint in Office 365” resource center page [https://aka.ms/SharePoint-build-modern-intranet]. This page contains:
- An overview for business, IT and developers
- A new FastTrack program to request assistance from partners
- Customer highlights – Wavemaker plus twelve other case studies
- Helpful ‘how to' guidance (12 new helpful resources on branding/design, permissions, search, navigation and more)
- plus, recent and relevant blogs and videos (#MSIgnite sessions)
The modern experience in SharePoint is designed to be compelling, flexible and more performant. The modern experience makes it easier for anyone to create beautiful, dynamic sites and pages that are mobile-ready. But what are the differences between the classic and modern experiences, and how do you go about creating a modern experience for your organization?
This aggregated set of materials and program are a starting point to help you learn about the modern experience and how you can begin to take advantage of it.
Plan to build your modern intranet on SharePoint in Office 365 – with insights, planning and the backing of Microsoft, its technology and its partners.
We are open to content and program suggestions to make this new resource center page even more helpful and clear. Let us know below in comments or via Twitter: @SharePoint.
Mark (@mkashman) Kashman