Landing Sections
Orbit Image Gallery Hero Section
A hero section where 12 to 18 image cards sit in a circular orbit around a centered headline and CTA row. Each card hovers up and flips 180 degrees on interaction. Perfect for image-heavy product landing pages (avatar generators, portrait studios, photo tools) where the imagery is the story.
Live preview
No extra dependencies. React 18+ and Tailwind CSS v3+ assumed. Save as OrbitGalleryHero.tsx.
Or rebuild it with a prompt
Paste the prompt into the tool you already use. Each version is written specifically for that tool, matched to the same design constraints so the output stays consistent.
Build components/OrbitGalleryHero.tsx. A hero section, min-h-screen, bg-white. In the background: an absolute layer with an image gallery arranged in a circle. Each card is 62x78px, positioned via translate(sin(angle)*radius, -cos(angle)*radius) rotate(angle) from the center. Cards use CSS transform-style: preserve-3d to enable a rotateY(180deg) flip on hover, with a translateY(-12px) bounce (cubic-bezier(0.34,1.56,0.64,1)). Two faces per card (front and back), both showing the same image (or different images if provided). Foreground: pointer-events-none flex column, centered vertically and horizontally, with a headline (text-[16-17px] font-semibold tracking-tight text-black leading-snug max-w-[280px]), a subtitle (text-[11px] text-[#737373] leading-relaxed max-w-[280px]), and two CTA buttons (white outline + solid blue #2B65F6). Wrap CTA buttons in a pointer-events-auto div. Props: title?, subtitle?, primaryCta?, secondaryCta?, images?, radius? (default 290), cardWidth? (62), cardHeight? (78). Respect prefers-reduced-motion (disable hover flip and bounce). Single default export. Font-sans throughout.
How to use it
- Ideal for image-first product landings: avatar generators, portrait studios, photo tools, gallery apps.
- Works best with twelve to eighteen images that share a visual style.
- Card flip pauses under reduced-motion. Responsive from phone to desktop.
Other components you might like
Landing Sections
Apple-Style Product Hero Section
Minimal Apple-style product hero for React landing pages: display headline, one-line subtitle, two text links.
Scroll & Motion
3D Parallax Depth Hero Section
3D parallax depth hero for React, image layers recede on scroll while the headline scales up and pushes forward.
Scroll & Motion
Pull Quote Testimonial Hero
Editorial pull quote hero for React, sticky testimonial at a small display size over a full-bleed image.
Related prompts for landing sections
Frequently asked questions
How do I use this component in my project?+
Copy the source file from the "Copy code" button and save it into your components folder. Add any listed dependencies (React 18 or later and Tailwind CSS v3 or later are always required, plus framer-motion or gradflow if the component lists them). Import and render the component wherever you want it. Every prop is optional and defaulted.
Can I customise the design and copy?+
Yes. Every component takes props for its content (headline, subtitle, image URL, CTA, and so on) and uses Tailwind classes throughout, so you can restyle without touching the logic. For deeper design changes, paste the prompt into Claude Code, Cursor, Lovable, Replit, or Codex and describe your brand tokens, spacing, or motion tweaks.
Are the components free for commercial use?+
Yes. Everything on this page is free to copy, adapt, and ship in commercial projects. No attribution required. If you post a public showcase we always appreciate a link back.
Which AI coding tool works best for these components?+
All five prompts produce the same design. Claude Code and Codex are best when you want the component slotted into a project with existing conventions. Cursor is ideal for editing inside your IDE with the file open. Lovable and Replit spin up a fresh preview fastest, useful for a quick play.
Do these work with Next.js, Vite, and Remix?+
Yes. The source files are plain React 18 client components. They run on any framework that supports React 18 and Tailwind CSS v3. If a component needs the "use client" directive (all of them do here, since they use hooks), keep the directive at the top of the file when you paste.