---
title: "A tour of the project page | Briks"
url: https://briks.dev/docs/the-project-page
description: "A guided tour of a project in the Briks studio: the conversation, the live preview and its screen widths, the tabs under the top bar, Settings and Publish."
last_updated: 2026-10-08
---

# A tour of the project page

Every site, app or dashboard you make in Briks has its own project page. It is where you talk to Briks, watch the site change and reach everything else the project has. This tour goes round it once, so you know what each part is for before you need it.

10 minute read Checked against the studio on 8 October 2026

1. 1 Where you are: **Projects**, then the project's name, with its address on a wide screen. Under it, the project's tabs in words: **Studio**, **Analytics**, **Media**, **Database** (once the project has one, and before that for Owners and Admins), **Storage**, **Chatbot** and **Settings**.
2. 2 The conversation. Ask for a change or ask a question in plain words.
3. 3 The preview of your site, refreshed after each publish.
4. 4 Preview tools: the width to view it at, reload, full screen and open in a new tab.
5. 5 **Publish** takes the site to production when you are ready.

The project page of a sample bakery site: where you are and **Publish** along the top bar, the project's tabs under it, the conversation on the left and the live preview on the right.

## Opening a project

Click **Projects** in the sidebar, then the project you want. Your latest projects are also listed under **Projects** in the sidebar itself, each with a dot for its state, so you can jump straight to one. A project always opens on its **Studio** tab: the conversation and the preview side by side.

Where

1. Projects
2. Your project
3. Studio

On a laptop or desktop the two sit next to each other. On a narrow screen, such as a phone, the conversation comes first and the preview sits underneath it.

## The top bar

The bar across the top says where you are. On the **Studio** tab it reads **Projects** and the project's name. On any other tab the tab's name follows, then any section or view you have opened inside it, for example Projects / Crumb & Co bakery / Settings / Domain. Each part before the last is a link back to it. On a wide screen the project's live address sits beside its name and opens the site in a new tab.

Under that line is a row of tabs in words, with the open one underlined. On a phone the row scrolls sideways, and the line above it shows only the project's name.

