Repository files navigation

• 1. Introduction
• 2. Getting started
  • 2.1. Requirements
  • 2.2. Deploying & Configuring
  • 2.3. Additional configuration options
• 3. Content pack upgrade
• 4. Product specific instructions
  • 4.1. Content Recommendations
• 5. Further documentation

This repository contains content and frontend that form the Optimizely SaaS CMS Demo Site.

If you're looking to build a new site from scratch, please use theCreate Next App Template to create an empty frontend using the same structure and tooling as this demo site.

Make sure you're good to go, by:

• Requesting an Optimizely CMS instance usingSign-up for the program
• Ensure you have a GitHub account
• Ensuring you have (at least) a hobby plan account at Vercel, or are comfortable creating one

After signing up for the beta instance and provisioning of the instance, you'll get an e-mail with the keys and instructions to activate your account.

Follow these instructions to configure the CMS

After you've completed the CMS configuration instructions and collected the needed information, click the "Deploy to vercel" button below, to deploy this site to your Vercel Account

When the deployment has succeeded, the following steps are needed to both fix the "Page not found" on the homepage and enable "Preview".

Fix "Not Found" error and enable preview

Please refer to theSupported environment variables document for all supported configuration options for the frontend. The steps above only outine the mimimum required configuration to obtain a working demo site. Many of the included features require additional configuration to be enabled.

Please note: every configuration change to the environment variables requires a new deployment to become active.

When installing the latest version of this demo site, you might need to apply a content pack update.

To upgrade the content pack, take these steps:

• Import the new content pack as described onConfiguring the CMS. The only difference here is that you willnot create a new Application, but update the existing one use the newly imported homepage.
• Make sure to run the Graph Full Index as specified

Running this upgrade process will yield you a working demo site, however it will now contain content-types that are no longer supported. If you need them back you can restore the code fromapps/old_cms_types in your fork/clone of this repository.

For Content Recommendations to work, the following steps are needed:

1. Configure Content Recommendations using the environment variables of theNext.JS Optimizely One package
2. Add the Content Recommendations widget using either the block (Page) or element (Experience), you will need to configure:
   • The API Key of the delivery, which is shown as value of 'data-api-key=' in the example code within Content Recommendations
   • The number of recommendations to show

• Local development
• CMS Configuration
• Enable on-page / in context editing
• Supported environment variables
• Custom demo building
• General solution description