Skip to Content

Frontends

A frontend is a website that shows a site’s content. Each has its own code, hosting and theme. A site can have several, all live at once, all showing the same content.

The active frontend is the one Visor works with: its preview, its theme and its starter kit. Changing which one is active doesn’t affect what visitors see on any of them.

Open Settings → Frontend. Everyone at the site can read this page, and Site Admins and Organization Admins can change things.

The frontends page

The Frontends page

Each card shows the frontend’s name, badges Active and First, whether Hosting ready, its latest Live and Preview builds, and its addresses. Click Manage to open it.

A frontend’s page

Overview

The Addresses section gives the Live website, Preview, Repository and Where its code started.

A frontend's Overview tab

Builds

A frontend's Builds tab

SectionWhat it lists
Live website buildsOne per Deploy. A merge into master also rebuilds the live website, but that build isn’t listed here.
Preview buildsPreview builds, newest first.

Site Admins and Organization Admins also have:

  • Rebuild preview: rebuilds the preview from the latest code, in about 5 to 10 minutes. The live website doesn’t change, and nothing is deployed or published.
  • Log: opens the build log, with likely errors highlighted and secrets masked. Use Copy to share it with a developer.

Code

You areYou see
A Site Admin or Organization AdminTemplate updates, and code changes waiting for review.
Anyone else at the siteCode changes waiting to merge, on the active frontend.

See Code Changes for how this works.

A frontend's Code tab

Template updates bring Visor’s fixes and improvements into the site’s code:

Get updates

The card shows how many template changes the site doesn’t have. Click Get updates. This opens a merge request, and nothing changes yet.

Merge

If it says Ready to merge, click Merge and build, then confirm. The site rebuilds in a few minutes.

If there are conflicts with the site’s own changes, a developer resolves them. See Template updates.

Settings

A frontend's Settings tab

The frontend’s fields, including:

FieldWhat it is
Analytics Id, under Site ConfigurationA GA4 measurement ID (G-…). It is added to the live website only, from the next Deploy. Leave it empty for none.
Template ConfigurationOne starter kit card per AI tool, each with Download. See Set Up Locally.

Addresses and hosting details are filled in when the frontend is set up. There’s rarely a need to change them.

Add a frontend

Use this to show the same content in another design. A site with its own content is a new site instead.

Open the form

Click Add frontend. If it is disabled, the page gives the reason. An older frontend may need Prepare for more frontends first, on its Overview tab. This rebuilds its preview, and its live website looks the same afterwards.

Fill it in

FieldChoices
NameFor example, Campaign 2026.
Start fromVisor template, or a copy of an existing frontend, which brings its widgets, layouts and themes.
HowFork stays linked to where it came from, so it can take updates. Clone is an independent copy.

Wait for it

It takes a few minutes, and you can follow it on the page. The active frontend doesn’t change.

Deploy then builds all frontends that are set up. Each one keeps its own theme.

Remove a frontend

On its Settings tab, under Danger zone, click remove and confirm. Its websites are taken down, its hosting is removed, and its code is archived and deleted after 7 days. The site’s content stays.

You can’t remove the active frontend, the site’s first frontend, or one still being set up.

To make another frontend the active one, use Theme Configuration.

Last updated on