Legal59: Readable Policy

A policy written to be read: a sticky contents list with numbered links down one side, and the sections themselves ruled and set at a comfortable measure on the other.

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

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

Base UI flavor

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

This installs the block to components/beste/block/legal59.tsx plus the button22 sliding-marker pill and the text1 word stagger it uses.

Quick start

The installed file exports legal59Demo alongside the block: the exact props behind the preview above. Spread it to get a working policy page in one line.

import { Legal59, legal59Demo } from "@/components/beste/block/legal59";

export default function Page() {
  return <Legal59 {...legal59Demo} />;
}

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

import { Legal59 } from "@/components/beste/block/legal59";

export default function Page() {
  return (
    <Legal59
      eyebrow="Privacy"
      heading="What we keep, and what we never do with it."
      updated="Last revised August 2026"
      intro="This is written to be read, not scrolled past."
      sections={[
        {
          title: "What we collect",
          paragraphs: [
            "Your name, an email address and, if you give it, a phone number.",
            "We do not record sessions, in the room or online.",
          ],
        },
        {
          title: "Your choices",
          paragraphs: ["You can read, correct or ask us to delete anything we hold, at any time."],
        },
      ]}
      button={{ label: "Ask a privacy question", href: "mailto:hello@beste.co", tone: "outline" }}
      labels={{ contents: "On this page" }}
    />
  );
}

Props

type Section = {
  title: string;
  paragraphs: string[];
};

type ActionButton = {
  label: string;
  href: string;
  tone?: "primary" | "light" | "dark" | "outline";
};

Behavior notes

• Anchors are slugs built from the section titles, so a link to a clause reads #what-we-collect rather than a generated id. A policy is a document people quote to each other, and the URL should survive being pasted into an email.
• The slug is normalised (accents stripped, non-alphanumerics collapsed to hyphens) and de-duplicated: a repeated title gets a numeric suffix, and an empty one falls back to section-N, so no two anchors can ever collide.
• Because the anchors come from the titles rather than from a render-time id, they stay stable across reloads and between the server and the client.
• Every section carries scroll-mt-28, so following a contents link leaves the heading clear of a sticky navbar rather than tucked under it.
• The contents list is an ol with numbers in tabular-nums, and it is md:sticky md:top-28 so it stays available down a long document; below md it returns to normal flow.
• Sections are article elements with h2 titles under the page h1, so the document outline matches what the contents list claims.
• Paragraphs are plain strings, so no markup is rendered inside them; a link inside a clause means extending the block rather than passing HTML.