Alternating Scenario Rows

(Where it fits)

The same practice, doing three different jobs.

Each of these started as a single request and turned into a longer relationship, which is usually the sign we picked the right problem.

Open print publication with a clean two-column layout

01

A press that needed readers, not a rebrand

Hallvard came for a logo and left with a catalogue people finish. We rebuilt the reading order first and only then drew anything, which is why the mark took eleven weeks and the sales conversation took one.

Catalogue completion
Doubled
Print run
12,000 copies
Close detail of a minimal control surface

02

A hardware team whose product spoke better than its pages

Norvik built something quietly excellent and described it in specifications nobody could hold. We wrote the language first, then designed the pages around the two sentences that actually landed.

Setup support tickets
Halved
Time on product page
3x longer
Pared-back retail interior with monochrome shelving

03

A retailer opening rooms faster than it could brand them

Marchetti was signing leases monthly. We built a kit their local teams could apply without us, then spent our remaining days training the people who would use it after handover.

Rooms opened with the kit
18
Studio days per opening
Down to 2
About this block

Alternating Scenario RowsPRO

Three use cases as image and text rows, each numbered and carrying a story, two ruled outcome figures and its own outline pill link; pictures stay top-aligned and the side only alternates from lg, so a tablet keeps every image at the top left.

Usecase45: Alternating Scenario Rows

Three use cases told as alternating image and text rows. Each is numbered and carries a story, two ruled outcome figures and its own outline pill link, with the image side flipping on every second row so the page keeps a rhythm without repeating a layout.

Upgrade to Pro

Pro blocks install through the shadcn CLI with your license key and ship their full source. Docs and live previews stay open to everyone, so you can read every block's details first.

Upgrade Now

Installation

Swap YOUR_EMAIL and YOUR_KEY for the email and license key on your account. Find your license key on your account page.

Radix flavor

bash
npx shadcn add "https://ui.beste.co/r/usecase45?email=YOUR_EMAIL&license_key=YOUR_KEY"

Base UI flavor

bash
npx shadcn add "https://ui.beste.co/r-base/usecase45?email=YOUR_EMAIL&license_key=YOUR_KEY"

This installs the block to components/beste/block/usecase45.tsx plus the badge7 eyebrow and button12 pill button it uses.

Quick start

The installed file exports usecase45Demo alongside the block: the exact props behind the preview above. Spread it to get a working scenario section in one line.

tsx
import { Usecase45, usecase45Demo } from "@/components/beste/block/usecase45";

export default function Page() {
  return <Usecase45 {...usecase45Demo} />;
}

Then replace the demo with your own props. Written out, a trimmed setup looks like this:

tsx
import { Usecase45 } from "@/components/beste/block/usecase45";

export default function Page() {
  return (
    <Usecase45
      badge={{ label: "Where it fits" }}
      heading="The same practice, doing three different jobs."
      description="Each started as a single request and turned into a longer relationship."
      scenarios={[
        {
          index: "01",
          title: "A press that needed readers, not a rebrand",
          description: "We rebuilt the reading order first and only then drew anything.",
          image: { src: "/work/press.jpg", alt: "Open print publication" },
          results: [
            { title: "Catalogue completion", value: "Doubled" },
            { title: "Print run", value: "12,000 copies" },
          ],
          button: { label: "Read the case", href: "/work/press" },
        },
      ]}
    />
  );
}

Props

PropTypeDefaultDescription
badge{ label: string }Eyebrow label rendered as a Badge7
headingstringSection heading in the left column
descriptionstringSupporting paragraph, right-aligned from md up
scenariosScenario[][]One alternating row per use case
classNamestringExtra classes for the outer <section>
ts
type Scenario = {
  index: string;
  title: string;
  description: string;
  image: { src: string; alt: string };
  results: ScenarioResult[];
  button: ActionButton;
};

type ScenarioResult = {
  title: string;
  value: string;
};

type ActionButton = {
  label: string;
  href: string;
};

Behavior notes

  • The flip is done with index % 2 === 1 && "lg:[&>*:first-child]:order-last", so the DOM order stays image-then-text for every row and only the visual order alternates; a screen reader hears the same sequence throughout.
  • Rows align on md:items-start, so a short picture sits at the top of its row rather than floating in the middle of a taller text column, and the alternation only starts at lg: on a tablet every image stays top left.
  • index is a string, not a number, so a row can read 01, A or Case 4 and the block never reformats or renumbers it.
  • Each scenario carries its own button, since these usually deep-link to different case studies; the tone is fixed to outline so no row competes with the page's primary CTA.
  • Results are dt/dd pairs on their own border-t rules, matching the ruled treatment used for figures across the set rather than a boxed stat card.
  • Images sit in an aspect-[4/3] box with object-cover and no hover effect, so any source crop works and nothing moves under the pointer.

More Use Case blocks

View all Use Case
PRO

usecase59

Linked Situation Rows

Five situations as ruled rows, each one a whole link: a square photograph pinned left, a serif sentence over its paragraph, and an arrow link at the right end that lifts as the row tints on hover.

PRO

usecase41

Role Use Case Cards

A use-case section with an eyebrow over a hairline rule, a two-column heading, and three bordered role cards with an icon chip, a role label, a title, a description, and an arrow link.

PRO

usecase51

Two Route Photo Columns

Two picture-led routes side by side, each with an eyebrow, title, dotted-rule expectations list and its own pill CTA, separated on desktop by a small pill divider sitting between the columns.

PRO

usecase53

Single Case Photo Story

One client story told in three photographed steps, opening with the client name on a ruled block beside the heading and closing with three oversized outcome figures.

PRO

usecase42

Multi-Site Locations

A multi-site use case with an eyebrow over a hairline rule, a two-column heading, and three image tiles that each float a live location card above a title and description.

FREE

usecase2

Use Case Card Grid

Responsive grid of use case cards with hover effects, images, descriptions, and feature checklists. Perfect for displaying solutions for different industries or customer segments.