Config defaults

Overview

The web app centralizes its default configuration in:

This file exports schema objects like:

• CONFIG_SCHEMA_BACKEND
• CONFIG_SCHEMA_COMPANY
• CONFIG_SCHEMA_MARKETING
• CONFIG_SCHEMA_LANDING_PAGE

Pages and repositories use these defaults when a value is missing from runtime data (for example when backend-provided config hasn’t been set yet).

How defaults are chosen

Some defaults are resolved from Vite env first, then fall back to a safe constant.

Examples:

• API base URL — VITE_API_BASE_URL sets the API origin when present. In development, leaving it unset uses same-origin /api/v1/… (Vite proxy for HTTPS local dev — Vite → HTTPS local development). Otherwise the fallback is http://localhost:3000.

What each section is for

CONFIG_SCHEMA_BACKEND

• What it controls: where the web app sends API requests.
• Common changes:
  • Local HTTPS — leave VITE_API_BASE_URL unset so the dev server proxies /api to the API (see Vite (SvelteKit)).
  • Explicit origin — set VITE_API_BASE_URL when you need a fixed API URL (for example production or a custom port).
  • Point production web → production API (via your hosting env/secret injection)

CONFIG_SCHEMA_COMPANY

• What it controls: company/legal identity shown across the site.
• Common changes:
  • Company name (NAME)
  • Website URL (URL)
  • Support email (SUPPORT_EMAIL) — static default in the schema (and company config when stored)
  • Legal name / VAT / address (LEGAL_NAME, VAT_ID, COMPANY_ADDRESS)
• Where it appears (examples): About page and legal pages. Secret admin email sending uses SITE_NAME + SENDER_EMAIL_ADDRESS on the backend; the email manager may still show the schema support email as read-only context.

CONFIG_SCHEMA_LANDING_PAGE

• What it controls: default public home/landing page copy and toggles.
• Common changes:
  • Hero title / slogan (HERO_TITLE, HERO_SLOGAN)
  • Top banner toggle (ACTIVE_TOP_BANNER)
  • Product demo video (DEMO_SUBTITLE, DEMO_TITLE, DEMO_DESCRIPTION, DEMO_YOUTUBE_VIDEO_ID, DEMO_YOUTUBE_UPLOAD_DATE, DEMO_THUMBNAIL_ALT)
  • Secondary feature sections (FEATURE_1_* … FEATURE_7_* — subtitle, title, description per block)
  • Landing FAQ section (FAQ_SUBTITLE, FAQ_TITLE, FAQ_DESCRIPTION on the home page)
• Public FAQ section (CONFIG_SCHEMA_PUBLIC_FAQ — SUBTITLE, TITLE, DESCRIPTION, ITEMS on / and /pricing#faq; ITEMS uses the admin FAQ editor)

Navigation and footer constants

Meta tags, keywords, and social links live under CONFIG_SCHEMA_MARKETING — see SEO & marketing defaults.

Related configuration