Configuration

This section will guide you through the process of configuring your Foundation app.

Foundation App

Foundation app: Tooling-agnostic. Only requires Kraken API configuration. You're free to choose your own CMS, UI library, analytics, payment processing, and error tracking tools based on your project needs.

App configuration

The Foundation app has an app.config.ts file in its src folder. This file allows you to customize various aspects of your app, such as the name, description, port, supported languages, and more.

Note: Some values in app.config.ts are sourced from the sibling file app.i18n.json, as they are referenced in JavaScript files like next-i18next.config.js and next-sitemap.config.js.

Environment variables

To configure the different services used in your application, create a duplicate of the .env.example file and rename it to .env.local in the root of your app.

Keep in mind that all services are optional except for Kraken (see Kraken below).

If you decide not to use certain services, make sure to delete any related code.

There is no specific order in which you need to configure the services, but it is recommended to configure the ones you want to use before deploying the app to Vercel.

Kraken

Essentially, every page that requires data from Kraken needs to have these environment variables set up correctly. This is vital for authentication to work. Request these values from your Kraken Client Delivery Lead or your authorized Kraken representative.

Set up environment variables

Find out what your Kraken API endpoint is and use it as the value of the KRAKEN_GRAPHQL_ENDPOINT environment variable in your .env.local file.