Book Image

SharePoint Architect's Planning Guide

By : Patrick Tucker
Book Image

SharePoint Architect's Planning Guide

By: Patrick Tucker

Overview of this book

After opening a toolbox full of tools, it can initially be hard to know which is the right one for the job – which tool works best and when. Showing you how to create an informed and purposeful plan for SharePoint Online in the context of the Microsoft 365 suite of tools is what this book is all about. SharePoint Architect's Planning Guide will help you understand all you can do with SharePoint. Whether the tools are new to you or you’ve used the older versions in the past, your journey will start by learning about the building blocks. This book is not a step-by-step guide; there are tons of online resources to give you that and to help you better keep up with the pace of change. This book is a planning guide, helping you with the context, capabilities, and considerations for implementing SharePoint Online in the most successful way possible. Whether you need to plan a new intranet, migrate files to a modern platform, or take advantage of tools such as Power Platform, Teams, and Planner, this guide will help you get to grips with the technology, ask the right questions to build your plan, and successfully implement it from the technical and user adoption perspectives. By the end of this Microsoft book, you’ll be able to perceive the toolbox as a whole and efficiently prepare a planning and governance document for use in your organization.
Table of Contents (17 chapters)
1
Part 1:From Farm to Cloud
5
Part 2:From Lone Wolf to Pack Leader – SPO Integrations with M365
9
Part 3:From Tall to Flat – SPO Information Architecture
13
Part 4:From Current to Change

Frameworks for development

The options we’ve discussed so far have been one step away from implementing SharePoint with out-of-the-box functionality. Even though JSON and PowerShell have been involved, our approach can be better described as customization than custom development. However, we would be remiss if we didn’t at least address some of the best-practice options, tools, and practices around developing components for SharePoint Online and programmatic ways to work with its features.

There are three primary areas I would like to focus on that represent a central core when planning to architect solutions inside of SharePoint and using it as a platform, rather than a data source – provisioning, UX extensibility, and scripting/APIs.

Provisioning

We have already explored the use of site templates as a mechanism for provisioning new sites and associated artifacts, but it is not the only option we have. The Microsoft 365 platform community exists as a...