@thedotmack's Landing Page & Marketing Design System
This skill encodes the design philosophy, UX patterns, copywriting voice, and conversion strategies @thedotmack has developed across dozens of successful landing pages. These aren't theoretical principles; they're patterns extracted from what actually shipped and worked.
Core Design Philosophy
Simplicity Is The Strategy
Every design decision runs through KISS, DRY, and YAGNI. If a section doesn't earn its place on the page, it gets cut. If an animation doesn't serve comprehension or conversion, it goes. The goal is clarity, not decoration.
- Simple solutions first, always
- If you're reaching for complexity, stop and ask: "Could this be simpler?"
- Delete before you add. The best fix for a cluttered page is removing things.
- Build working prototypes, not theoretical wireframes
Foundational References
This design system is built on two key texts that should be internalized, not just referenced:
Steve Krug's "Don't Make Me Think":
- Every page should be self-evident. If a user has to think about how to navigate, you've failed.
- Reduce noise and visual clutter ruthlessly
- Conventions are your friend — don't reinvent navigation, form patterns, or CTAs
- Test with real people, observe where they struggle, fix those things
Adam Wathan & Steve Schoger's "Refactoring UI":
- Hierarchy through weight AND color, not just size
- Labels as a last resort — if the content is clear, the label is noise
- Systematic spacing on an 8px grid, not arbitrary values
- Typography creates hierarchy — use weight, size, color, and opacity together
- Start with too much white space, then selectively reduce
- Don't force elements to fill available space unless they need to
Page Architecture
The Scroll Narrative
Landing pages tell stories. They don't dump features — they take the visitor on a journey from problem awareness to purchase decision. The structure follows a consistent emotional arc:
1. Hero → Grab attention, state the core promise
2. Problem → Name the pain the visitor already feels
3. Solution → Show how you solve it (not features—transformation)
4. Proof → Social proof, numbers, case studies
5. How It Works → Simple 3-step process
6. Pricing/CTA → Clear options, risk reversal
7. FAQ → Handle objections
8. Final CTA → One last push
This isn't rigid — some pages compress or expand sections. But the emotional arc remains consistent.
Section-Level Patterns
Hero Section:
- One clear value proposition, not three competing messages
- Use "your" not "a" — "Build your ___" not "Build a ___"
- Benefits-oriented subhead (what changes for them), not feature-oriented
- Primary CTA + secondary CTA (never more than two)
- Social proof badges or stats strip below the fold line
- Generous spacing — let the message breathe
Problem Section:
- Name the specific pain point the audience already knows
- Use their language, not marketing speak
- Short, punchy sentences that build tension
- "Here's the trap:" or "But here's the problem:" as a pivot
- The visitor should be nodding before you present the solution
Solution Section:
- Lead with transformation, not mechanism
- Before/After framing works extremely well
- "What people actually want: [simple truth]"
- Show the contrast between old way and new way
- Keep it visceral and relatable
Social Proof Section:
- Quantified results over generic testimonials ("840% lead increase" not "great service")
- Specific numbers: dollar amounts, percentages, timeframes
- Real names, real photos, real titles
- Multiple testimonials addressing different concerns
- Case study cards with before/after metrics
Process Section:
- Maximum 3 steps
- Each step gets a clear label, brief description, and visual icon
- Numbered with large, visible step indicators
- This section exists to make the complex feel simple
Pricing Section:
- 2-3 tiers maximum, one marked as "Popular" or "Recommended"
- Show the value clearly — what's included at each level
- Risk reversal (money-back guarantee, satisfaction promise)
- "Starting at $X" is better than hiding price entirely
- Subscription framing reduces perceived cost vs. one-time
FAQ Section:
- Address real objections, not softballs
- Expandable accordion format
- 6-8 questions maximum
- Write answers that sell, not just inform
Footer CTA:
- Restate the core promise in different words
- "Not sure if [Product] is right for you? Let's chat."
- One final clear action button
Visual Hierarchy Rules
Typography System
Use distinct display/body font pairings. Typography does heavy lifting for hierarchy:
- Headlines: Large, distinctive display font. Serif italic for editorial feel, bold geometric sans for tech products.
- Body: Clean, readable sans-serif or monospace depending on context.
- UI/Labels: Monospace, small, uppercase with wide letter-spacing, low opacity.
- Stats/Numbers: Extra large, bold, high contrast. Numbers should punch.
Hierarchy through layered opacity (especially on dark backgrounds):
Primary text: white/90 or text-white
Secondary text: white/60 or text-gray-300
Tertiary text: white/40 or text-gray-500
Labels/meta: white/30 with tracking-[0.2em] uppercase
Spacing & Layout
- 8px grid system, always
- Generous padding inside sections (py-20 to py-32)
- Max content width of 4xl to 6xl for readability
- Text line length: 45-75 characters (max-w-xl to max-w-2xl for paragraphs)
- Section separators: subtle borders (border-white/[0.05]) or spacing, not heavy dividers
- Mobile-first: everything must work on phones before desktop polish
Color Approach
- Dark base: Near-black tones (#0a0a0c, slate-900, gray-950), not pure black
- Text on dark: White with varying opacity levels (see hierarchy above)
- Accent colors: One strong accent per project, used sparingly. Never more than 2-3 total.
- Semantic color usage:
- Red = critical/error/danger
- Yellow = warning/caution
- Blue = information
- Green = success/positive
- Purple = discovery/insight
- Gradients: Subtle and purposeful. Gradient borders and accent glows work better than gradient backgrounds.
- For light themes: Natural palettes (beige, olive, earth tones) over sterile whites.
Animation & Motion
- Purposeful, never decorative — if it distracts, remove it
- 150-300ms for micro-interactions
- Ease-out for entrances
- Scroll-driven reveals for hero sequences
- Subtle hover states: 5-10% darken or background shift, not dramatic transforms
- Loading skeletons over spinners
- One orchestrated page-load animation beats scattered micro-interactions
- If scroll transitions break the page, remove them — function over flair
Marketing Copy & Messaging
Voice Principles
Copy should be direct, personal, and conversational.
Do:
- Second person ("your", "you") — always address the reader directly
- Short sentences for impact. Longer ones for explanation.
- Confident without being arrogant
- Specific over vague ("840% lead increase" not "dramatically more leads")
- Honest about limitations
Don't:
- Generic language ("We leverage cutting-edge solutions")
- Passive voice ("Websites are built by our team")
- Buzzwords ("Synergize your digital transformation")
- Overpolished corporate tone — some roughness is authentic
Copy Patterns
Hero Headlines:
- "[Verb] your [thing] [benefit clause]"
- Examples: "Build your fitness empire without the complexity or compromise", "Never miss another token launch", "Imagine what's possible when AI remembers everything"
Subheads:
- State the specific benefit or transformation
- Address one key anxiety: "No contracts, no BS, just results."
Problem Statements:
- Use "Here's the trap:" or "But here's the problem:" as pivots
- Name the pain directly in the audience's own language
CTAs:
- Primary: Action-oriented verb + clear outcome ("Book a Free Strategy Call", "View on GitHub", "Get Started")
- Secondary: Lower commitment ("See Client Results", "Learn More")
- Never more than 2 CTAs visible at once
- Repeat the primary CTA at multiple scroll points (minimum: hero, mid-page, footer)
Benefits Over Features
Every section should answer "so what?" from the visitor's perspective.
| Feature (Don't Lead With) |
Benefit (Lead With) |
| Three-layer architecture |
Your AI remembers everything about you |
| Responsive development |
Your website looks perfect on every device |
| 2.9% fee structure |
Keep more of what you earn |
| Observer/note-taker pattern |
One agent watches, learns, and remembers |
Social Proof Copy
- Specific numbers always: "$45k MRR", "840% increase", "20x ROI in year 1"
- Attribution: Real name, role, company. With photo when possible.
- Pull quotes that mention specific outcomes, not generic praise
- Case study cards: business type badge, headline result, specific metrics, brief quote
Conversion Optimization
CTA Strategy
- Sticky nav with persistent CTA button on long pages
- Multiple CTA placements: hero, after social proof, after pricing, footer
- Single primary action per page — don't split attention
- Risk reversal near pricing: "30-day money-back guarantee", "If you're not stoked, request a refund"
- Scheduling integration (Calendly, SavvyCal) for "Book a call" CTAs — reduce friction
Information Architecture for Conversion
Awareness → Hero + Problem (they realize they have the pain)
Interest → Solution + Social Proof (they see you can solve it)
Desire → Process + Pricing (they understand the path and cost)
Action → CTA + FAQ + Risk Reversal (they have no reason not to)
Objection Handling
The FAQ section is a conversion tool, not an afterthought:
- "Is this right for me?" → Qualify the audience clearly
- "How long does it take?" → Set clear timelines
- "What if it doesn't work?" → Guarantee or risk reversal
- "How is this different from [competitor/DIY]?" → Specific differentiators
- "Can I talk to someone first?" → Low-friction contact option
Responsive Design
Breakpoint Rules
- Mobile-first, always. Design for phones, then expand.
- Tailwind breakpoints: Use
sm:, md:, lg: systematically
- Touch targets: Minimum 44px × 44px, preferably 48px
- Mobile text: 16px minimum body text (prevents iOS zoom)
- Stack vertically on mobile: Horizontal layouts become vertical
- Hide non-essential elements on mobile rather than cramming
- Test at real device widths, not just "make the browser narrow"
Common Responsive Patterns
Hero: Full-width, reduced padding on mobile, stacked CTAs
Nav: Hamburger on mobile with full-screen overlay
Grid cards: 3-col desktop → 2-col tablet → 1-col mobile
Stats strip: Horizontal row → stacked or 2×2 grid
Pricing: Side-by-side → stacked with swipe
Testimonials: Carousel on mobile, grid on desktop
Project-Type Reference
Aesthetic direction varies by product category:
Developer/Technical Products
- Dark theme
- Monospace for UI elements
- Serif italic for editorial headlines
- Subtle noise texture and scanlines
- Numbered, uppercase, wide-tracked section labels
- Stats displayed prominently with large bold numbers
Consumer/Lifestyle Products
- Light or dark depending on brand
- Warmer palettes: beige, olive, earth tones, soft blues
- Elegant serif headlines, clean sans body text
- More photography, less illustration
- Approachable, warm copy tone
DeFi/Trading Products
- Dark theme
- Animated elements: live data, notification banners, real-time updates
- Neon accents (green for gains, red for losses)
- Glassmorphism cards with backdrop blur
- Wallet connection as first-class UI element
- "How it works" must be dead simple — 3 steps max
- Trust signals: audit badges, lock icons, transparency
Agency/Services
- Professional but not boring
- Split hero: copy left, social proof/image right
- Methodology section with numbered phases
- Real client testimonials with photos and metrics
- Tiered pricing with "Popular" indicator
- "Book a call" as primary CTA throughout
Implementation Checklist
Before shipping any landing page:
Visual
Copy
UX
Conversion
1---2name: ux-designer3description: @thedotmack's Landing Page & Marketing Design System4---56# @thedotmack's Landing Page & Marketing Design System78This skill encodes the design philosophy, UX patterns, copywriting voice, and conversion strategies @thedotmack has developed across dozens of successful landing pages. These aren't theoretical principles; they're patterns extracted from what actually shipped and worked.910---1112## Core Design Philosophy1314### Simplicity Is The Strategy1516Every design decision runs through KISS, DRY, and YAGNI. If a section doesn't earn its place on the page, it gets cut. If an animation doesn't serve comprehension or conversion, it goes. The goal is clarity, not decoration.1718- Simple solutions first, always19- If you're reaching for complexity, stop and ask: "Could this be simpler?"20- Delete before you add. The best fix for a cluttered page is removing things.21- Build working prototypes, not theoretical wireframes2223### Foundational References2425This design system is built on two key texts that should be internalized, not just referenced:2627**Steve Krug's "Don't Make Me Think":**28- Every page should be self-evident. If a user has to think about how to navigate, you've failed.29- Reduce noise and visual clutter ruthlessly30- Conventions are your friend — don't reinvent navigation, form patterns, or CTAs31- Test with real people, observe where they struggle, fix those things3233**Adam Wathan & Steve Schoger's "Refactoring UI":**34- Hierarchy through weight AND color, not just size35- Labels as a last resort — if the content is clear, the label is noise36- Systematic spacing on an 8px grid, not arbitrary values37- Typography creates hierarchy — use weight, size, color, and opacity together38- Start with too much white space, then selectively reduce39- Don't force elements to fill available space unless they need to4041---4243## Page Architecture4445### The Scroll Narrative4647Landing pages tell stories. They don't dump features — they take the visitor on a journey from problem awareness to purchase decision. The structure follows a consistent emotional arc:4849```501. Hero → Grab attention, state the core promise512. Problem → Name the pain the visitor already feels523. Solution → Show how you solve it (not features—transformation)534. Proof → Social proof, numbers, case studies545. How It Works → Simple 3-step process556. Pricing/CTA → Clear options, risk reversal567. FAQ → Handle objections578. Final CTA → One last push58```5960This isn't rigid — some pages compress or expand sections. But the emotional arc remains consistent.6162### Section-Level Patterns6364**Hero Section:**65- One clear value proposition, not three competing messages66- Use "your" not "a" — "Build **your** ___" not "Build a ___"67- Benefits-oriented subhead (what changes for them), not feature-oriented68- Primary CTA + secondary CTA (never more than two)69- Social proof badges or stats strip below the fold line70- Generous spacing — let the message breathe7172**Problem Section:**73- Name the specific pain point the audience already knows74- Use their language, not marketing speak75- Short, punchy sentences that build tension76- "Here's the trap:" or "But here's the problem:" as a pivot77- The visitor should be nodding before you present the solution7879**Solution Section:**80- Lead with transformation, not mechanism81- Before/After framing works extremely well82- "What people actually want: [simple truth]"83- Show the contrast between old way and new way84- Keep it visceral and relatable8586**Social Proof Section:**87- Quantified results over generic testimonials ("840% lead increase" not "great service")88- Specific numbers: dollar amounts, percentages, timeframes89- Real names, real photos, real titles90- Multiple testimonials addressing different concerns91- Case study cards with before/after metrics9293**Process Section:**94- Maximum 3 steps95- Each step gets a clear label, brief description, and visual icon96- Numbered with large, visible step indicators97- This section exists to make the complex feel simple9899**Pricing Section:**100- 2-3 tiers maximum, one marked as "Popular" or "Recommended"101- Show the value clearly — what's included at each level102- Risk reversal (money-back guarantee, satisfaction promise)103- "Starting at $X" is better than hiding price entirely104- Subscription framing reduces perceived cost vs. one-time105106**FAQ Section:**107- Address real objections, not softballs108- Expandable accordion format109- 6-8 questions maximum110- Write answers that sell, not just inform111112**Footer CTA:**113- Restate the core promise in different words114- "Not sure if [Product] is right for you? Let's chat."115- One final clear action button116117---118119## Visual Hierarchy Rules120121### Typography System122123Use distinct display/body font pairings. Typography does heavy lifting for hierarchy:124125- **Headlines**: Large, distinctive display font. Serif italic for editorial feel, bold geometric sans for tech products.126- **Body**: Clean, readable sans-serif or monospace depending on context.127- **UI/Labels**: Monospace, small, uppercase with wide letter-spacing, low opacity.128- **Stats/Numbers**: Extra large, bold, high contrast. Numbers should punch.129130**Hierarchy through layered opacity (especially on dark backgrounds):**131```132Primary text: white/90 or text-white133Secondary text: white/60 or text-gray-300134Tertiary text: white/40 or text-gray-500135Labels/meta: white/30 with tracking-[0.2em] uppercase136```137138### Spacing & Layout139140- 8px grid system, always141- Generous padding inside sections (py-20 to py-32)142- Max content width of 4xl to 6xl for readability143- Text line length: 45-75 characters (max-w-xl to max-w-2xl for paragraphs)144- Section separators: subtle borders (border-white/[0.05]) or spacing, not heavy dividers145- Mobile-first: everything must work on phones before desktop polish146147### Color Approach148149- **Dark base**: Near-black tones (#0a0a0c, slate-900, gray-950), not pure black150- **Text on dark**: White with varying opacity levels (see hierarchy above)151- **Accent colors**: One strong accent per project, used sparingly. Never more than 2-3 total.152- **Semantic color usage:**153 - Red = critical/error/danger154 - Yellow = warning/caution155 - Blue = information156 - Green = success/positive157 - Purple = discovery/insight158- **Gradients**: Subtle and purposeful. Gradient borders and accent glows work better than gradient backgrounds.159- **For light themes**: Natural palettes (beige, olive, earth tones) over sterile whites.160161### Animation & Motion162163- Purposeful, never decorative — if it distracts, remove it164- 150-300ms for micro-interactions165- Ease-out for entrances166- Scroll-driven reveals for hero sequences167- Subtle hover states: 5-10% darken or background shift, not dramatic transforms168- Loading skeletons over spinners169- One orchestrated page-load animation beats scattered micro-interactions170- If scroll transitions break the page, remove them — function over flair171172---173174## Marketing Copy & Messaging175176### Voice Principles177178Copy should be direct, personal, and conversational.179180**Do:**181- Second person ("your", "you") — always address the reader directly182- Short sentences for impact. Longer ones for explanation.183- Confident without being arrogant184- Specific over vague ("840% lead increase" not "dramatically more leads")185- Honest about limitations186187**Don't:**188- Generic language ("We leverage cutting-edge solutions")189- Passive voice ("Websites are built by our team")190- Buzzwords ("Synergize your digital transformation")191- Overpolished corporate tone — some roughness is authentic192193### Copy Patterns194195**Hero Headlines:**196- "[Verb] your [thing] [benefit clause]"197- Examples: "Build your fitness empire without the complexity or compromise", "Never miss another token launch", "Imagine what's possible when AI remembers everything"198199**Subheads:**200- State the specific benefit or transformation201- Address one key anxiety: "No contracts, no BS, just results."202203**Problem Statements:**204- Use "Here's the trap:" or "But here's the problem:" as pivots205- Name the pain directly in the audience's own language206207**CTAs:**208- Primary: Action-oriented verb + clear outcome ("Book a Free Strategy Call", "View on GitHub", "Get Started")209- Secondary: Lower commitment ("See Client Results", "Learn More")210- Never more than 2 CTAs visible at once211- Repeat the primary CTA at multiple scroll points (minimum: hero, mid-page, footer)212213### Benefits Over Features214215Every section should answer "so what?" from the visitor's perspective.216217| Feature (Don't Lead With) | Benefit (Lead With) |218|---|---|219| Three-layer architecture | Your AI remembers everything about you |220| Responsive development | Your website looks perfect on every device |221| 2.9% fee structure | Keep more of what you earn |222| Observer/note-taker pattern | One agent watches, learns, and remembers |223224### Social Proof Copy225226- Specific numbers always: "$45k MRR", "840% increase", "20x ROI in year 1"227- Attribution: Real name, role, company. With photo when possible.228- Pull quotes that mention specific outcomes, not generic praise229- Case study cards: business type badge, headline result, specific metrics, brief quote230231---232233## Conversion Optimization234235### CTA Strategy236237- Sticky nav with persistent CTA button on long pages238- Multiple CTA placements: hero, after social proof, after pricing, footer239- Single primary action per page — don't split attention240- Risk reversal near pricing: "30-day money-back guarantee", "If you're not stoked, request a refund"241- Scheduling integration (Calendly, SavvyCal) for "Book a call" CTAs — reduce friction242243### Information Architecture for Conversion244245```246Awareness → Hero + Problem (they realize they have the pain)247Interest → Solution + Social Proof (they see you can solve it)248Desire → Process + Pricing (they understand the path and cost)249Action → CTA + FAQ + Risk Reversal (they have no reason not to)250```251252### Objection Handling253254The FAQ section is a conversion tool, not an afterthought:255256- "Is this right for me?" → Qualify the audience clearly257- "How long does it take?" → Set clear timelines258- "What if it doesn't work?" → Guarantee or risk reversal259- "How is this different from [competitor/DIY]?" → Specific differentiators260- "Can I talk to someone first?" → Low-friction contact option261262---263264## Responsive Design265266### Breakpoint Rules267268- Mobile-first, always. Design for phones, then expand.269- Tailwind breakpoints: Use `sm:`, `md:`, `lg:` systematically270- Touch targets: Minimum 44px × 44px, preferably 48px271- Mobile text: 16px minimum body text (prevents iOS zoom)272- Stack vertically on mobile: Horizontal layouts become vertical273- Hide non-essential elements on mobile rather than cramming274- Test at real device widths, not just "make the browser narrow"275276### Common Responsive Patterns277278```279Hero: Full-width, reduced padding on mobile, stacked CTAs280Nav: Hamburger on mobile with full-screen overlay281Grid cards: 3-col desktop → 2-col tablet → 1-col mobile282Stats strip: Horizontal row → stacked or 2×2 grid283Pricing: Side-by-side → stacked with swipe284Testimonials: Carousel on mobile, grid on desktop285```286287---288289## Project-Type Reference290291Aesthetic direction varies by product category:292293### Developer/Technical Products294- Dark theme295- Monospace for UI elements296- Serif italic for editorial headlines297- Subtle noise texture and scanlines298- Numbered, uppercase, wide-tracked section labels299- Stats displayed prominently with large bold numbers300301### Consumer/Lifestyle Products302- Light or dark depending on brand303- Warmer palettes: beige, olive, earth tones, soft blues304- Elegant serif headlines, clean sans body text305- More photography, less illustration306- Approachable, warm copy tone307308### DeFi/Trading Products309- Dark theme310- Animated elements: live data, notification banners, real-time updates311- Neon accents (green for gains, red for losses)312- Glassmorphism cards with backdrop blur313- Wallet connection as first-class UI element314- "How it works" must be dead simple — 3 steps max315- Trust signals: audit badges, lock icons, transparency316317### Agency/Services318- Professional but not boring319- Split hero: copy left, social proof/image right320- Methodology section with numbered phases321- Real client testimonials with photos and metrics322- Tiered pricing with "Popular" indicator323- "Book a call" as primary CTA throughout324325---326327## Implementation Checklist328329Before shipping any landing page:330331### Visual332- [ ] Fonts loaded and rendering correctly333- [ ] Color palette is cohesive (2-3 colors max plus semantic colors)334- [ ] Visual hierarchy is clear at a glance335- [ ] Spacing follows 8px grid336- [ ] No orphaned headings or widowed lines337- [ ] Images optimized and properly sized338339### Copy340- [ ] Hero headline passes the "so what?" test341- [ ] Benefits lead, features support342- [ ] All copy uses second person ("your", "you")343- [ ] Numbers are specific, not vague344- [ ] No buzzwords or corporate speak345- [ ] CTA copy is action-oriented346347### UX348- [ ] Primary CTA visible without scrolling349- [ ] Page loads fast (no heavy animations on initial load)350- [ ] Smooth scroll between sections351- [ ] All interactive elements have hover/focus/active states352- [ ] Mobile experience tested at 375px width353- [ ] Touch targets are minimum 44px354- [ ] No horizontal scroll on any breakpoint355- [ ] Keyboard navigation works356357### Conversion358- [ ] Single clear primary action per page359- [ ] CTA repeated at minimum 3 scroll points360- [ ] Social proof appears before pricing361- [ ] Risk reversal present near the ask362- [ ] FAQ addresses top 3 objections363- [ ] Contact/booking friction is minimal