Overview

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

Foundation App vs Legacy Apps

• 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.
• Legacy apps (GB/FR/demo-site): Include specific integrations with Storyblok (CMS), Coral (UI), Google Analytics, Stripe, and Sentry. These apps are being phased out.

The guides below cover required configuration (Kraken) for all apps. Legacy-specific configuration guides (Storyblok, Google Analytics) are retained for existing users with bookmarked links, but are not recommended for new implementations.

Scope shared (agnostic) code to your app

Each app has a app.config.ts file in their src folder, which is responsible for scoping every shared piece of code from the core package to your app. This file allows you to customize various aspects of your app, such as the name, description, port, supported languages, and more.

Note: The legacy apps (GB/FR/demo-site) include Coral theming configuration in the theme property. The Foundation app is UI framework-agnostic, allowing you to choose your own UI library.

Note: Some values in app.config.ts are sourced from the sibling file app.i18n.js, 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.

In the following pages, we will guide you through the configuration process for each service. Keep in mind that all services are optional except for Kraken.

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.