# Highlight Agents: start with [Workspace for Agents](https://workspace.socra.com/solutions/agents.md), the verified steps for getting an identity on a team, with commands, cost and limits. Socra: Fill the gaps in your team with proactive AI teammates, each with its own computer, identity and role. Canonical: https://socra.design/landing/highlight ## Governing rules [Building with Socra components](https://socra.design/agents.md) explains setup, consumption rules and verification. Semantic owner: Flash Module `ui-chapters` in Socra Cortex when available. It supplies current intent and prerequisite rules; the public API below supplies exact code names and values. ## Owning Module contract: ui-chapters v35 - Each chapter associates one visible heading with its claim, supporting explanation and proof. - Centered, split and editorial chapters keep semantic order; compact split places claim before proof. - Bands grow with content; screen height is a minimum. - Proof may be contained or deliberately bleed while copy keeps its readable rail. - Peer cards group comparable destinations or artifacts; ordinary prose stays on the open canvas. - Text-only peer cards align actions without forcing media height; incomplete compact rows center deliberately. - Prominent marketing action groups place one filled primary before an outlined secondary in reading, focus and visual order. - A secondary CTA keeps an explicit boundary even alone. - CTA buttons are at least 48 high with a 12-unit gap and complete labels. - Equal pairs share width and height and stack at the full rail when labels no longer fit. - Centered groups stay centered; wide split groups align to logical start. - Larger destination sets use menus or supporting navigation rather than equal button stacks. - Inline prose links keep text-link semantics. - Structural changes preserve approved copy, destinations, media and sequence. - Article previews keep one native destination and show covers only when width supports them. - Compact tool grids keep intended columns and usable targets on narrow phones. - Pricing visuals align amounts with billing bases and use hierarchy for rates and inclusions. Use published property names, not inspector labels. Composition and preview settings are not component props. Public styling escape hatches do not permit product-local presentation overrides. The decisive phrase in a heading or a line of copy. Mark the words a chapter turns on. Statement headings pair it with the statement scale; a progression’s closing line uses the strong tone. Status: ready. Shared landing emphasis (landing.Highlight: accent, critical and strong tones that stay legible inside gradient headings; landing.BandHeader, BandIntro, CenteredChapter and SplitChapter take headingScale="statement" for the page’s turning points: 36, 48 and 64px, weight 500, tightened tracking) lives in @socra/ui-web-landing. Library: @socra/ui-web-landing ## Properties [Complete public API, including inherited properties and event signatures](https://socra.design/landing/highlight/api.md) ### Setup - Use the host-selected compatible Socra theme provider and published component styles. Keep one compatible provider instance across shared packages. ### Highlight Import: `import { Highlight } from '@socra/ui-web-landing';` | Property | Type or permitted values | Default / omission | Required | Meaning and behavior | Inspector | | --- | --- | --- | --- | --- | --- | | `children` | `ReactNode` | Required input | yes | The decisive phrase. Keep it to a few words. | Direct API | | `tone` | `"strong"`, `"accent"`, `"critical"` | `"accent"` | no | | Tone | ### CenteredChapter Import: `import { CenteredChapter } from '@socra/ui-web-landing';` | Property | Type or permitted values | Default / omission | Required | Meaning and behavior | Inspector | | --- | --- | --- | --- | --- | --- | | `align` | `"center"`, `"responsive"` | `"responsive"` | no | Whether the chapter's introduction centers at every width or start-aligns below \`md\`. A page whose thesis is centered by design passes \`center\`; without it a centered chapter reads as left-aligned on a phone, which the page then has to correct with CSS of its own. | Direct API | | `brand` | `ReactNode` | Omitted; no declared default | no | Product lockup above the chapter heading. | Direct API | | `children` | `ReactNode` | Omitted; no declared default | no | Actions or supporting copy rendered with the chapter introduction. | Direct API | | `conclusion` | `ReactNode` | Omitted; no declared default | no | The chapter's closing statement, set on the \`lead\` role below the media, where the reader lands after the proof. One sentence. | Direct API | | `description` | `string` | Required input | yes | Supporting copy beneath the heading. | Direct API | | `descriptionTone` | `"secondary"`, `"primary"` | `'primary'` | no | Supporting copy emphasis. | Direct API | | `divider` | `false`, `true` | `false` | no | Marks a real change in the page's argument. | Direct API | | `headingScale` | `"section"`, `"statement"` | `'section'` | no | The heading scale. \`statement\` marks the page's turning points; pair it with a \`Highlight\` on the decisive phrase. | Heading scale | | `headingTreatment` | `"solid"`, `"gradient"` | `'gradient'` | no | The heading paint treatment. | Direct API | | `id` | `string \| undefined` | Omitted; no declared default | no | Anchor id for in-page navigation. | Direct API | | `level` | `"h1"`, `"h2"` | `"h2"` | no | Heading level. Only the page's opening chapter should use h1. | Direct API | | `media` | `ReactNode` | Required input | yes | The explanatory visual or page-owned animated artifact. | Direct API | | `mediaLayout` | `"contained"`, `"mobile-bleed"`, `"viewport-bleed"` | `"contained"` | no | \`mobile-bleed\` lets an interactive visual use the complete phone viewport while retaining the shared content rail from \`sm\` upward. \`viewport-bleed\` gives large explanatory media the full phone viewport and the viewport rail at every larger breakpoint. | Direct API | | `note` | `CenteredChapterNote \| undefined` | Omitted; no declared default | no | Text that is read rather than declaimed, such as a three-sentence price: set in body type beneath the media, centered at a reading measure, with its actions directly beneath it, so the text and its actions are the chapter's last word and never sit apart. A statement belongs in \`conclusion\`. | Direct API | | `spacing` | `"none"`, `"compact"`, `"screen"`, `"regular"` | `"regular"` | no | The chapter's vertical rhythm; \`screen\` claims the viewport. | Direct API | | `title` | `ReactNode` | Required input | yes | The chapter heading. | Direct API | | `tone` | `"base"`, `"surface"`, `"raised"` | `"base"` | no | The chapter's surface step. | Direct API | ### Behavior and constraints - Tone belongs to Highlight; heading scale belongs to the surrounding demonstration chapter. ### Inspector mappings | Setting | Initial preview value | Consumed code | | --- | --- | --- | | Tone | `accent` | Highlight.tone | | Heading scale | `statement` | CenteredChapter.headingScale. Preview default: The isolated headline specimen starts at statement scale; ordinary Highlight defaults to section scale. | ## Example ```tsx import { Highlight } from '@socra/ui-web-landing'; export function Example() { return (

One source for every answer

); } ```