Preview the prompt +
# Build brief — an original marketing website in the taste of Rize
> Reference: https://rize.io · UIDiscovery: https://uidiscovery.com/sites/rize · captured 2026-09-22 at a 1440px desktop viewport (+ 390px iPhone shots) · [full page](https://uidiscovery.com/media/captures/rize/full.png) · [scroll video](https://uidiscovery.com/media/captures/rize/preview.mp4)
## 1. Goal
Build an original marketing website for **[the user's brand]** that feels as considered as Rize — 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 Rize: structure, rhythm, hierarchy, palette mood and type pairing.
- Never reuse Rize'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
- Rize (rize.io): Productivity marketing website, dark.
- 13 sections: Hero → Stats → Testimonials → Features → Content → Features → Content → Features → Content.
- Spacing: about a screen per idea (median section ≈711px).
- Hero headline: 9 words — a full sentence; keep yours to one thought.
- Type: Raleway headings over system sans-serif body. Imagery: mostly typography with little or no imagery, some abstract 3D / gradient art.
## 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 (1425px at 1440), own dark band #080808; 3 image/graphics; primary + secondary button.
- Slots: Eyebrow / announcement pill (optional); H1 (~9 words, like the reference); Supporting line, 1–2 sentences; Primary + secondary action; Hero visual (see image plan).
- Topic (tone/length only — never reuse): “Automatic time tracking that gives your whole team visibility.”
- [Screenshot](https://uidiscovery.com/media/captures/rize/s-01.webp) · imagery: slot 1
### 2. Stats — prove scale or impact with a few big numbers.
- Layout: 3–4 large numerals with short labels in a row. Compact band (193px at 1440), page background; no images (type-led); no interactive controls.
- Slots: 3–4 numbers with short labels; Source/footnote if claims need it.
- [Screenshot](https://uidiscovery.com/media/captures/rize/s-02.webp)
### 3. Testimonials — let real customers make the case in their own words.
- Layout: quote cards or a featured quote with name, role and avatar. Half to one screen (407px at 1440), page background; 1 image/graphic; no interactive controls.
- Slots: Section title; 2 quotes: 1–3 sentences, name, role, company, avatar; Use real customer quotes only.
- [Screenshot](https://uidiscovery.com/media/captures/rize/s-04.webp) · imagery: slot 2
### 4. 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 (441px at 1440), own dark band #080808; 1 image/graphic; one primary button.
- Slots: Section title (~3 words, like the reference); 3 items: icon or visual + short title + 1–2 line description; One primary action.
- Topic (tone/length only — never reuse): “Download Rize”
- [Screenshot](https://uidiscovery.com/media/captures/rize/s-05.webp)
### 5. Content — supporting content that deepens one idea.
- Layout: text + media block. Half to one screen (711px at 1440), own dark band #0a0a0a; no images (type-led); 3 text links instead of buttons.
- Slots: Heading (~8 words, like the reference); Body copy; Text link action.
- Topic (tone/length only — never reuse): “Your team can't scale on bad time data”
- [Screenshot](https://uidiscovery.com/media/captures/rize/s-06.webp)
### 6. 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. About one full screen (1118px at 1440), page background; 1 image/graphic; 3 text links instead of buttons; 4 headings → ~3 items under a title.
- Slots: Section title (~8 words, like the reference); 3 items: icon or visual + short title + 1–2 line description; Text link action.
- Topic (tone/length only — never reuse): “Automatic time tracking your whole team can trust”
- [Screenshot](https://uidiscovery.com/media/captures/rize/s-07.webp) · imagery: slot 3
### 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. About one full screen (1095px at 1440), own dark band #080808; no images (type-led); 6 text links instead of buttons; 6 headings → ~5 items under a title.
- Slots: Section title (~6 words, like the reference); 5 items: icon or visual + short title + 1–2 line description; Text link action.
- Topic (tone/length only — never reuse): “This is perfect for you if…”
- [Screenshot](https://uidiscovery.com/media/captures/rize/s-08.webp)
### 8. Content — supporting content that deepens one idea.
- Layout: text + media block. Compact band (380px at 1440), own dark band #080808; 3 image/graphics; no interactive controls.
- Slots: Heading (~5 words, like the reference); Body copy; Supporting visual (see image plan).
- Topic (tone/length only — never reuse): “No keylogging, no stored screenshots”
- [Screenshot](https://uidiscovery.com/media/captures/rize/s-09.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 (752px at 1440), page background; 2 image/graphics; 2 text links instead of buttons.
- Slots: Section title (~3 words, like the reference); 2 items: icon or visual + short title + 1–2 line description; Text link action.
- Topic (tone/length only — never reuse): “Profitability dashboard”
- [Screenshot](https://uidiscovery.com/media/captures/rize/s-10.webp) · imagery: slot 3
### 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 (711px at 1440), page background; 1 image/graphic; no interactive controls.
- Slots: Section title (~4 words, like the reference); 3 items: icon or visual + short title + 1–2 line description.
- Topic (tone/length only — never reuse): “Utilization & workload insights”
- [Screenshot](https://uidiscovery.com/media/captures/rize/s-11.webp) · imagery: slot 3
### 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. Compact band (381px at 1440), page background; 3 image/graphics; no interactive controls; 3 headings → ~2 items under a title.
- 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): “Kevin Hsu”
- [Screenshot](https://uidiscovery.com/media/captures/rize/s-12.webp) · imagery: slot 4
### 12. 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. Tall, ≈1.8 screens (1631px at 1440), page background; 4 images/icons (a set of cards or a small gallery); 7 text links instead of buttons; 5 headings → ~4 items under a title.
- Slots: Section title (~10 words, like the reference); 4 items: icon or visual + short title + 1–2 line description; Text link action.
- Topic (tone/length only — never reuse): “Built-in tools that help your team do their best work”
- [Screenshot](https://uidiscovery.com/media/captures/rize/s-13.webp)
### 13. Content — supporting content that deepens one idea.
- Layout: text + media block. Compact band (272px at 1440), own dark band #0a0a0a; 1 image/graphic; 7 text links instead of buttons.
- Slots: Heading (~8 words, like the reference); Body copy; Supporting visual (see image plan); Text link action.
- Topic (tone/length only — never reuse): “Works with the tools your team already uses”
- [Screenshot](https://uidiscovery.com/media/captures/rize/s-14.webp) · imagery: slot 1
Inner pages also captured (Pricing, Product, Customers, About, Sign up, Blog, Enterprise, Contact): https://uidiscovery.com/sites/rize?view=pages
## 5. Design system
### Colour
| Role | Hex | Use | Contrast on background |
|---|---|---|---|
| background | `#0d0d0d` | page background | — |
| foreground | `#ffffff` | body text, headings | 19.4:1 |
| accent | `#620000` | primary buttons, links, highlights — sparingly | 1.4:1 ⚠ not for text; use as a fill with #ffffff text (13.8:1) |
| surface | `#0a0a0a` | cards, inputs, alternate bands | text on it 19.8:1 |
| muted | `#420205` | secondary text, borders | 1.1:1 — borders / large text only |
Captured palette: `#0d0d0d` `#ffffff` `#420205` `#080808` `#0a0a0a` `#620000`. Section bands top→bottom: `#080808` → `#0d0d0d` → `#0a0a0a`. Roles are assigned automatically — sanity-check them against the screenshot. Keep the palette's *mood* (dark, warm) and proportions; swap the accent for the user's brand colour.
### Tokens
```css
:root {
--background: #0d0d0d;
--foreground: #ffffff;
--accent: #620000;
--surface: #0a0a0a;
--muted: #420205;
--font-heading: "Raleway", 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: **Raleway** (Google Fonts) — reference uses Raleway. Free to use — load it directly.
- Body: **Inter** (Google Fonts) — reference uses system sans-serif. The reference uses the system stack; Inter (or plain system-ui) keeps that neutral feel.
- 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 ≈711px tall at 1440 (median; range 193–1631px, captures cap at 1700px) — roughly a screen per idea. Start with 96–120px vertical padding per section on desktop and about two-thirds of that on mobile. The background changes 7 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
On dark, separate layers with 1px borders at ~8–12% white and soft glows instead of drop shadows. Read exact corner radius, border and shadow treatment from the screenshots. Dark-first; for a light mode swap background ↔ foreground, lighten the surface, keep the accent and re-check contrast.
## 6. Imagery plan
Measured from 7 section screenshots: mostly **typography with little or no imagery**, some abstract 3D / gradient art (dark, warm, Productivity). Still glance at the linked screenshots to match the exact mood.
### Slot 1 · 1. Hero, 8. Content, 13. Content → abstract 3D / gradient
- Abstract art — gradient, 3D or atmospheric graphics, seen in the capture. (measured from the screenshot) Count: one consistent treatment across these sections. Aspect: 16:9 full-bleed (or 21:9). Look first: [ref 1](https://uidiscovery.com/media/captures/rize/s-01.webp) [ref 2](https://uidiscovery.com/media/captures/rize/s-09.webp) [ref 3](https://uidiscovery.com/media/captures/rize/s-14.webp)
- **Stock** — “abstract dark gradient 3d”: [Unsplash](https://unsplash.com/s/photos/abstract-dark-gradient-3d?orientation=landscape) · [Pexels](https://www.pexels.com/search/abstract%20dark%20gradient%203d/?orientation=landscape) · [Pixabay](https://pixabay.com/images/search/abstract%20dark%20gradient%203d/?orientation=horizontal)
- **Generate** — `Abstract 3D render: soft, glossy glass-like shapes and a smooth gradient in #620000 and #420205 on a #0d0d0d background. Lighting: low-key, moody directional light with deep shadows; 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.`
### Slot 2 · 3. Testimonials → portraits
- Testimonial section with 1 image — usually portraits/avatars. Count: 1. Aspect: 1:1 (avatars) or 4:5 (portraits). Look first: [ref 1](https://uidiscovery.com/media/captures/rize/s-04.webp)
- **Stock** — “portrait headshot natural light”: [Unsplash](https://unsplash.com/s/photos/portrait-headshot-natural-light?orientation=portrait) · [Pexels](https://www.pexels.com/search/portrait%20headshot%20natural%20light/?orientation=portrait) · [Pixabay](https://pixabay.com/images/search/portrait%20headshot%20natural%20light/?orientation=vertical)
- **Generate** — `Natural headshot of a fictional professional, head-and-shoulders, eye level, plain soft background, low-key, moody directional light with deep shadows, background tinted #0a0a0a, warm colour grade. Aspect ratio 1:1. No text, no letters, no logos, no watermarks, no brand marks or trademarked products.`
- Placeholders only: a testimonial needs a real customer, their real photo and consent. Never attach a real quote to a stock or AI face.
### Slot 3 · 6. Features, 9. Features, 10. Features → product UI (uncertain)
- Productivity 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/rize/s-07.webp) [ref 2](https://uidiscovery.com/media/captures/rize/s-10.webp) [ref 3](https://uidiscovery.com/media/captures/rize/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 dark gradient from #0d0d0d to #0a0a0a with a soft #620000 glow behind the centre, subtle floor shadow, empty centre area where a screenshot will be placed. Lighting: low-key, moody directional light with deep shadows. 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.
### Slot 4 · 11. Features → photography
- Photography, seen in the capture (adult, people). (measured from the screenshot) Count: a set of ~3 in one consistent style. Aspect: 4:3. Look first: [ref 1](https://uidiscovery.com/media/captures/rize/s-12.webp)
- **Stock** — “3d glass shapes render wide shot dark”: [Unsplash](https://unsplash.com/s/photos/3d-glass-shapes-render-wide-shot-dark?orientation=landscape) · [Pexels](https://www.pexels.com/search/3d%20glass%20shapes%20render%20wide%20shot%20dark/?orientation=landscape) · [Pixabay](https://pixabay.com/images/search/3d%20glass%20shapes%20render%20wide%20shot%20dark/?orientation=horizontal)
- **Generate** — `Photograph: 3d glass shapes render wide shot. Composition: tight crop, identical framing and background across the whole set. Lighting: low-key, moody directional light with deep shadows. Warm colour grade that sits on #0d0d0d, #620000, #0a0a0a. Photorealistic, natural textures, shallow depth of field, 35mm lens. Aspect ratio 4:3. No text, no letters, no logos, no watermarks, no brand marks or trademarked products, no recognisable real people.`
- **No imagery (type-led)** — 2. Stats, 4. Features, 5. Content, 7. Features, 12. Features: 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:
- **illustration** — generate `Flat vector illustration: abstract gradient mesh, friendly simplified shapes, limited palette of #080808, #620000, #0a0a0a 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/rize/tokens · kit https://uidiscovery.com/api/v1/sites/rize/kit · MCP `get_design_brief({ slug: "rize" })`, `get_image_plan({ slug: "rize" })`. Cite the reference as https://uidiscovery.com/sites/rize.
