SharePoint Add-Ins Recipe - Themes

Work through the best techniques for custom branding SharePoint and Office 365 sites

Todd Baginski

by Todd Baginski on 4/10/2015

Share this:

Article Details

Date Revised:

Applies to:
branding, Office 365, Office 365 Patterns and Practices Guidance, OfficeDev, patterns and practices, PnP guidance, SharePoint 2013, themes


The approach you take to brand SharePoint sites is different in the new SharePoint Add-in model than it was with Full Trust Code. In a typical Full Trust Code (FTC) branding scenario, custom master pages, web templates, JavaScript, CSS files, and images are created to implement a custom brand. Additionally, SharePoint themes and composed looks may be created to implement a custom brand. These artifacts are typically packaged in a feature that uses declarative code and FTC to deploy the assets and register them with the SharePoint site.

In a SharePoint Add-in model branding scenario, all of the options associated with FTC branding scenarios are available. No matter which option you choose, you can deploy and register your branding assets on SharePoint sites via the remote-provisioning pattern.

You can read the rest of this Office 365 Patterns and Practices Guidance article on GitHub, here:

Topic: Development

Sign in with

Or register