Skip to content
QuantCDN

Settings

The Settings screen holds project-wide options for how Studio builds, deploys, and assists you while editing. Open it from the gear icon in the Studio nav rail.

Settings are organised into three tabs: General, Languages, and Brand & Identity.

General

Section titled “General”

The General tab has two cards.

Build & Deploy

Section titled “Build & Deploy”
Setting Description
Use Quant Builder (beta) Toggle the browser-based build pipeline. When on, Studio renders pages in your browser and pushes them to the CDN, and Studio commits are tagged with [skip deploy] so GitHub Actions does not also run a deploy. When off, deployments go through the standard CI workflow.

When Quant Builder is active, an info banner appears with a link to the Deployments page, where the Build & Publish button replaces Deploy.

Production branch

Section titled “Production branch”

The production branch is the base for pull requests, the comparison target for the pending-changes count, the source for revert operations, and the branch whose deployments are polled in the toolbar.

Setting Description
Production branch Pick a branch from your repository. Defaults to main. If Studio can list your branches, this is a dropdown; otherwise a free-text input. Studio also shows your repository’s default branch as a hint.

Click Save to persist the change. The full branch model is documented under Branches and environments.

Languages

Section titled “Languages”

Configure Astro’s built-in internationalisation (i18n) support for multi-language sites. Toggling Enable i18n reveals these fields:

Setting Description
Default locale The primary language code (e.g. en).
Additional locales A comma-separated list of additional language codes (e.g. es, fr, de).
Prefix default locale When enabled, the default locale also gets a URL prefix (/en/about instead of /about).

Click Save i18n settings to write the configuration. Studio:

  1. Persists the i18n config to your project.
  2. Detects right-to-left locales (Arabic, Hebrew, Persian, Urdu and related languages) and records them as RTL.
  3. Adds or updates an i18n block in your project’s Astro config file (astro.config.mjs, astro.config.ts, or astro.config.js).

Disabling i18n and saving removes the i18n block from the Astro config.

Brand & Identity

Section titled “Brand & Identity”

Brand settings define your site’s identity and are made available to the AI assistant so that generated content matches your brand. They are also prefilled from migration when available.

The tab has four cards: Identity, Tone of Voice, Colors, and Fonts.

Identity

Section titled “Identity”
Field Description
Site Name Your website’s name.
Description A short description of your site.
Logo Path to your logo file (for example /images/logo.png).
Favicon Path to your favicon (for example /public/favicon.ico).

Tone of Voice

Section titled “Tone of Voice”

Free-text field describing how content should sound across your site. Pick a preset to prefill the field, or write your own:

Preset Approximate tone
Custom Empty — write your own.
Professional Professional and authoritative, clear and precise.
Casual & friendly Warm and conversational.
Technical Detailed and assumes domain expertise.
Government / public sector Plain language, follows WCAG content guidelines.

Colors

Section titled “Colors”

Define your brand colours for light mode and dark mode. Switch between Light and Dark to edit each set. Each entry has a name (e.g. primary) and a value (a hex code with a colour picker). Click + Add color to add more.

Fonts

Section titled “Fonts”

Define font mappings. Each entry has a key (a semantic role such as heading, body, or mono) and a value (the font family name, such as Inter). Click + Add font to add more.

Click Save Brand Settings at the bottom of the tab to persist all four cards in a single save.

Next steps

Section titled “Next steps”