Build options: Branding

sp-build-tasks supports branding build automation.

Basic branding settings are tweaked in ./config/app.json within the following parameters:

{
  ...
  "masterpagePath": "masterpage/frankfurt.master",
    // Relative to publishing folder path to custom masterpage
    // Is used in `gulp masterpage:apply` task
  "logoPath": "images/logo.png",
    // Relative to publishing folder path to custom logo
    // Is used in `gulp masterpage:apply` and `gulp logo:apply` tasks
  "masterpageCodeName": "frankfurt",
    // Masterpage code name
  "platformVersion": "2016",
    // Masterpage platform version (2016, 2013, etc.)
  "masterpage": { 
    // Custom structure object which properties 
    // can be used while compiling masterpage's .hbs
    "copyright": {
      "year": "2017",
      "title": "Contoso intranet"
    }
  }
  ...
}

Masterpage sources should be placed in:

• src
  • masterpage
    • frankfurt.2016.hbs
    • frankfurt.2013.hbs

Where frankfurt is a masterpageCodeName sample, 2016 or 2013 parts are platformVersion's. .hbs is a handlebars, masterpage .aspx's content should be copied to the .hbs initially.