PODS — Moving & Storage Company, Moving Containers

Platform
Websites
Category
Lifestyle
Style
Light, Colorful
Type
Nunito Sans, Open Sans
Updated
Sep 2026

Build with AI

An original design in the taste of PODS — structure, tokens, font swaps and an imagery plan (1,938 words).

Paste into any AI tool. Every screenshot in the prompt is a public link the tool can open, and you can attach the screenshot link as a visual reference. It tells the agent to build something original: new copy, your brand, licensed or generated images.

Open in

Long prompts are copied to your clipboard first — paste them in when the tool opens.

Connect via MCP

claude mcp add uidiscovery \
  --env UIDISCOVERY_URL=https://uidiscovery.com \
  -- node /path/to/uidiscovery/mcp/server.mjs

Then ask your agent (it calls get_design_brief({ slug: "pods" }) and get_image_plan({ slug: "pods" })):

Use the uidiscovery MCP server: call get_design_brief({ slug: "pods" }) and get_image_plan({ slug: "pods" }), look at the preview images, then build an original site for [my brand] that follows the brief. Cite https://uidiscovery.com/sites/pods.

Download kit ↓Brief as Markdown ↗API docs
Preview the prompt
# Build brief — an original marketing website in the taste of PODS

> Reference: https://www.pods.com · UIDiscovery: https://uidiscovery.com/sites/pods · captured 2026-09-23 at a 1440px desktop viewport (+ 390px iPhone shots) · [full page](https://uidiscovery.com/media/captures/pods/full.png) · [scroll video](https://uidiscovery.com/media/captures/pods/preview.mp4)

