Dev GuideAPI Reference
Dev GuideAPI ReferenceUser GuideGitHubNuGetDev CommunitySubmit a ticketLog In
GitHubNuGetDev CommunitySubmit a ticket

Start a Spire project

Describes how to start a Spire project.

Getting started with a Spire project is very similar to beginning an Optimizely Configured Commerce project with Classic CMS, with a few changes. See Understanding the development architecture for a front-end architecture diagram of Spire CMS.

All development work is the responsibility of the Implementation Team. As a result, implementation teams need to initiate the request to provision Configured Commerce environments in the cloud for Optimizely customers. This document outlines the process, environments, and resources involved to ensure a smooth transition for implementation teams and Optimizely customers.

Setup and configure

There are multiple data points that are needed to initiate a Configured Commerce project. Optimizely uses Git source control and infrastructure tools to deploy Configured Commerce websites to the cloud environment.

Additionally, the implementation team will authorize the GitHub account name insite-teamcity-build read-only access to the new repository for each Configured Commerce instance/project in the cloud.



Be sure to review the file when you complete your Developer Setup. You must add /contentadmin to the end of your site URL to access the Spire CMS.

Front end setup (/FrontEnd)

  1. Install node/npm
  2. Run `npm install` from /FrontEnd.

Follow the instructions below for use with Visual Studio Code and Rider/WebStorm.

Visual Studio code

  1. Open the /FrontEnd directory. A launch configuration is already present so no additional steps are required to start the application.
  2. (Recommended) Install the ESLint extension from Microsoft to see ESLint errors in the editor.


  • make sure to enable tslint settings - languages & frames - typescript - tslint - pick proper tslint.json file
  • turn on recompile on changes to see ts errors in rider
  • a number of launch configurations are already present

Launch Spire

  1. Run `npm run start` from /FrontEnd. This launches Spire with the default blueprint and port. Note: This step is already setup in Visual Studio Code and Rider as a launch configuration.
  2. Go to http://localhost:3000.

By default, API requests are forwarded to You can change this URL in the /FrontEnd/config/settings.js file.

Launch Spire with a custom blueprint

In addition to launching Spire with the base blueprint, you can create a custom blueprint and launch spire using that blueprint. The steps to do that are below:

  1. Create new blueprints in Spire.
  2. Run `npm run start {customBlueprintName}` from /FrontEnd.
  3. Go to http://localhost:3000.

You can also create a launch configuration in Visual Studio Code or Rider to launch spire using the custom blueprint.

Site generation

The pages for a site will automatically generate the first time a request is made to the server, if there are no pages present. You can force the regeneration of the site by running the following SQL statement in your Configured Commerce database:

DELETE FROM content.Node

Then load the site again.

Project initiation form

The following online form is used to capture the important data-points needed to provision the Configured Commerce in the Cloud environment.

To submit the project initiation form, follow the same process you would to submit a ticket and select the Project Initiation Form from the Form drop-down list. Populate the fields that appear. If you want your site to have access to Spire, you will need to indicate this in the CMS Type field. You may select both Spire CMS and Classic CMS if necessary.

Upgrade base code

After you have wired up your Extensions repo to your Spire environment, you can update the base code version yourself by updating the versionInfo.yaml file in your Extensions repo. Note that versionInfo.yaml is only used in a containerized environment and its not just for Spire. Non containerized environments will require a ticket to upgrade the base code version.

Deployment and environments

Optimizely provisions and maintain two hosting environments: Sandbox and Production. Note that Production environments for Spire-enabled projects will not be available until mid-July; starting on June 15, users can request a production environment, which will be provided four weeks after the request is made.

Code pushed to the Sandbox and Production branches are picked up by Optimizely's CI, which builds the Extensions, Classic Themes, and Spire Blueprints. For Sandbox environments, the deployment of the 'sandbox' branch artifacts are automatic. For Production environments, deployments are done by request.