Preview the prompt +
# Build brief — an original marketing website in the taste of Relato
> Reference: https://www.relato.com · UIDiscovery: https://uidiscovery.com/sites/relato · captured 2026-09-23 at a 1440px desktop viewport (+ 390px iPhone shots) · [full page](https://uidiscovery.com/media/captures/relato/full.png) · [scroll video](https://uidiscovery.com/media/captures/relato/preview.mp4)
## 1. Goal
Build an original marketing website for **[the user's brand]** that feels as considered as Relato — same structure, rhythm and polish, entirely new identity and content.
## 2. Originality rules
- Build an ORIGINAL design for the user's own brand in the same *taste* as Relato: structure, rhythm, hierarchy, palette mood and type pairing.
- Never reuse Relato's logo, name, product imagery, illustrations, icons, screenshots or copy. Write new copy for the user's product.
- If the user hasn't said what their product is, ask first (or use clearly marked placeholders like [Brand], [Product], [Audience]).
- Reference screenshots are for looking at, not for embedding or tracing.
## 3. The taste, in short
- Relato (relato.com): Marketing marketing website, light.
- 21 sections: Hero → Statement → Content → Features → Statement → Content → Features → Testimonials → Features → FAQ → Features.
- Spacing: short, dense bands (median section ≈463px).
- Type: one family (Antique Legacy). Imagery: mostly typography with little or no imagery.
## 4. Page structure (top to bottom)
### 1. Hero — state what the product is and for whom in one glance, and offer the primary action.
- Layout: headline-led stack: eyebrow → H1 → supporting line → actions, with a visual beside or below. Tall, ≈1.6 screens (1460px at 1440), own light band #ffffff; no images (type-led); no interactive controls.
- Slots: Eyebrow / announcement pill (optional); H1; Supporting line, 1–2 sentences; Primary action; No image — let type and colour carry it.
- [Screenshot](https://uidiscovery.com/media/captures/relato/s-01.webp)
### 2. Statement — a large-type moment that sets tone and pace.
- Layout: oversized typography with lots of space. Tall, ≈1.4 screens (1273px at 1440), own light band #ffffff; no images (type-led); no interactive controls.
- Slots: Heading; Body copy.
- [Screenshot](https://uidiscovery.com/media/captures/relato/s-02.webp)
### 3. Statement — a large-type moment that sets tone and pace.
- Layout: oversized typography with lots of space. Tall, ≈1.3 screens (1173px at 1440), own light band #ffffff; no images (type-led); no interactive controls.
- Slots: Heading; Body copy.
- [Screenshot](https://uidiscovery.com/media/captures/relato/s-03.webp)
### 4. Statement — a large-type moment that sets tone and pace.
- Layout: oversized typography with lots of space. Half to one screen (651px at 1440), own light band #ffffff; 2 image/graphics; 2 text links instead of buttons.
- Slots: Heading (~7 words, like the reference); Body copy; Supporting visual (see image plan); Text link action.
- Topic (tone/length only — never reuse): “One workspace for your entire content workflow.”
- [Screenshot](https://uidiscovery.com/media/captures/relato/s-04.webp)
### 5. Content — supporting content that deepens one idea.
- Layout: text + media block. Compact band (192px at 1440), own light band #ffffff; no images (type-led); 40 links (link lists / navigation).
- Slots: Heading; Body copy; Text link action.
- [Screenshot](https://uidiscovery.com/media/captures/relato/s-05.webp)
### 6. Content — supporting content that deepens one idea.
- Layout: text + media block. Compact band (351px at 1440), own light band #ffffff; no images (type-led); no interactive controls.
- Slots: Heading (~14 words, like the reference); Body copy.
- Topic (tone/length only — never reuse): “ChatGPT in one tab, project board in another, Google Doc in a third. Relato…”
- [Screenshot](https://uidiscovery.com/media/captures/relato/s-06.webp)
### 7. Features — explain the key benefits, grouped so each can be scanned in seconds.
- Layout: section title over a grid or alternating rows of benefit items. Compact band (391px at 1440), own light band #ffffff; 10 images/icons (a set of cards or a small gallery); no interactive controls.
- Slots: Section title (~3 words, like the reference); 2 items: icon or visual + short title + 1–2 line description.
- Topic (tone/length only — never reuse): “Without Relato”
- [Screenshot](https://uidiscovery.com/media/captures/relato/s-07.webp)
### 8. Features — explain the key benefits, grouped so each can be scanned in seconds.
- Layout: section title over a grid or alternating rows of benefit items. Compact band (368px at 1440), own light band #ffffff; 3 image/graphics; no interactive controls; 3 headings → ~2 items under a title.
- Slots: Section title (~8 words, like the reference); 2 items: icon or visual + short title + 1–2 line description.
- Topic (tone/length only — never reuse): “Assign agents to tasks like you assign people”
- [Screenshot](https://uidiscovery.com/media/captures/relato/s-08.webp) · imagery: slot 1
### 9. Features — explain the key benefits, grouped so each can be scanned in seconds.
- Layout: section title over a grid or alternating rows of benefit items. Half to one screen (435px at 1440), own light band #ffffff; 5 images/icons (a set of cards or a small gallery); 2 text links instead of buttons.
- Slots: Section title (~8 words, like the reference); 5 items: icon or visual + short title + 1–2 line description; Text link action.
- Topic (tone/length only — never reuse): “Agents to handle research, writing, editing, and optimization”
- [Screenshot](https://uidiscovery.com/media/captures/relato/s-09.webp) · imagery: slot 1
### 10. Features — explain the key benefits, grouped so each can be scanned in seconds.
- Layout: section title over a grid or alternating rows of benefit items. Half to one screen (463px at 1440), own light band #ffffff; 4 images/icons (a set of cards or a small gallery); 2 text links instead of buttons.
- Slots: Section title (~8 words, like the reference); 4 items: icon or visual + short title + 1–2 line description; Text link action.
- Topic (tone/length only — never reuse): “Agents and humans pull from the same Library”
- [Screenshot](https://uidiscovery.com/media/captures/relato/s-10.webp) · imagery: slot 1
### 11. Features — explain the key benefits, grouped so each can be scanned in seconds.
- Layout: section title over a grid or alternating rows of benefit items. Half to one screen (435px at 1440), own light band #ffffff; 5 images/icons (a set of cards or a small gallery); 2 text links instead of buttons.
- Slots: Section title (~7 words, like the reference); 5 items: icon or visual + short title + 1–2 line description; Text link action.
- Topic (tone/length only — never reuse): “Start with a proven workflow. Customize everything”
- [Screenshot](https://uidiscovery.com/media/captures/relato/s-11.webp) · imagery: slot 1
### 12. Statement — a large-type moment that sets tone and pace.
- Layout: oversized typography with lots of space. Compact band (224px at 1440), own light band #ffffff; no images (type-led); no interactive controls.
- Slots: Heading (~11 words, like the reference); Body copy.
- Topic (tone/length only — never reuse): “Testing an agent is free and easy. No content engineering required.”
- [Screenshot](https://uidiscovery.com/media/captures/relato/s-12.webp)
### 13. Content — supporting content that deepens one idea.
- Layout: text + media block. Half to one screen (479px at 1440), own light band #fddace; 40 image elements (icons, logos, product UI — not 40 photos); no interactive controls.
- Slots: Heading; Body copy; Supporting visual (see image plan).
- [Screenshot](https://uidiscovery.com/media/captures/relato/s-13.webp) · imagery: slot 1
### 14. Features — explain the key benefits, grouped so each can be scanned in seconds.
- Layout: section title over a grid or alternating rows of benefit items. Half to one screen (413px at 1440), own light band #ffffff; 10 images/icons (a set of cards or a small gallery); no interactive controls.
- Slots: Section title (~3 words, like the reference); 9 items: icon or visual + short title + 1–2 line description.
- Topic (tone/length only — never reuse): “Reddit Monitor Agent”
- [Screenshot](https://uidiscovery.com/media/captures/relato/s-14.webp)
### 15. Features — explain the key benefits, grouped so each can be scanned in seconds.
- Layout: section title over a grid or alternating rows of benefit items. Compact band (243px at 1440), own light band #ffffff; no images (type-led); no interactive controls.
- Slots: Section title (~7 words, like the reference); 3 items: icon or visual + short title + 1–2 line description.
- Topic (tone/length only — never reuse): “Don’t just take our word for it”
- [Screenshot](https://uidiscovery.com/media/captures/relato/s-15.webp)
### 16. Testimonials — let real customers make the case in their own words.
- Layout: quote cards or a featured quote with name, role and avatar. About one full screen (888px at 1440), own light band #ffffff; 5 images/icons (a set of cards or a small gallery); 4 text links instead of buttons.
- Slots: Section title; 2 quotes: 1–3 sentences, name, role, company, avatar; Use real customer quotes only.
- [Screenshot](https://uidiscovery.com/media/captures/relato/s-16.webp)
…and 5 more at https://uidiscovery.com/sites/relato.
Inner pages also captured (Pricing, Product, Customers, About, Blog, Docs, Contact, Security): https://uidiscovery.com/sites/relato?view=pages
## 5. Design system
### Colour
| Role | Hex | Use | Contrast on background |
|---|---|---|---|
| background | `#f9f8f7` | page background | — |
| foreground | `#400a24` | body text, headings | 15.4:1 |
| accent | `#e35b20` | primary buttons, links, highlights — sparingly | 3.4:1 (large text / UI only) |
| surface | `#ffffff` | cards, inputs, alternate bands | text on it 16.3:1 |
| muted | `#ffc077` | secondary text, borders | 1.5:1 — borders / large text only |
Captured palette: `#f9f8f7` `#400a24` `#ffffff` `#ffc077` `#e35b20` `#fddace`. Section bands top→bottom: `#ffffff` → `#fddace`. Roles are assigned automatically — sanity-check them against the screenshot. Keep the palette's *mood* (light, warm) and proportions; swap the accent for the user's brand colour.
### Tokens
```css
:root {
--background: #f9f8f7;
--foreground: #400a24;
--accent: #e35b20;
--surface: #ffffff;
--muted: #ffc077;
--font-heading: "Inter", ui-sans-serif, system-ui, sans-serif;
--font-body: "Inter", ui-sans-serif, system-ui, sans-serif;
--radius: 12px; /* calibrate from the screenshot */
}
/* Tailwind v4 — in globals.css after @import "tailwindcss"; */
@theme {
--color-background: var(--background);
--color-foreground: var(--foreground);
--color-accent: var(--accent);
--color-surface: var(--surface);
--color-muted: var(--muted);
--font-heading: var(--font-heading);
--font-sans: var(--font-body);
}
```
### Typography
- Headings: **Inter** (Google Fonts) — reference uses Antique Legacy. “Antique Legacy” is likely a custom or licensed face. Inter is a neutral stand-in — pick a closer free match by eye from the screenshot.
- Body: same family — a single-family system; create contrast with size and weight, not a second face.
- Scale (starting point, sizes weren't measured — calibrate against the 1440px screenshot): display clamp(2.5rem, 5vw, 4.25rem), h2 clamp(1.75rem, 3vw, 2.5rem), h3 1.25rem, body 1rem–1.125rem / 1.6, small 0.875rem. Headings: tight tracking (-0.02em), line-height 1.05–1.15.
### Spacing & rhythm
Sections run ≈463px tall at 1440 (median; range 192–1460px, captures cap at 1700px) — short, dense bands. Start with 64–80px vertical padding per section on desktop and about two-thirds of that on mobile. The background changes 2 times down the page — use band changes to mark chapters. 8px spacing grid, 1200–1280px max content width, 24px (mobile) / 32–48px (desktop) gutters.
### Shape, depth & theme
Radii and shadows weren't measured. Read exact corner radius, border and shadow treatment from the screenshots. Light-first; for a dark mode use a near-black (not #000) background, ~90% white text, lift surfaces with lightness not shadow, re-check the accent.
## 6. Imagery plan
Measured from 10 section screenshots: mostly **typography with little or no imagery** (light, warm, Marketing). Still glance at the linked screenshots to match the exact mood.
### Slot 1 · 8. Features, 9. Features, 10. Features, 11. Features, 13. Content → product UI (uncertain)
- Marketing sections with many image elements — most likely product UI screenshots/mockups plus icons. Count: one consistent treatment across these sections. Aspect: 4:3. Look first: [ref 1](https://uidiscovery.com/media/captures/relato/s-08.webp) [ref 2](https://uidiscovery.com/media/captures/relato/s-09.webp) [ref 3](https://uidiscovery.com/media/captures/relato/s-10.webp) [ref 4](https://uidiscovery.com/media/captures/relato/s-11.webp)
- **Stock** — “laptop blank screen minimal desk”: [Unsplash](https://unsplash.com/s/photos/laptop-blank-screen-minimal-desk?orientation=landscape) · [Pexels](https://www.pexels.com/search/laptop%20blank%20screen%20minimal%20desk/?orientation=landscape) · [Pixabay](https://pixabay.com/images/search/laptop%20blank%20screen%20minimal%20desk/?orientation=horizontal)
- **Generate** — `Product-shot backdrop for a UI screenshot: smooth light gradient from #f9f8f7 to #ffffff with a soft #e35b20 glow behind the centre, subtle floor shadow, empty centre area where a screenshot will be placed. Lighting: soft natural daylight, airy and high-key. Aspect ratio 4:3. No text, no letters, no logos, no watermarks, no brand marks or trademarked products, no recognisable real people. No UI elements.`
- Build the UI itself in HTML/CSS with realistic sample data from YOUR product (or screenshot your real app). Don't generate UI as an image and don't reuse the reference's screenshots. Stock/AI is only for the backdrop or device frame.
- **No imagery (type-led)** — 1. Hero, 2. Statement, 3. Statement, 4. Statement, 5. Content, 6. Content, 7. Features, 12. Statement, 14. Features, 15. Features, 16. Testimonials: No imagery needed — type, spacing and colour do the work. If the screenshot shows a background graphic, rebuild it in CSS (gradient, grid, noise) or a short muted video, not a stock photo.
### If the screenshots show a different style
Open the refs first and name what you actually see (photo / product UI / illustration / abstract gradient or 3D / type only). If it differs from the guess, switch routes — UI is built in code, type-only needs no image, otherwise:
- **photography** — generate `Photograph: abstract gradient mesh. Composition: wide shot, subject off-centre to one side, generous clean negative space for the headline. Lighting: soft natural daylight, airy and high-key. Warm colour grade that sits on #ffffff, #e35b20. Photorealistic, natural textures, shallow depth of field, 35mm lens. Aspect ratio 16:9. No text, no letters, no logos, no watermarks, no brand marks or trademarked products, no recognisable real people.` · stock: [“abstract gradient mesh” on Unsplash](https://unsplash.com/s/photos/abstract-gradient-mesh?orientation=landscape) (same query works on Pexels/Pixabay)
- **abstract 3D / gradient** — generate `Abstract 3D render: soft, matte clay shapes and a smooth gradient in #e35b20 and #ffc077 on a #f9f8f7 background. Lighting: soft natural daylight, airy and high-key; warm tone. Minimal and calm, generous negative space on one side for text. Aspect ratio 16:9. No text, no letters, no logos, no watermarks, no brand marks or trademarked products, no recognisable real people.` · stock: [“abstract gradient 3d” on Unsplash](https://unsplash.com/s/photos/abstract-gradient-3d?orientation=landscape) (same query works on Pexels/Pixabay)
- **illustration** — generate `Flat vector illustration: abstract gradient mesh, friendly simplified shapes, limited palette of #ffffff, #e35b20 plus one soft neutral, plenty of empty background, consistent line weight, warm mood. Aspect ratio 16:9. No text, no letters, no logos, no watermarks, no brand marks or trademarked products, no recognisable real people.` · stock: [“technology flat illustration” on Unsplash](https://unsplash.com/s/photos/technology-flat-illustration?orientation=landscape) (same query works on Pexels/Pixabay)
- **Licences:** Unsplash and Pexels images are free for commercial use under their own licences; Pixabay under the Pixabay Content License. Check each image's page before use, credit the photographer when asked (good practice anyway), and skip images showing logos, trademarks, branded products or identifiable people without a release.
- **AI generation:** the prompts work with any image model (GPT Image, Imagen, Flux, Midjourney, Firefly, SDXL…) — check its commercial-use terms. Never put the reference brand's name or “in the style of <brand>” in a prompt.
- **Never** download, trace or re-host the reference's own images, illustrations, product shots or logos.
## 7. Build steps
1. Confirm brand, product, audience and the primary action with the user.
2. Set up the tokens (CSS variables / Tailwind @theme) and load the fonts.
3. Build the sections in order, mobile-first, with each reference screenshot open.
4. Write original copy for every slot — match length and tone, never the words.
5. Source every image via the imagery plan (stock or generated); compress it and record credits.
6. Run the checklist at 390 / 768 / 1440px and fix what fails.
## 8. Acceptance checklist
- [ ] Responsive at 390px, 768px and 1440px — no horizontal scroll, tap targets ≥ 44px on mobile.
- [ ] Colour contrast WCAG AA: 4.5:1 body text, 3:1 large text and UI; visible focus states; full keyboard navigation.
- [ ] Semantic HTML: one <h1>, ordered headings, landmarks (header/nav/main/footer), labelled form fields, alt text on meaningful images.
- [ ] Performance: modern image formats with width/height set, lazy-load below the fold, ≤ 2 font families with font-display: swap, LCP < 2.5s.
- [ ] prefers-reduced-motion respected; animations under ~300ms and never blocking content.
- [ ] Originality: no copied logos, images, illustrations or copy from the reference; every image licensed or generated; credits recorded.
## 9. If you use Next.js + Tailwind
Paste the @theme block into globals.css, load fonts with next/font/google, make each section a server component in components/sections/, use next/image with explicit sizes, and keep client components for interactive bits only (menus, toggles, accordions).
---
More: tokens https://uidiscovery.com/api/v1/sites/relato/tokens · kit https://uidiscovery.com/api/v1/sites/relato/kit · MCP `get_design_brief({ slug: "relato" })`, `get_image_plan({ slug: "relato" })`. Cite the reference as https://uidiscovery.com/sites/relato.