Justin Welsh

Personal CreatorVisit sitejustinwelsh.me

A calm, type-led personal publication makes one recurring email the primary offer.

Justin Welsh — captured interface — Page capture · scroll inside to explore

Source capture · 2026-09-05Open full image ↗

Why this pattern works

Explaining the newsletter’s topic and cadence before a simple subscription form, then adding endorsements, a free guide, and sample essays. Selection is based on observable design and conversion paths; conversion rates have not been independently verified.

Design notes

Mood: Editorial Newsletter Brand. A calm, type-led personal publication makes one recurring email the primary offer.
Colors: Warm off-white, charcoal, and muted gray.
Type: Editorial serif headlines paired with quiet sans-serif interface text.
Layout: Narrow centered hero, inline form, short proof statements, then a guide and essay index.
Motion: Keep navigation and reading immediate; motion should support the work rather than delay access.
Texture: Fine rules and generous whitespace create a publication feel.
Imagery: A small portrait and a genuine guide cover are sufficient; let the writing carry the page.
Don't: Do not add visual noise around the form or substitute vague inspiration for a specific email promise.

Make it your own

Turn this reference into a useful brief for your project. Copy it into the AI tool you already use.

Your project

Use withI want to

Tech stack

Add constraints

What should the tool respect?

Preview & edit prompt

Prompt text

# My project
[Describe the product, audience, and screen you want to improve]

Stack: Use the existing project stack
Task: Implement the interface and verify the result in the existing project.

## Tool guidance (Any AI tool)
Use available project tools to inspect, implement, and test. State any unavailable capabilities.

# Design reference: Justin Welsh
Source: https://justinwelsh.me/
Swipefile reference: https://swipefile.design/ref/personal-justin-welsh/
Captured: 2026-09-05. This is a dated reference, not a claim about the current live product.

## Objective
Adapt the visual principles below to my project. Use my own content and identity. Do not reproduce logos, proprietary copy, or brand assets.

## Reference notes
- mood: Editorial Newsletter Brand. A calm, type-led personal publication makes one recurring email the primary offer.
- colors: Warm off-white, charcoal, and muted gray.
- typography: Editorial serif headlines paired with quiet sans-serif interface text.
- layout: Narrow centered hero, inline form, short proof statements, then a guide and essay index.
- motion: Keep navigation and reading immediate; motion should support the work rather than delay access.
- texture: Fine rules and generous whitespace create a publication feel.
- dont: Do not add visual noise around the form or substitute vague inspiration for a specific email promise.

Useful for: Explaining the newsletter’s topic and cadence before a simple subscription form, then adding endorsements, a free guide, and sample essays. Selection is based on observable design and conversion paths; conversion rates have not been independently verified.

## Acceptance criteria
- Existing project conventions, design tokens, working functionality, and unrelated changes are preserved.
- Two or three reference principles clearly support the user's task; conflicts are resolved in favor of usability and the existing product.
- Reusable components and semantic HTML express the interface. Available licensed assets are used; important UI text is never rendered as a bitmap.
- Every visible control has a defined behavior. Loading, empty, error, success, disabled, and long-content states are specified where relevant. Demo data is clearly labeled.
- Navigation and content adapt at 375px, 768px, and 1440px without horizontal page overflow. Keyboard use, visible focus, labeled inputs, at least 44px touch targets, readable contrast, and reduced motion are supported.
- Verification distinguishes rendered behavior from proposals and identifies anything still requiring a backend or external service.

## Quality bar
Clear hierarchy, consistent spacing, restrained surfaces, and purposeful motion. Avoid decorative gradients, excessive cards, placeholder buttons, and invented metrics unless the project calls for them. Do not claim a feature is connected or tested without evidence.

Assembled in your browser. No API key or AI request needed. Changing the fields refreshes the preview.

## Objective
Adapt the visual principles below to my project. Use my own content and identity. Do not reproduce logos, proprietary copy, or brand assets.

Justin Welsh

Make it your own

Keep exploring