Dev GuideAPI Reference
Dev GuideAPI ReferenceUser GuideGitHubNuGetDev CommunityDoc feedbackLog In
GitHubNuGetDev CommunityDoc feedback

Add websites to a cloud project

Describes the process for adding websites to a Configured Commerce Cloud project.

You may decide to add websites, or subdomains, to your existing Cloud project. Before you do, see Microsite support in Spire for websites using the Spire CMS, or the Multi-site management articles for sites using the Classic CMS.

Access limitations

Access to the function of creating a website, including using site copy, is limited to Mission Control and requires a ticket to the Optimizely support team.

The following fields are also limited to modification in Mission Control once the site is created:

  • Key (website name)
  • Domain Names (including add/edit/delete)
  • CMS Type (Classic or Spire)
    • If Spire, we also need the blueprint name

The following fields are limited to the ISC_System or ISC_Implementer roles:

  • Active
  • Theme (if using Classic CMS)

Request an additional website

To add websites to an existing Cloud project, enter a support ticket:

  1. Select Configured Commerce Requests and Deployments from the drop-down menu
  2. Fill out the form by entering the subject (Add additional website).
  3. Create a new website for {client name} {environment type: production or sandbox} with the following template:
    • Containerized: Yes or No:
    • Client:
    • Display Name:
    • Description:
    • Key:
    • CMS Type (Spire or Classic):
    • Expected Domain Name:
    • Blueprint/Theme:
    • Sendmail Domain (if different than primary website):
  4. Select Add Additional Sites for the Configured Request Type.
  5. Add any attachments as needed.
  6. Click Submit.

After support notifies you that your additional site was created, use the Websites section of the Admin Console to manage it. Support doesn't copy existing websites, they only create new websites from scratch.

Note that when these websites are staged, you are provided with various DNS/TXT records that must be set for SSL, Mail, and other validation. These records should be set as soon as possible, but the site will not be cut over on a production site until you set the final CNAME record for the domain.

For further information on launching your new website, see Cloud customer launch checklist.