> ## Documentation Index
> Fetch the complete documentation index at: https://docs.avocadostudio.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# The editorial brief

> Tell the site what it is about, how it should sound, and what it must never say — once, instead of in every prompt.

Repeating *"keep it in our voice, and don't mention pricing"* on every request
gets old, and it only works when you remember. Site settings holds a short
standing brief instead.

Open **Site settings** — click the site name in the top bar and choose **Site
settings**, or press the gear button on the site's card on the **Sites** page.
The **Brief** tab holds the editorial brief, in four parts: **Overview**,
**Tone**, **Constraints** and **Templates**.

## Overview

One or two sentences on what this site is for.

> A B2B logistics platform selling to operations managers at mid-size
> distributors. Buyers are sceptical, time-poor, and comparing us against
> incumbents they already dislike.

This is context, not instruction. It is what lets generated copy be about your
actual business instead of a generic version of your category.

## Tone

How the writing should sound.

> Direct and concrete. Short sentences. No exclamation marks, no "revolutionary",
> no "seamless". British spelling.

Tone rules that name things to *avoid* tend to work better than adjectives.
"Professional" means very little; "no exclamation marks" is unambiguous.

## Constraints

Hard rules, one per line. These are the things that must not happen, rather than
preferences about style.

```
Never name a competitor.
Never state a price or a discount percentage.
Never claim a certification we do not hold.
Always call the product "the platform", never "the tool".
```

Keep this list short and absolute. A constraint that is really a preference
belongs in **Tone**.

## Templates

Reusable page structures, each with a name and a description of what sections it
contains, in what order, with what content focus. Add one with **+ Add
template**.

> **Campaign landing page** — hero with a single offer, three proof points as
> cards, one testimonial, FAQ of five entries, closing CTA. No navigation to
> other products.

Once a template exists you can name it when creating a page:

> *"Create a /spring-sale page from the Campaign landing page template"*

## Where the brief applies

The brief is part of the site's configuration, so it is shared: every person
editing this site works against the same standing instructions, and updating it
updates it for everyone.

It is context rather than a filter. It steers what gets generated; it is not a
compliance gate, and it does not retroactively check content that is already on
the page. For the checks that do look at what is actually published — missing
metadata, broken links, images with no alt text — see
[site health](/features/site-health).

## Also in Site settings

The same drawer, titled **Site Config**, holds the rest of a site's
configuration, most of which is set once by whoever wired the site up:

| Tab | What lives there |
| - | - |
| **General** | Site name, the site's preview address, the header name and logo, and the switch for the drag-and-drop editor built on [Puck](https://puckeditor.com/) — see [Puck mode](/integration/puck-mode) |
| **Brief** | The editorial brief described on this page |
| **Deploy** | Hosting — the deploy target, so a publish can trigger a rebuild and link you to it — and media sources: a Google Drive folder, or your CMS's media library |

Published snapshots, and their **Restore** button, are on the **Sites** page
instead — see [review and undo](/editing/review-and-undo#published-snapshots-going-back-after-it-went-live).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.