Ship 30 for 30 — Writing Course

Course Sales PageVisit siteship30for30.com

A long course offer that explains the writing program, teaches its method, introduces the instructors, and builds toward enrollment with curriculum and student proof.

Ship 30 for 30 — Writing Course — captured interface — Full page · scroll inside to explore

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

Landing pages & funnels Long-form sales pages

Why this pattern works

Study the complete public landing page and its section order. This is one sales page, not a captured multi-step checkout or verified conversion result.

Design notes

Mood: Encouraging, educational, and personal.
Colors: Deep ink-blue backgrounds, white text and content panels, and pink-to-orange enrollment accents.
Type: Large expressive headings paired with comfortable paragraph widths and scannable benefit lists.
Layout: Course promise and enrollment action → reasons to write online → teaching method and curriculum → student examples and proof → instructor context → offer and closing questions. The reference covers the public sales page only.
Motion: The screenshot records a static state. Preserve readable scrolling and clear CTA feedback; do not infer video playback or hidden form behavior.
Texture: Writing examples, hand-drawn circles, colorful notes, instructor imagery, and student testimonials.
Don't: Use your own offer, brand, and assets. Do not invent testimonials, results, scarcity, guarantees, or pricing.

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: Ship 30 for 30 — Writing Course
Source: https://www.ship30for30.com/
Swipefile reference: https://swipefile.design/ref/funnel-ship30/
Captured: 2026-09-07. 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: Encouraging, educational, and personal.
- colors: Deep ink-blue backgrounds, white text and content panels, and pink-to-orange enrollment accents.
- typography: Large expressive headings paired with comfortable paragraph widths and scannable benefit lists.
- layout: Course promise and enrollment action → reasons to write online → teaching method and curriculum → student examples and proof → instructor context → offer and closing questions. The reference covers the public sales page only.
- motion: The screenshot records a static state. Preserve readable scrolling and clear CTA feedback; do not infer video playback or hidden form behavior.
- texture: Writing examples, hand-drawn circles, colorful notes, instructor imagery, and student testimonials.
- dont: Use your own offer, brand, and assets. Do not invent testimonials, results, scarcity, guarantees, or pricing.

Useful for: Study the complete public landing page and its section order. This is one sales page, not a captured multi-step checkout or verified conversion result.

## 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.

Useful for: Study the complete public landing page and its section order. This is one sales page, not a captured multi-step checkout or verified conversion result.

Ship 30 for 30 — Writing Course

Make it your own

Keep exploring