| Tab | What it holds | Read more |
| --- | --- | --- |
| **Studio** | The conversation and the preview. Changes and questions go here. | [Making changes](https://briks.dev/docs/making-changes) |
| **Visual Editor** | Your own page beside a panel: click anything to change its words, pictures and look, then publish with no credits used. It comes with paid plans. | [Visual Editor](https://briks.dev/docs/visual-editor) |
| **Analytics** | Visitors, pages and where they came from, in a **Data** view and a **Settings** view. | [Analytics](https://briks.dev/docs/analytics) |
| **Marketing** | Posts for the site's social accounts. The tab shows once posting is open on Briks. | [Marketing and social posts](https://briks.dev/docs/marketing) |
| **Media** | Every picture and video the site shows as last published, each with **Replace**. | [Media library](https://briks.dev/docs/media-library) |
| **Database** | What the site stores, collection by collection. It shows once the project has a database, and before that only to Owners and Admins, so they can make one. | [Database](https://briks.dev/docs/database) |
| **Storage** | Files the project keeps, for its pages and for you, in **Files**, **Usage** and **Settings** views. | [Storage](https://briks.dev/docs/storage) |
| **Chatbot** | A chat for the published site that answers from its own pages and passes on what it can't answer. | [Chatbot](https://briks.dev/docs/chatbot) |
| **Settings** | Everything else: the project's name and marks, its domain, forms, chats, email, versions, backups and tools for developers. | See below |

At the far right of the bar, once the site has been published for the first time, you'll see a grey **Preview** tag and a **Publish** button. Every build lands at a preview address first. It is kept out of search engines, and messages sent through its forms are kept in the studio rather than emailed. **Publish** runs a launch check and, if nothing needs fixing, takes the site to production. After that the button reads **In production**, and clicking it offers **Back to preview**.

Publish waits for builds

While a build or change is running, **Publish** is greyed out with the hint “Wait for the current build to finish”. It comes back as soon as the work ends. The full walkthrough is in [Publish to production](https://briks.dev/docs/publish-to-production).

## The conversation

The left side is a running conversation between you and Briks. Your messages sit on the right in dark bubbles and Briks's replies sit on the left. Under each reply is a small line with the credits that request was charged and roughly how long it took. Above the conversation, a status pill shows where the site stands (**Draft**, **Building**, **Live** or **Needs attention**) and, once anything has been charged, the project's running total in credits.

- **Ask for a change** in plain words, such as `Add our Saturday hours to the footer: 9am to 1pm`. Briks builds and publishes it. See [Making changes](https://briks.dev/docs/making-changes).
- **Ask a question**, such as `When did the site last change?`. Briks answers in the thread without building anything. See [Asking questions](https://briks.dev/docs/asking-questions).
- **Answer Briks's questions** before a first build, or approve its words, look or hero if those steps are switched on. See [Approve as it builds](https://briks.dev/docs/approval-steps).

The box at the bottom reads “Change the hero, add a page, adjust the colours…” until you type. Enter sends, and Shift with Enter starts a new line. Beside the box are three buttons: **Attach pictures**, **Add from your media** and **Speak your request**. Under it is a switch, **Check the site after this change**, which looks at the published site at four screen sizes and repairs anything that renders broken. It adds a few minutes, and your choice is remembered for that site in your browser.

If your role is Viewer, the box is replaced by a note: “You can view this project. Changes are made by Editors, Admins and Owners of this workspace.” You still see the whole conversation and the preview.

### While something is building

A panel appears in the conversation with a timer, the steps the job goes through and one line underneath saying what Briks is doing right now. For a change the steps are **Applying your changes**, **Verifying build** and **Publishing**, plus **Checking the published site** if you switched the check on. A **Stop** button sits beside the timer. The box stays open and its button changes to **Queue**, so you can line up your next request while this one finishes.

## The preview

The right side is your real, published site in a frame. It isn't a picture: you can scroll it, click its buttons and use its own menu to move between pages. The tag above it reads **Live preview** with the time of the last publish, and the frame reloads by itself a moment after every publish, so you always see what visitors see.

| Control | What it does |
| --- | --- |
| **Desktop** | Shows the site at the full width of the frame. |
| **Tablet** | Shows it 834 pixels wide, framed, like a tablet held upright. |
| **Phone** | Shows it 390 pixels wide, like a typical phone. |
| The page list | Shows once the site has more than one page: pick a page to open it in the frame. |
| Undo and redo arrows | Step back to the previous version, or forward again. See [Versions](https://briks.dev/docs/versions). |
| **Versions** (the clock, showing the live number such as v7) | Lists every saved version, with **Make live** and **Test against live**. |
| **Reload preview** | Loads the page again without waiting for a publish. |
| **Full screen** | Gives the preview the whole window. Press Esc to close it. |
| **Open in new tab** | Opens the site at its own address. |

Before the first publish there is no site to show yet, so the preview lays your page out part by part as Briks plans and writes it. Once other pages are planned, small tabs (**Home** and each page's name) let you look at each one. [Watching a build](https://briks.dev/docs/watching-a-build) explains that view.

Make room

Drag the thin handle between the conversation and the preview to give either side more space, and double-click it to go back to the default. The width you drag to and the screen size you pick are both remembered in your browser.

## The Settings tab

**Settings** gathers everything that isn't a tab of its own. It opens on **General**, with every section listed down the left in groups. On a narrow screen, such as a phone, the list folds under one control that reads **Settings:** and the name of the open section. Tap it to choose another.

| Section | Group | What it's for | Read more |
| --- | --- | --- | --- |
| **General** | At the top | Name, logo, favicon, the Built with Briks badge, Made with Briks, copying, moving and deleting. | [Project settings](https://briks.dev/docs/project-settings) |
| **Domain** | At the top | The site's address and your own domains. | [Connect your domain](https://briks.dev/docs/custom-domains) |
| **Preferences** | At the top | The rules every build keeps to, where pictures come from, what each change does and the websites the site may load from. | [Project settings](https://briks.dev/docs/project-settings) |
| **Forms** | **Forms and email** | What visitors send through the site's forms. | [Forms](https://briks.dev/docs/forms) |
| **Chats** | **Forms and email** | Every conversation visitors had with the site's chat in the last 90 days, newest first, with **Export CSV**. | [Chatbot](https://briks.dev/docs/chatbot) |
| **Emails** | **Forms and email** | Email the site sends its visitors. | [Site email](https://briks.dev/docs/site-email) |
| **Sign-in** and **Payments** | **Accounts and payments** | How your site's visitors sign in, and the payment processor the site takes payments with, each with your own keys. | [Sign-in and payments](https://briks.dev/docs/sign-in-and-payments) |
| **Versions** | **Versions and backups** | Every version that was published, each with a way to restore it. | [Published versions](https://briks.dev/docs/publish-history) |
| **Backups** | **Versions and backups** | Every version of the code, ready to restore, or to download on a paid plan. | [Backups](https://briks.dev/docs/backups) |
| **File Explorer** | **Developer** | The code written for the site: read it and edit it, and download it on a paid plan. | [Your site's code](https://briks.dev/docs/code) |
| **GitHub** | **Developer** | Keeps the site's own code in a GitHub repository, in step both ways. | [GitHub sync](https://briks.dev/docs/github) |
| **Secrets** | **Developer** | Keys and passwords the site's own code reads. Once saved, a value can never be shown again. | [Secrets](https://briks.dev/docs/secrets) |
| **Webhooks** | **Developer** | Tell other services when something happens on the site. | [Webhooks](https://briks.dev/docs/webhooks) |
| **Deploy hooks** | **Developer** | Secret addresses that publish the project again when something calls them. | [Deploy hooks](https://briks.dev/docs/publish-history) |
| **Scheduled tasks** | **Developer** | Calls the project makes on a schedule, in your time zone. | [Scheduled tasks](https://briks.dev/docs/crons) |
| **Logs** | **Developer** | Every build, change and publish, and the steps each went through. | [Logs](https://briks.dev/docs/logs) |

Links saved before these sections moved to Settings, such as ones in older emails, still work: they open the same section here.

## A first look, step by step

Ten minutes with a new project

1. Check the status

   Where: Studio

   Look at the pill above the conversation. **Live** means the last publish went through. **Needs attention** means the last job failed, and the conversation says why.

2. See it on a phone

   Where: Preview toolbar

   Click **Phone**, scroll the whole page and open the menu. Most of what people want to fix shows up here first.

3. Click through the pages

   Where: Preview

   Use the site's own menu inside the frame to visit each page, exactly as a visitor would.

4. Open the versions

   Where: Versions

   Click the clock icon with the version number. Every build and change is listed, and the one visitors see is marked **Live**.

5. Name it properly

   Where: Settings, General

   Open the **Settings** tab, which opens on **General**. Check the project name, add your logo and favicon if you have them, and press **Save** under **Name and marks**.

6. Ask for your first change

   Where: Studio

   Back on **Studio**, write one specific change and press Enter. Watch the steps, then look at the preview when it reloads.

7. Publish when you're ready

   Where: Top bar

   Press **Publish**. The launch check runs first and its result arrives in the conversation.

## What each role sees

| Role | On the project page |
| --- | --- |
| Owner and Admin | Everything, including deleting the project, moving it to another workspace and changing its address. |
| Editor | Changes, questions, publishing, versions, A/B tests, the Visual Editor and editing code. Not deleting, moving or changing the address. |
| Viewer | The conversation, the preview, the versions list and analytics, read only. No prompt box, no **Chats** log, and the Visual Editor only to look through and comment. |

Roles belong to the workspace, not to one project. [Members and roles](https://briks.dev/docs/members-and-roles) has the full table.

A copy of a template

If you made the project from a template and it still shows the old business's details, a strip above the conversation says so, with a **Make it yours** button that rewrites the site for your business. See [Templates](https://briks.dev/docs/templates).

### Why is there no Publish button?

It appears once the site has been published for the first time. Until then there's nothing to take to production.

### Why can't I see the Database tab?

It shows once the project has a database. Before that, only Owners and Admins see it, so they can make one. [Database](https://briks.dev/docs/database) explains how one is made.

### Why can't I see the Visual Editor tab?

The Visual Editor comes with paid plans, so a workspace on Free doesn't show the tab. An Owner can change the plan in **Billing**. See [Visual Editor](https://briks.dev/docs/visual-editor).

### The preview looks out of date.

Click **Reload preview**. After a publish, the frame waits a couple of seconds before reloading so the new version is ready everywhere.

### Who can stop a build?

Editors, Admins and Owners. Stopping one that hasn't started yet costs nothing.

## Read next

- [Working on a project **Making changes** How to change your site by writing to Briks: what to say, adding pictures, what a change holds and costs, inner pages, queued requests and fixing a miss.](https://briks.dev/docs/making-changes)
- [Working on a project **Versions, undo and redo** Every build and change is saved as a version of your site. Undo a change, redo it, or put any earlier version back live exactly as it was, with no credits held.](https://briks.dev/docs/versions)
- [Publishing and domains **Publish to production** Take a Briks site from preview to production: what the launch check reads, what blocks a launch, how to fix each finding and how to go back to preview.](https://briks.dev/docs/publish-to-production)
- [Getting started **Exploring the dashboard** A guided tour of the Briks dashboard: the navigation, Home, Projects, Templates, Agents, Jump to, notifications, your credits and the tabs inside a project.](https://briks.dev/docs/exploring-the-dashboard)

Still stuck?

Write to [hello@briks.dev](mailto:hello@briks.dev) with your project's name and what you expected to see. A screenshot helps.