Sections

Hero Section

Full-width hero section with animated content and code mockup

Quick Preview

✦ Next.js Learning Platform

LEARN NEXT.JS,
SHIP LIKE A PRO.

Master App Router, React patterns, Tailwind v4, component architecture, and production-ready workflows through examples that teach how real projects are built.

Browse component library

Structured for deliberate practice · Built for professional growth

✓ Deployed

Customising Content

// src/lib/constants.ts
export const HERO = {
  badge: '✦ Now in Beta',
  heading: 'MOVE FAST,',
  headingAccent: 'STAY FEARLESS.',
  subheading: 'The modern platform to launch, scale, and automate your business.',
  primaryCta:  { label: 'Get started free', href: '/products/starter' },
  secondaryCta: { label: 'View components →',  href: '/components' },
}

Installation

# Copy the component file
cp src/components/sections/HeroSection.tsx your-project/src/components/sections/

# Install peer dependencies
npm install framer-motion lucide-react

Prompt Preview

Copy a prompt that recreates this UI

Paste this into your AI coding assistant to generate code that closely matches the reference, including color, size, shape, typography, spacing, and polish.

Copy-ready AI prompt

Starts from the current visual reference and project constraints.

Build a sections component named Hero Section in React/Next.js.
Goal: recreate the same overall UI and behavior as the Hero Section reference from a component gallery.
What it needs to communicate: Full-width hero section with animated content and code mockup.

Project constraints:
- Use Next.js 16.2.6 with the App Router, React 19, TypeScript strict mode, and Tailwind CSS v4.
- Do not create a tailwind.config.js file. Use Tailwind v4 utilities and CSS variables where design tokens are needed.
- If you are implementing this inside the same project, use the Prompt font via next/font/google. If not, use the closest equivalent typeface.
- Return production-ready code with imports, responsive behavior, keyboard accessibility, and polished empty, hover, focus, active, and disabled states where relevant.
- Match the reference closely: color palette, spacing scale, border radius, shadows, icon scale, typography hierarchy, and motion timing.

Component-specific expectations:
- Treat the result as a full-width section with strong layout rhythm and responsive spacing.
- Preserve headline hierarchy, supporting copy, and clear CTA emphasis.
- Existing documented dependencies: framer-motion
- No explicit color literals were found in the examples. Match the live reference and the project accent color when appropriate.

Props to support:
- No documented props were provided, so infer a minimal but production-ready API from the reference.

Reference usage patterns:
- Hero Section

```tsx
<HeroSection />
```

Feature expectations:
- Black background with CSS grid pattern
- Teal glow effect
- Framer Motion animations
- Two-column layout (text + mockup)
- Badge, heading, CTA buttons
- Fake code editor mockup
- Staggered animation delays

Output requirements:
- Return complete code, not pseudocode.
- Include all necessary imports and helper types.
- Keep the implementation accessible, responsive, and visually finished.
- Match the reference for color, size, shape, typography, spacing, and interaction states as closely as possible.
- If multiple files are needed, organize them cleanly and explain the file structure briefly.

Tweak only product-specific copy or data after the first generation pass.

Props

This component has no props.

This component uses constants from lib/constants.ts

Features

✓Black background with CSS grid pattern
✓Teal glow effect
✓Framer Motion animations
✓Two-column layout (text + mockup)
✓Badge, heading, CTA buttons
✓Fake code editor mockup
✓Staggered animation delays

Dependencies

framer-motion

← Back to Sections