Sections

Contact Section

Contact form with info panel, simulated async submit, and success state

Quick Preview

Get in touch

Have a question or want to work together? We'd love to hear from you.

Contact information

hello@example.com

Phone

+1 (555) 000-0000

Address

123 Main Street, San Francisco, CA 94105

Support hours

Monday – Friday, 9 AM – 6 PM (GMT+7)

We respond to all emails within 24 hours.

Installation

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

Usage

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

<ContactSection
  title="Get in touch"
  info={{
    email:   'hello@company.com',
    phone:   '+66 2 000 0000',
    address: '123 Sukhumvit Rd, Bangkok 10110',
  }}
/>

Connecting a real API

// Replace the setTimeout in ContactSection.tsx with:
async function handleSubmit(e: React.FormEvent) {
  e.preventDefault()
  setLoading(true)
  try {
    await fetch('/api/contact', {
      method: 'POST',
      headers: { 'Content-Type': 'application/json' },
      body: JSON.stringify(form),
    })
    setSubmitted(true)
  } finally {
    setLoading(false)
  }
}

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 Contact Section in React/Next.js.
Goal: recreate the same overall UI and behavior as the Contact Section reference from a component gallery.
What it needs to communicate: Contact form with info panel, simulated async submit, and success state.

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:
- title: string — default "Get in touch" — Section heading
- subtitle: string — Section sub-heading
- info: ContactInfo — { email?, phone?, address? }
- className: string — Additional CSS classes

Reference usage patterns:
- No examples were documented. Infer a sensible default presentation and one richer usage example.

Feature expectations:
- Two-column layout (info + form)
- Loading spinner and success state
- Native form validation
- Support hours callout
- Client Component (form state)

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
`title`	`string`	`"Get in touch"`	Section heading
`subtitle`	`string`	-	Section sub-heading
`info`	`ContactInfo`	-	{ email?, phone?, address? }
`className`	`string`	-	Additional CSS classes

Features

✓Two-column layout (info + form)
✓Loading spinner and success state
✓Native form validation
✓Support hours callout
✓Client Component (form state)