Website

Overview

Defaults for the public Website builder and for Sales funnels branding: color system, typography, navigation layout, header treatment, and container width. Individual pages can still override pieces in the Pages editor—this app is the workspace-wide baseline.

Languages — where it lives

Visitor-facing languages are not the same as your personal UI language under Account. Here you choose which locales appear on your public website, funnels, forms, and appointment pages.

From Website, use Languages in the card header to open the same panel inline—Back returns to the theme. You can also open the full Website languages screen from Settings (direct route: Settings → Website languages) when you want a dedicated page with a Back to website appearance link.

Languages — primary and list

One language is marked Original text (primary / source locale). That is the baseline copy the system extracts from your published content.

Every other enabled language is a visitor language you add. The table shows each code with actions; primary has no remove or bulk-translate row—only additional languages do.

Languages — adding locales

Add language opens a dialog where you tick one or more supported codes (anything not already enabled). You can Add languages manually to only extend the locale list, or Add & translate with AI to save the locales and queue background translation jobs for each new language at once.

Bulk jobs are polled in the UI; progress survives an app refresh in the same browser session. When those jobs finish, you get a toast; if Add & translate was used, the dialog can close automatically when all queued jobs complete.

The dialog reminds you that AI translation uses quota (each translated page consumes multiple AI requests—see the in-app cost hint). If background translation cannot start, check that your worker is running or add languages manually and use Translate all pages with AI per language later.

Languages — per visitor language

For each non-primary language, Translate all pages with AI enqueues a workspace-wide bulk job for that locale (disabled while a job for that language is already running).

Edit translations opens Page-by-page translations for that locale: pick a resource type and item, then edit strings in a table.

Remove stops offering that locale on the public site; stored translations are kept until you add the language again. A confirmation explains this.

Languages — page-by-page editor

First choose what you are translating: Website page, Sales funnel page, Form page, or Appointment page. Only types that actually exist in your workspace appear. Then pick the specific page / form / booking from the second list.

Strings load only for published website-style content—unpublished pages show an error until you publish. If nothing exists yet, you will see a nothing to translate style message.

The table shows original text (primary language) beside the target language. Row labels humanize internal field paths and group related keys: meta (SEO title and description first), theme, then body content. Identical source text used in multiple fields can share one row; SEO title and description never merge so you always have separate fields.

Leave a translation empty to keep showing the original string on the live site. Only non-empty values are stored. Edits auto-save after a short debounce (watch the save status).

Translate the page with AI fills the current resource only (review suggestions before relying on them). When your primary domain is known, View live page opens the public URL for the selected item in the language you are editing.

Members without edit permission can view the table; hints explain that only editors can change translations.

Languages — after you change originals

If you edit primary-language content or change structure, translations may be out of date. The panel notes that you should update translations manually or with AI again for affected locales.

Logo and favicon

Website logo is stored on the Company record: pick an image from the file manager (Upload / Edit), or Remove to clear it. It is the same asset other parts of the product may use for your business identity.

Favicon is stored with website appearance: small icon shown in browser tabs—upload or replace via the file manager, or remove it. Favicon can be saved even before the rest of the theme is filled in.

Theme controls and preview

Below the assets you get a live-style preview block. Choose a color palette from presets or switch to custom and edit primary, secondary, accent, background, text, and title colors.

Set menu alignment (how the nav sits in the header), container width (full vs boxed layouts), header style, and separate fonts for titles versus body text. Changing any of these triggers a debounced auto-save—watch the save indicator in the header instead of hunting for a single Save button for the theme fields.

Pushing changes to existing pages

When the saved theme’s colors, fonts, container width, menu style, or header style change compared to the previous version, the app runs a bulk update across your Website pages so published content picks up the new look. A toast summarizes how many pages were updated and whether any were skipped.