> ## Documentation Index > Fetch the complete documentation index at: https://docs.brew.new/llms.txt > Use this file to discover all available pages before exploring further. # Set a Design Baseline > Everything about email-design.md and image-style.md: what they contain, and how to shape them, including from an email you already like. Without a baseline, Brew is highly creative: every generation tries different layouts and structures. That's useful while you're still finding your look. Once you know what your emails should look like, you want every generation to start from the same place. Your baseline lives in two markdown files, rendered in the [Brand tab](/brand/brand-identity): `email-design.md` for how emails are built, and `image-style.md` for how generated imagery looks. They are documents, not settings. Brew reads them at generation time, so whatever they say is what you get. ## What the Files Contain **`email-design.md`** is your email design system written as a document instead of a set of fields. Brew's extraction agent reads your site the way a designer would, studies colors, type, layout, and real screenshots, then writes up what it finds. It covers: * **Brand essence.** A short description of your visual personality and what mood the brand is going for. * **Signature moves.** The specific, repeatable details that make an email recognizably yours: an eyebrow label style, a divider treatment, how CTAs are shaped. This is the part a color palette alone can't capture. * **Color system.** Every color Brew uses, with the role each one plays (accent, ink, muted text, surface, hairline). Not just a swatch. * **Typography.** Heading and body fonts, weights, and the web-safe fallback stack Brew uses for inboxes that don't support custom fonts. * **Voice and standing instructions.** How your brand sounds (friendly, expert, witty, direct), plus rules Brew should follow on every generation: custom footer copy, formatting conventions, merge tags you always include. *"Always use sentence case in subject lines. Never use exclamation points."* belongs here, written as plain lines in the document. **`image-style.md`** art-directs any imagery Brew generates: palette, subject and composition, signature visual elements, lighting and mood, and rendering style, plus a hard list of what to avoid. If your brand uses a consistent illustration style, mascot, or photographic treatment, this is where it's defined. It's separate from your uploaded [Assets](/brand/brand-identity#assets), which Brew uses directly rather than as style guidance.

Because they're documents, you edit them the way you'd edit any text. Open **Brand → Email Design** or **Brand → Image Style** and change the line that's wrong. Switch a CTA from pill to square, tighten a color, rewrite a signature move. Every email generated after that inherits the change. There's nothing to save in a separate field; the documents are the source of truth Brew reads at generation time. ## 1. Let Extraction Write Them, Then Edit When you [add your brand](/get-started/add-your-brand), Brew writes both files from your site in about 30 seconds. If you upload a brand guide, PDF, or existing markdown during setup, your files win over anything inferred from the site; the domain only fills the gaps your uploads leave. Extraction is a starting point, not the final word. If your site doesn't reflect your brand accurately, edit the documents directly and your edits stand. ## 2. Start from an Email You Like If an email already nails the look you want (one Brew generated, a template you remixed, an import, or an email you forwarded in), you can make it the baseline without writing a spec yourself. Open the email on the canvas and click **Add to chat** in the toolbar. This brings that specific design into the conversation. > *"Make this the default layout for our emails, and update the brand design to reflect it."* Brew studies the email's structure, spacing, and signature details, then rewrites `email-design.md` to match. Your colors, fonts, and voice stay yours; the layout patterns come from the email. Open **Brand → Email Design** and read the updated document. It's the source of truth, so if Brew captured a pattern you don't want, delete that line and it's gone from every future generation. The baseline is a design guide, not a template. Brew learns the patterns and applies them to new content; it doesn't copy the email. ## 3. Scope a Baseline to One Email Type Your newsletter and your product announcements probably shouldn't share a layout. You can point a specific email type at its own reference instead of changing the global baseline. With the email added to chat: > *"Whenever I ask for a newsletter, base its design on this email."* Brew records the scoped preference in your brand spec. Newsletter prompts then start from that layout, while everything else keeps following the global baseline. Repeat with a different email for product updates, digests, or any other type you send regularly. ## Keep It Current The files are the single source of truth, so maintenance is editing text: * **A pattern stopped working?** Delete or rewrite its line in `email-design.md`. * **Generated images drifting off-style?** The fix lives in `image-style.md`, including its "do not" list. * **Rebranded?** Delete the existing brand and add it again from the brand switcher. Brew re-runs extraction against the current version of your site and writes fresh copies of both files. Or hand the new look to chat: add a redesigned email and ask for the update. Deleting a brand is permanent. It removes the brand workspace and its related data. Export or copy anything you want to keep before deleting. ## Related The map of the Brand tab: identity, assets, links, and settings. How extraction works, and how to upload an existing brand guide during setup. ## Need help? Our team is ready to support you at every step of your journey with Brew. Choose the option that works best for you: Type in the "Ask any question" search bar at the top left to instantly find relevant documentation pages. Click "Open in ChatGPT" at the top right of any page to analyze documentation with ChatGPT or Claude for deeper insights. Book time with our founders for personalized guidance on strategy, best practices, or complex implementation questions. Need immediate assistance? Reach us at **+1-(332)-203-2145** for urgent issues or time-sensitive questions. Our preferred support channel. You'll receive an invite after signup for direct founder support and fast responses. Contact us at **[support@brew.new](mailto:support@brew.new)** for detailed inquiries or if you prefer not to use Slack.