Hero — split (motion)

"use client"

/**
 * The `hero-split` demo, with the motion variant swapped in.
 *
 * Identical props: the motion variant only changes which slot components
 * the static section renders through.
 *
 * `"use client"` is required here, not incidental: the motion variant is a
 * client component, and icon components cannot cross a server-to-client
 * boundary as props. See the note on `IconComponent`.
 */

import { HeroSplitMotion } from "@registry/sections/hero-split-motion"

import { ACTIONS, MediaPlaceholder } from "./content"

export function Demo() {
  return (
    <HeroSplitMotion
      eyebrow="Sections"
      title="Build the page, not the primitives"
      description="Every section takes typed content and slots, so assembling a landing page is composition rather than another round of copy-paste."
      actions={ACTIONS}
      note="Works in any React 19 project."
      media={<MediaPlaceholder label="Product screenshot" />}
      headingLevel={1}
      spacing="md"
    />
  )
}

"use client"

/**
 * HeroSplitMotion — the split hero with a staggered entrance.
 *
 * A genuine wrapper: it renders the static `HeroSplit` and only swaps the stack
 * slots. Nothing visual and no accessibility decision is duplicated, so the two
 * variants cannot drift apart.
 *
 * The stagger plays on mount rather than on scroll — a hero is above the fold by
 * definition, and waiting for an intersection that already happened would just
 * leave it invisible for a frame.
 *
 * Dependencies: react, @/components/motion/slots,
 * @/components/sections/hero-split.
 */

import { StaggerBlock, StaggerStack } from "@/components/motion/slots"
import { HeroSplit, type HeroSplitProps } from "@/components/sections/hero-split"

export type HeroSplitMotionProps = Omit<HeroSplitProps, "stackAs" | "blockAs">

export function HeroSplitMotion(props: HeroSplitMotionProps) {
  return <HeroSplit {...props} stackAs={StaggerStack} blockAs={StaggerBlock} />
}