Skip to content

Process with deliverables

Each stage lists what the client actually receives.

Contentstarterprocessdeliverablesengagementproposal

Live preview

full widthLive preview — open it in a new tab for the full-height version.
Open the preview in a new tab

Source

This exact file renders the preview above.

import { CheckCircle2 } from 'lucide-react'
import { Container } from '@/components/ui/layout'
import { Badge } from '@/components/ui/badge'

/**
 * Process with deliverables
 *
 * Each stage lists what the client actually receives. A process section that
 * only names stages describes activity; naming the deliverable describes value,
 * and it is what makes a proposal reviewable.
 */
const stages = [
  {
    stage: 'Discovery',
    weeks: 'Weeks 1–2',
    summary: 'Inventory, interviews and a written assessment of where the current system leaks.',
    deliverables: [
      'Component inventory spreadsheet',
      'Written audit with prioritised findings',
      'Recorded walkthrough',
    ],
  },
  {
    stage: 'Foundations',
    weeks: 'Weeks 3–5',
    summary: 'Token set, theming strategy and the first ten primitives with real states.',
    deliverables: [
      'Token file with light and dark',
      'Ten primitives in your repository',
      'Contribution guide',
    ],
  },
  {
    stage: 'Adoption',
    weeks: 'Weeks 6–12',
    summary: 'Sections, one migrated production route, and a team that can continue without us.',
    deliverables: [
      'Section library',
      'One migrated route in production',
      'Two half-day working sessions',
    ],
  },
]

export default function SplitDetailProcess() {
  return (
    <section className="border-b border-line bg-canvas py-section">
      <Container>
        <div className="max-w-2xl">
          <h2 className="display-type text-2xl font-semibold text-ink-strong sm:text-3xl">
            What you get, stage by stage.
          </h2>
          <p className="mt-3 text-md text-ink-muted">Named deliverables, not named activities.</p>
        </div>

        <div className="mt-10 flex flex-col divide-y divide-[var(--color-border)] border-y border-line">
          {stages.map((stage) => (
            <div key={stage.stage} className="grid gap-5 py-8 lg:grid-cols-[1fr_1.4fr] lg:gap-12">
              <div>
                <Badge size="sm">{stage.weeks}</Badge>
                <h3 className="display-type mt-3 text-xl font-semibold text-ink-strong">
                  {stage.stage}
                </h3>
                <p className="mt-2 text-sm text-ink-muted">{stage.summary}</p>
              </div>
              <ul className="flex flex-col gap-2.5">
                {stage.deliverables.map((deliverable) => (
                  <li key={deliverable} className="flex items-start gap-2.5 text-sm text-ink">
                    <CheckCircle2
                      className="mt-0.5 size-4 shrink-0 text-success"
                      aria-hidden="true"
                    />
                    {deliverable}
                  </li>
                ))}
              </ul>
            </div>
          ))}
        </div>
      </Container>
    </section>
  )
}

components/blocks/sections/process/split-detail.tsx

import { CheckCircle2 } from 'lucide-react'
import { Container } from '@/components/ui/layout'
import { Badge } from '@/components/ui/badge'

/**
 * Process with deliverables
 *
 * Each stage lists what the client actually receives. A process section that
 * only names stages describes activity; naming the deliverable describes value,
 * and it is what makes a proposal reviewable.
 */
const stages = [
  {
    stage: 'Discovery',
    weeks: 'Weeks 1–2',
    summary: 'Inventory, interviews and a written assessment of where the current system leaks.',
    deliverables: [
      'Component inventory spreadsheet',
      'Written audit with prioritised findings',
      'Recorded walkthrough',
    ],
  },
  {
    stage: 'Foundations',
    weeks: 'Weeks 3–5',
    summary: 'Token set, theming strategy and the first ten primitives with real states.',
    deliverables: [
      'Token file with light and dark',
      'Ten primitives in your repository',
      'Contribution guide',
    ],
  },
  {
    stage: 'Adoption',
    weeks: 'Weeks 6–12',
    summary: 'Sections, one migrated production route, and a team that can continue without us.',
    deliverables: [
      'Section library',
      'One migrated route in production',
      'Two half-day working sessions',
    ],
  },
]