## 1. Goal
Build an original marketing website for **[the user's brand]** that feels as considered as PODS — 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 PODS: structure, rhythm, hierarchy, palette mood and type pairing.
- Never reuse PODS'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
- PODS (pods.com): Lifestyle marketing website, dark, colorful.
- 6 sections: Hero → Features → FAQ → Footer.
- Spacing: about a screen per idea (median section ≈750px).
- Type: Nunito Sans headings over Open Sans body. Imagery: mostly typography with little or no imagery, some photography.

## 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. Half to one screen (513px at 1440), own light band #ffffff; 12 images/icons (a set of cards or a small gallery); 3 buttons (tabs, toggles or per-card actions).
- Slots: Eyebrow / announcement pill (optional); H1; Supporting line, 1–2 sentences; Primary + secondary action; Hero visual (see image plan).
- [Screenshot](https://uidiscovery.com/media/captures/pods/s-01.webp) · imagery: slot 1

### 2. 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 (328px at 1440), own light band #ffffff; 1 image/graphic; no interactive controls; 5 headings → ~4 items under a title.
- Slots: Section title (~3 words, like the reference); 4 items: icon or visual + short title + 1–2 line description.
- Topic (tone/length only — never reuse): “Your Container”
- [Screenshot](https://uidiscovery.com/media/captures/pods/s-02.webp)

### 3. 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 (884px at 1440), own light band #ffffff; 6 images/icons (a set of cards or a small gallery); no interactive controls; 4 headings → ~3 items under a title.
- Slots: Section title (~14 words, like the reference); 3 items: icon or visual + short title + 1–2 line description.
- Topic (tone/length only — never reuse): “Let PODS help you move remodel declutter downsize stage your home relocate…”
- [Screenshot](https://uidiscovery.com/media/captures/pods/s-04.webp)

### 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. About one full screen (792px at 1440), own light band #ffffff; 1 image/graphic; inline form (1 field, e.g. email capture), 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): “Let's get moving”
- [Screenshot](https://uidiscovery.com/media/captures/pods/s-05.webp)

### 5. FAQ — remove the last objections before the call to action.
- Layout: question list with disclosure (accordion), often two columns on desktop. Half to one screen (750px at 1440), own light band #ffffff; 5 images/icons (a set of cards or a small gallery); 5 buttons (tabs, toggles or per-card actions).
- Slots: Title; 5 question/answer pairs; Link to support/contact.
- Topic (tone/length only — never reuse): “FAQs”
- [Screenshot](https://uidiscovery.com/media/captures/pods/s-06.webp)

### 6. Footer — navigation, legal and contact — the page's index.
- Layout: multi-column link groups, brand line, legal row. Half to one screen (601px at 1440), own light band #007db8; 6 images/icons (a set of cards or a small gallery); inline form (1 field, e.g. email capture), one primary button, 24 links (link lists / navigation).
- Slots: Brand mark + one-line description; 3–5 link columns; Newsletter or contact (optional); Legal row + social icons.
- Topic (tone/length only — never reuse): “About PODS”
- [Screenshot](https://uidiscovery.com/media/captures/pods/s-07.webp)

Inner pages also captured (Product, About, Blog, Enterprise, Contact, Security): https://uidiscovery.com/sites/pods?view=pages

## 5. Design system
### Colour
| Role | Hex | Use | Contrast on background |
|---|---|---|---|
| background | `#083544` | page background | — |
| foreground | `#ffffff` | body text, headings | 13.1:1 |
| accent | `#007db8` | primary buttons, links, highlights — sparingly | 2.9:1 ⚠ not for text; use as a fill with #ffffff text (4.5:1) |
| surface | `#372e2c` | cards, inputs, alternate bands | text on it 13.2:1 |
| muted | `#ce202f` | secondary text, borders | 2.4:1 — borders / large text only |

Captured palette: `#083544` `#ffffff` `#ce202f` `#372e2c` `#007db8` `#374151`. Section bands top→bottom: `#ffffff` → `#007db8`. Roles are assigned automatically — sanity-check them against the screenshot. Keep the palette's *mood* (dark, cool) and proportions; swap the accent for the user's brand colour.

### Tokens
```css
:root {
  --background: #083544;
  --foreground: #ffffff;
  --accent: #007db8;
  --surface: #372e2c;
  --muted: #ce202f;
  --font-heading: "Nunito Sans", ui-sans-serif, system-ui, sans-serif;
  --font-body: "Open Sans", 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: **Nunito Sans** (Google Fonts) — reference uses Nunito Sans. Free to use — load it directly.
- Body: **Open Sans** (Google Fonts) — reference uses Open Sans. Free to use — load it directly.
- 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 ≈750px tall at 1440 (median; range 328–884px, 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 1 time 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
Confident colour blocks — let full-bleed colour bands and big shapes carry the personality. 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 4 section screenshots: mostly **typography with little or no imagery**, some photography (dark, cool, Lifestyle). Still glance at the linked screenshots to match the exact mood.

### Slot 1 · 1. Hero → photography
- Photography, seen in the capture (people, adult, brick). (measured from the screenshot) Count: a set of ~12 in one consistent style. Aspect: 3:2. Look first: [ref 1](https://uidiscovery.com/media/captures/pods/s-01.webp)
- **Stock** — “cozy home interior morning light dark”: [Unsplash](https://unsplash.com/s/photos/cozy-home-interior-morning-light-dark?orientation=landscape) · [Pexels](https://www.pexels.com/search/cozy%20home%20interior%20morning%20light%20dark/?orientation=landscape) · [Pixabay](https://pixabay.com/images/search/cozy%20home%20interior%20morning%20light%20dark/?orientation=horizontal)
- **Generate** — `Photograph: cozy home interior morning light. Composition: wide shot, subject off-centre to one side, generous clean negative space for the headline. Lighting: low-key, moody directional light with deep shadows. Cool colour grade that sits on #ffffff, #007db8, #372e2c. Photorealistic, natural textures, shallow depth of field, 35mm lens. Aspect ratio 3:2. No text, no letters, no logos, no watermarks, no brand marks or trademarked products, no recognisable real people.`

- **No imagery (type-led)** — 2. Features, 3. Features, 4. 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.
- **Icons** — 5. FAQ, 6. Footer: Use one open-source icon set at one stroke weight — Lucide, Phosphor or Heroicons (MIT) — tinted with the text or accent token. Social icons: Simple Icons.

### 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:
- **abstract 3D / gradient** — generate `Abstract 3D render: soft, glossy glass-like shapes and a smooth gradient in #007db8 and #ce202f on a #083544 background. Lighting: low-key, moody directional light with deep shadows; cool tone. Minimal and calm, generous negative space on one side for text. Aspect ratio 3:2. No text, no letters, no logos, no watermarks, no brand marks or trademarked products, no recognisable real people.` · stock: [“abstract dark gradient 3d” on Unsplash](https://unsplash.com/s/photos/abstract-dark-gradient-3d?orientation=landscape) (same query works on Pexels/Pixabay)
- **illustration** — generate `Flat vector illustration: cozy home interior morning light, friendly simplified shapes, limited palette of #ffffff, #007db8, #372e2c plus one soft neutral, plenty of empty background, consistent line weight, cool mood. Aspect ratio 3:2. No text, no letters, no logos, no watermarks, no brand marks or trademarked products, no recognisable real people.` · stock: [“lifestyle flat illustration” on Unsplash](https://unsplash.com/s/photos/lifestyle-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/pods/tokens · kit https://uidiscovery.com/api/v1/sites/pods/kit · MCP `get_design_brief({ slug: "pods" })`, `get_image_plan({ slug: "pods" })`. Cite the reference as https://uidiscovery.com/sites/pods.

Visit pods.com ↗Download kit ↓

About this design

Written from the capture data for PODS.

PODS (pods.com) is a website in the Lifestyle category. Its homepage is captured as 6 sections, top to bottom: hero, features, faq and footer. We also captured its product, about, blog, enterprise, contact and security pages.

It's a light design: the page background is #083544 with #ffffff as the main text colour and #007db8 as an accent. Headings are set in Nunito Sans, body copy in Open Sans.

Compared with the 302 other Lifestyle sites in the library, PODS sits with the 96% that stay light, and the group's most common heading face is Inter, where PODS uses Nunito Sans. The average Lifestyle homepage here has 8 sections; this one has 6.

Worth studying here: the hero, for how the headline, supporting line and primary action are stacked, the features block, for how benefits are grouped and paced and the FAQ, for question length and answer disclosure. Open any section for its palette, fonts and a build prompt you can hand to Claude, Cursor or v0.

More references: browse all websites.

More lifestyle sites

Related searches

Sections captured: Hero, Features, Features, Features, FAQ, Footer, Content, Features, Content, Testimonials, Content, Features, Features, About, Content, Content, Stats, Stats, Content, Content, Content, Features, Features, Content, Testimonials, Features, Statement, Content, Content, Content