Sections

CTA Section

Call-to-action section with customizable heading and button

Live Preview

🚀

Ready for the next layer?

Pick a track, study the references, and build something real while you learn.

Built for deliberate practice

Installation

// Copy the CtaSection component from
src/components/sections/CtaSection.tsx

Usage

import { CtaSection } from '@/components/sections/CtaSection'

export default function MyPage() {
  return (
    <CtaSection />
  )
}

Examples

Default CTA

Using default props

🚀

Ready for the next layer?

Pick a track, study the references, and build something real while you learn.

Built for deliberate practice

Custom CTA

Customized heading and button

🚀

Need help?

Our team is here to assist you

Built for deliberate practice

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 CTA Section in React/Next.js.
Goal: recreate the same overall UI and behavior as the CTA Section reference from a component gallery.
What it needs to communicate: Call-to-action section with customizable heading and button.

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.
- Avoid unnecessary dependencies unless the behavior truly requires them.
- No explicit color literals were found in the examples. Match the live reference and the project accent color when appropriate.

Props to support:
- heading: string — default "Ready for the next layer?" — Main heading text
- subheading: string — Secondary heading text
- ctaLabel: string — default "Explore tracks" — Button text
- ctaHref: string — default "/products" — Button link destination

Reference usage patterns:
- Default CTA

```tsx
<CtaSection />
```

- Custom CTA

```tsx
<CtaSection
  heading="Need help?"
  subheading="Choose the guidance format that matches your current blocker"
  ctaLabel="See guidance"
  ctaHref="/contact"
/>
```

Feature expectations:
- Gray background with white card
- Rocket emoji decoration
- Customizable heading and CTA
- Disclaimer text
- Centered layout

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

Prop	Type	Default	Description
`heading`	`string`	`"Ready for the next layer?"`	Main heading text
`subheading`	`string`	-	Secondary heading text
`ctaLabel`	`string`	`"Explore tracks"`	Button text
`ctaHref`	`string`	`"/products"`	Button link destination

Features

✓Gray background with white card
✓Rocket emoji decoration
✓Customizable heading and CTA
✓Disclaimer text
✓Centered layout

← Back to Sections