Sections

Container Query Section

Feature grid that uses CSS Container Queries (@container) to adapt card layout to container width — not the viewport. Showcases Tailwind v4 @container support.

Quick Preview

@container queries

Adapts to Any Context

These cards use container queries (@container / @md variants) to change layout based on their container — not the viewport.

⚡

Container Queries

Tailwind v4

Components adapt to their parent container width, not the viewport. Build truly reusable UI.

🎨

Design Tokens

CSS Variables

All design tokens live in @theme inline — colors, spacing, shadows and animations in one place.

🌙

Dark Mode

@custom-variant

Manual dark mode via @custom-variant dark — add .dark class to enable, no flicker.

🔷

TypeScript

Strict Mode

Every component ships with strict TypeScript types and IntelliSense support.

🌐

OKLCH Colors

P3 Colors

Perceptually uniform color scale using OKLCH — better interpolation, wider gamut.

📦

@utility Classes

v4 Feature

Define reusable CSS utilities with @utility — they work with all Tailwind variants.

How it works

Each card wrapper has @container — the inner layout uses @md:flex-row to switch from column to row once the card is wide enough.

@container / @md:flex-row

Installation

// Copy component from
src/components/sections/ContainerQuerySection.tsx

Usage

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

const items = [
  {
    icon:        '⚡',
    title:       'Container Queries',
    description: 'Adapts layout to container width, not viewport.',
    badge:       'Tailwind v4',
    badgeColor:  'teal',   // 'teal' | 'blue' | 'violet' | 'orange' | 'pink'
  },
  // ...more items
]

export default function Page() {
  return (
    <ContainerQuerySection
      title="Why use our platform?"
      subtitle="Cards adapt their layout to their own container size."
      items={items}
    />
  )
}

Custom items

3-column custom items

@container queries

Platform Features

Everything you need to ship faster.

🚀

Deploy in seconds

CI/CD

Push to GitHub and your site goes live automatically via CI/CD.

🔒

Security first

SOC 2

Zero-trust architecture with end-to-end encryption at rest and in transit.

📊

Analytics built-in

Real-time

Real-time dashboards, custom events, and retention funnels included.

How it works

Each card wrapper has @container — the inner layout uses @md:flex-row to switch from column to row once the card is wide enough.

@container / @md:flex-row

How container queries work

// The card wrapper is the container
<div className="@container">
  {/* Inner layout: column by default, row when container ≥ 28rem */}
  <div className="flex flex-col @md:flex-row gap-4">
    <div className="w-11 h-11 rounded-xl">Icon</div>
    <div>
      <h3>Title</h3>
      <p>Description</p>
    </div>
  </div>
</div>

// Container query breakpoints (Tailwind v4):
// @xs  — 20rem  (320px)
// @sm  — 24rem  (384px)
// @md  — 28rem  (448px)   ← used in this component
// @lg  — 32rem  (512px)
// @xl  — 36rem  (576px)
// @2xl — 42rem  (672px)
// @3xl — 48rem  (768px)

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 Container Query Section in React/Next.js.
Goal: recreate the same overall UI and behavior as the Container Query Section reference from a component gallery.
What it needs to communicate: Feature grid that uses CSS Container Queries (@container) to adapt card layout to container width — not the viewport. Showcases Tailwind v4 @container support..

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 — Section heading
- subtitle: string — Section sub-heading
- items: ContainerQueryItem[] — Array of feature items
- className: string — Additional CSS classes

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

Feature expectations:
- @container queries
- Tailwind v4 @md: container variant
- Server Component
- Badge color variants

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`	-	Section heading
`subtitle`	`string`	-	Section sub-heading
`items`	`ContainerQueryItem[]`	-	Array of feature items
`className`	`string`	-	Additional CSS classes