Uploading and configuring components of your Brikit Platform on a different server.

The Design and Build phases of site design generally take place in a test or development environment (always our recommendation). In order to migrate into production, content and theme exports, as well as product settings, need to be transferred from one server to another. 

THEME PRESS

A site designed in Brikit Theme Press is generally comprised of three parts: a theme, one or more spaces, and a set of architect pages.

(Tip: Hover on the title links below for a description of each. Click through to the underlying glossary pages for more information, as needed.) 

Theme

If you are performing your own migration, you will first need to download your theme, and then upload it to your destination server. (If you are working with the Brikit services team the first step of downloading will be done for you, and you will be provided with a zipped theme file for uploading.)

Space(s)

One or more spaces containing body copy, dynamic page feeds, and other content.

These spaces are packaged in a zipped export file.

Architect Pages

The underlying pages that drive your page layouts (key for arranging content on the page), as well as your footer, header, and menus. Once again, delivered as a zip file.

BLUEPRINT MAKER

Accessing and Editing the JSON File

Best Practice

Plan for a 'freeze' on any updates in your development environment (theme, content, or otherwise) as work is migrated to production.

If using:

  1. Replace me with something to note about this how-to entry that falls outside the scope of all other sections; and
  2. Add the tight-bottom class to the next visible/non-collapsed block above this one to narrow the gap between the two blocks.

If using:

  1. Replace me with something to note about this how-to entry that falls outside the scope of all other sections; and
  2. Add the tight-bottom class to the next visible/non-collapsed block above this one to narrow the gap between the two blocks.

If using:

  1. Replace me with something to note about this how-to entry that falls outside the scope of all other sections; and
  2. Add the tight-bottom class to the next visible/non-collapsed block above this one to narrow the gap between the two blocks.