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

# Style Guide

> Your newsletter's look and feel, organization facts, and dos and don'ts, which your AI reads before writing

The **Style guide** is everything your AI reads before it writes an issue: how your emails look, what it needs to know about your organization, and the rules every issue is checked against. Fill it in once, change any part whenever you like, and every new issue starts from it.

It lives under **Campaigns → Style guide**, in four pages:

* **Overview** — where each part stands, and the step that confirms your starting style guide
* **Look & feel** — name, colors, fonts, and footer, beside a sample newsletter
* **Organization facts** — people, places, programs, and approved wording your AI can use
* **Dos & don'ts** — the instructions each issue is checked against

While setup is unfinished, **Overview** carries a **To do** badge in the sidebar.

## Finishing setup

Open **Style guide → Overview**. Add facts and instructions yourself, or hand your AI past newsletters and guidelines and ask it to propose them. Instructions your AI infers start as proposals, so review them: activate the ones you want and remove the rest. Then confirm your starting style guide.

Until setup is finished, every issue's checks include **Complete newsletter setup**, and that check blocks sending. You can finish with no instructions at all if your organization has no standing requirements yet. Unconfirmed facts stay marked for verification after you finish.

## Setting your look and feel

**Style guide → Look & feel** shows a sample newsletter on one side and the form that drives it on the other. The sample updates as you save.

* **Name** — **Brand name** (required) and **Tagline under the header**
* **Colors** — **Primary**, **Accent**, **Background**, **Text**, **Header background**, and **Header text**, each as a hex color like `#154849`. Leave a header color empty to use the primary color with white text.
* **Fonts** — one for **Headings** and one for **Body text**, from a list of email-safe fonts
* **Footer** — **Mailing address**, **Footer text**, and the **Show the "Read this issue on our website" link** checkbox

Click **Save look & feel**. These settings apply to every email unless an issue sets its own.

Your logo, button shapes, email width, and other styling aren't on this form. Ask your AI for those.

If your AI changes the look and feel while you have the form open, a warning says so. Saving then replaces its change with what's on your form; click **Load the latest instead** to keep its version.

### Mailing address

Every email prints your mailing address at the bottom. The law requires your organization's real postal address, either a street address or a PO box. You can save the form without one, but no campaign sends until it's filled in: the issue's checks show **Add your organization's mailing address** as a required failure that links back here.

### Hiding the web-edition link

Once an issue has been sent, it has a web edition, and each email carries a **Read this issue on our website** link to it above the footer. Clear **Show the "Read this issue on our website" link** to take that link out of every campaign. The unsubscribe link always stays.

The web edition page itself isn't listed by search engines.

### Sender details

The sender name, sender address, and reply-to address are part of the same brand kit, but they aren't on the **Look & feel** form. Ask your AI to set them. See [Sending and approval](https://zenorent.com/docs/campaigns/sending.md#sender-address) for how the sender address is used.

## Organization facts

**Style guide → Organization facts** holds what your AI must know: key people and their preferred titles, locations, programs, calendar practices, audience guidance, and approved wording. Each fact has a source, a confirmation status, and an optional **Valid through** date.

Set **Publication permission** to **Internal context only** for anything that should help the AI understand your organization without being printed. If an internal fact shows up in an issue anyway, the issue's checks ask a person to confirm permission to publish it or take it out.

Facts that are unconfirmed or past their **Valid through** date show up in every issue's checks. When the issue actually uses one, a person has to verify it before the issue can send.

## Dos and don'ts

**Style guide → Dos & don'ts** groups instructions into **Always do**, **Don't**, and **Check before sending**. For each one, set **Importance** to **Required**, **Preference**, or **Human review** (a person confirms it for each issue).

* **Exact-text checks** test whether a phrase is present or absent. They check the text only, not whether a fact is true.
* **Reviews** are for anything that needs judgment: meaning, factual accuracy, what an image shows, or permission to publish.

See [Sending and approval](https://zenorent.com/docs/campaigns/sending.md#checking-an-issue) for how these turn into checks on each issue.

## Asking your AI

The AI reads and writes the same style guide. For example:

* *"Read our last three newsletters and propose organization facts and dos and don'ts."*
* *"Make the header dark green with white text and use Georgia for headings."*
* *"Hide the 'Read this issue on our website' link."*
* *"Set the reply-to address to [office@example.org](mailto:office@example.org)."*

Its tools are `campaign_get_brand_kit` and `campaign_update_brand_kit` for the look and feel (`show_web_link` controls the web-edition link), and `campaign_get_editorial_context`, `campaign_save_organization_profile`, and `campaign_save_playbook` for facts and instructions. Facts it extracts start unconfirmed, and instructions it infers start as proposals.

Changing the brand kit or the facts and instructions clears any send that's waiting for approval, so the next send is approved against what's actually in the email.


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