Migrating customizations

You have completed customizations, and a new version of the GBC is released. What steps do you need to take to move your customizations to the latest version?

First, you must download and set up the project directory for the latest version, as documented in the section "Setup your customization project" from Getting started with GBC. Then you will need to move your theme parts and customizations from the old project into the new project.

Steps summarized

Extract the project package to a directory. This becomes the <GBC_PROJECT_DIR>.

Complete the following:

$ cd $GBC_PROJECT_DIR
$ npm install
$ grunt

Copy the customization directories from the previous GBC project and add them to <GBC_PROJECT_DIR>/customization.

If you added global theme parts in the previous GBC project, you must move those global theme parts into your new project. To keep them global, copy those theme part directories and add them to <GBC_PROJECT_DIR>/theme. Alternatively, you can use this opportunity to move them into a local theme parts directory.

TIP: To ease migration, it is recommended that you use local theme parts. Using local theme parts eleviates the need to manage changes to the global theme parts directory during a migration.

IMPORTANT: Prior to 1.00.52, all theme parts were stored in the global directory <GBC_PROJECT_DIR>/theme. As part of the migration, it is recommended that you move those theme parts into the local theme parts folder for the customization, <GBC_PROJECT_DIR>/customization/<customization_project_dir>/theme.

If you modified any of the default global theme part directories, you may want to examine any changes to the most recent default theme parts, and merge your changes accordingly.