Mark Manson

An email-first author site makes the newsletter tangible through phone previews and direct benefit copy.

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

Why this pattern works

Reducing uncertainty about subscribing by showing the reading format and placing the form beside it. Biography and content routes give visitors ways to evaluate the author first. Selection is based on observable design and conversion paths; conversion rates have not been independently verified.

Design notes

Mood: Author Newsletter Hub. An email-first author site makes the newsletter tangible through phone previews and direct benefit copy.
Colors: Pale blue-gray, white, black, and restrained warm highlights.
Type: Heavy sans-serif headings with approachable body copy.
Layout: Newsletter hero with phone mockups and signup, followed by biography and article, podcast, and video pathways.
Motion: Keep navigation and reading immediate; motion should support the work rather than delay access.
Texture: Product-like phone previews and a candid cutout portrait.
Imagery: Show your real newsletter in device previews and use an authentic portrait.
Don't: Do not copy audience or outcome claims; use only evidence belonging to your own publication.

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: Mark Manson
Source: https://markmanson.net/
Swipefile reference: https://swipefile.design/ref/personal-mark-manson/
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: Author Newsletter Hub. An email-first author site makes the newsletter tangible through phone previews and direct benefit copy.
- colors: Pale blue-gray, white, black, and restrained warm highlights.
- typography: Heavy sans-serif headings with approachable body copy.
- layout: Newsletter hero with phone mockups and signup, followed by biography and article, podcast, and video pathways.
- motion: Keep navigation and reading immediate; motion should support the work rather than delay access.
- texture: Product-like phone previews and a candid cutout portrait.
- dont: Do not copy audience or outcome claims; use only evidence belonging to your own publication.

Useful for: Reducing uncertainty about subscribing by showing the reading format and placing the form beside it. Biography and content routes give visitors ways to evaluate the author first. 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.

Mark Manson

Make it your own

Keep exploring