export default function SplitDetailProcess() {
  return (
    <section className="border-b border-line bg-canvas py-section">
      <Container>
        <div className="max-w-2xl">
          <h2 className="display-type text-2xl font-semibold text-ink-strong sm:text-3xl">
            What you get, stage by stage.
          </h2>
          <p className="mt-3 text-md text-ink-muted">Named deliverables, not named activities.</p>
        </div>

        <div className="mt-10 flex flex-col divide-y divide-[var(--color-border)] border-y border-line">
          {stages.map((stage) => (
            <div key={stage.stage} className="grid gap-5 py-8 lg:grid-cols-[1fr_1.4fr] lg:gap-12">
              <div>
                <Badge size="sm">{stage.weeks}</Badge>
                <h3 className="display-type mt-3 text-xl font-semibold text-ink-strong">
                  {stage.stage}
                </h3>
                <p className="mt-2 text-sm text-ink-muted">{stage.summary}</p>
              </div>
              <ul className="flex flex-col gap-2.5">
                {stage.deliverables.map((deliverable) => (
                  <li key={deliverable} className="flex items-start gap-2.5 text-sm text-ink">
                    <CheckCircle2
                      className="mt-0.5 size-4 shrink-0 text-success"
                      aria-hidden="true"
                    />
                    {deliverable}
                  </li>
                ))}
              </ul>
            </div>
          ))}
        </div>
      </Container>
    </section>
  )
}

components/ui/badge.tsx

import type { HTMLAttributes, ReactNode } from 'react'
import { variants } from '@/lib/variants'

/**
 * Badge
 *
 * A compact, non-interactive label. Tones map to the status token trios, and
 * because a badge is often the only signal in a dense table, the `dot` option
 * exists to add a second, colour-independent cue alongside the text.
 */
const badgeVariants = variants('inline-flex items-center gap-1.5 whitespace-nowrap font-medium', {
  variants: {
    tone: {
      neutral: 'bg-surface-sunken text-ink-muted border-line',
      accent: 'bg-accent-soft text-accent-soft-ink border-accent-line',
      success: 'bg-success-soft text-success border-success-line',
      warning: 'bg-warning-soft text-warning border-warning-line',
      danger: 'bg-danger-soft text-danger border-danger-line',
      info: 'bg-info-soft text-info border-info-line',
      inverse: 'bg-surface-inverse text-ink-inverse border-transparent',
    },
    appearance: {
      soft: 'border',
      outline: 'border bg-transparent',
      solid: 'border border-transparent',
    },
    size: {
      sm: 'h-4.5 rounded-sm px-1.5 text-2xs',
      md: 'h-5.5 rounded-sm px-2 text-xs',
    },
  },
  defaultVariants: { tone: 'neutral', appearance: 'soft', size: 'md' },
  compound: [
    { appearance: 'solid', tone: 'accent', class: 'bg-accent text-accent-ink' },
    { appearance: 'solid', tone: 'success', class: 'bg-success text-white' },
    { appearance: 'solid', tone: 'warning', class: 'bg-warning text-white' },
    { appearance: 'solid', tone: 'danger', class: 'bg-danger text-white' },
    { appearance: 'solid', tone: 'info', class: 'bg-info text-white' },
    { appearance: 'solid', tone: 'neutral', class: 'bg-ink text-ink-inverse' },
    { appearance: 'outline', tone: 'neutral', class: 'text-ink-muted' },
  ],
})

export type BadgeTone = 'neutral' | 'accent' | 'success' | 'warning' | 'danger' | 'info' | 'inverse'

export interface BadgeProps extends HTMLAttributes<HTMLSpanElement> {
  tone?: BadgeTone
  appearance?: 'soft' | 'outline' | 'solid'
  size?: 'sm' | 'md'
  /** Adds a leading dot so the badge does not rely on hue alone. */
  dot?: boolean
  icon?: ReactNode
}

export function Badge({
  tone = 'neutral',
  appearance = 'soft',
  size = 'md',
  dot = false,
  icon,
  className,
  children,
  ...props
}: BadgeProps) {
  return (
    <span className={badgeVariants({ tone, appearance, size, className })} {...props}>
      {dot ? (
        <span className="size-1.5 shrink-0 rounded-full bg-current" aria-hidden="true" />
      ) : null}
      {icon}
      {children}
    </span>
  )
}

Demo source — adapt to your project. Foundry is not published as a package.

Usage

A process section that only names stages describes activity. Naming the deliverable describes value, and it is what makes a proposal reviewable.

  • Every deliverable should be a noun you could attach to an email.
  • Keep deliverables to three per stage; more reads as padding.

Variants and states

Every entry below is a genuine difference in behaviour or layout, and every one of them is visible in the preview above.

  • Three stages
  • Deliverable lists
  • Week ranges

Accessibility

Paired structure
Stage summary and deliverables are separate regions within one row.
List semantics
Deliverables are a real list with tick icons hidden from assistive tech.

Foundry implements published ARIA patterns and is tested against them. No WCAG certification is claimed — see the accessibility documentation for what is and is not covered.