This is a Next.js project bootstrapped with create-next-app.
This sample site use the same Music Festival backend site implemented with Optimizely CMS 12. Please refer to the README file of the backend site project and setup the backend site.
This sample site demonstrates how the frontend site can be implemented using next.js and deployed to Vercel. This site also demonstrates how the frontend site can integrate with OIDC providers like OptiID, Azure AD, or Optmizely CMS OpenIDConnect server.
Note: on page editing does not work for the Next.js version of the Music Festival frontend site, you can edit the pages using property view in CMS UI instead.
First make sure you are running the Music Festival Backend site. Please refer to the README for the backend site.
Make sure you have run the ContentGraph content synchronization job if you have not already to sync initial data from the backend site to ContentGraph.
First, configure ContentGraph endpoint and key in .env.local file.
- Replace the hostname with ContentGraph endpoint (e.g.: cg.optimizely.com).
- Replace the value of auth parameter with you HMAC single key, if neccessary.
Install dependencies
npm install
# or
yarnThen run the development server:
npm run dev
# or
yarn dev
# or
npm devOpen http://localhost:3000 with your browser to see the result.
The pages/api directory is mapped to /api/*. Files in this directory are treated as API routes instead of React pages.
This project uses next/font to automatically optimize and load Inter, a custom Google Font.
To learn more about Next.js, take a look at the following resources:
- Next.js Documentation - learn about Next.js features and API.
- Learn Next.js - an interactive Next.js tutorial.
You can check out the Next.js GitHub repository - your feedback and contributions are welcome!
The easiest way to deploy your Next.js app is to use the Vercel Platform from the creators of Next.js.
Check out our Next.js deployment documentation for more details.