Ark UI about blocks.

150 about us sections for a company page: mission statements, the founding story, timelines, team and leadership, culture, careers, company numbers, customers, press, security and comparisons. The gallery sorts them into 14 groups: Statements, Company story, Timelines, Team and leaders, Team and offices, Culture and values, Careers, Numbers, Customers, Press and recognition, Comparisons, Principles and process, Security and platform, Support and contact. Each one is a React section file with Tailwind classes that you copy into your project.

For a founder story use Founder Letter with Margin Notes About or Converging Founder Paths About. For leadership use Leadership Remit Rows About or Advisory Board About. For figures use By The Numbers Bento About or Counters Row About, for the company's history Horizontal Track Timeline About or Rounds Funding Timeline About, and for customers Hover Card Customer Logos.

A short comment at the top says what the section draws, then the typed data (a LEADERS, MILESTONES or FACTS array of plain objects), then the markup. Many about sections have no state at all: Leadership Remit Rows and Horizontal Track Timeline are marked Static and carry no use client directive. The ones with a toggle, a tab or a form are client components.

No. Every example company is invented, people are initials in an avatar and the pictures are drawn in markup, so a section never depends on an image file. You put your own names, copy and pictures into the typed data.

Edit the typed arrays at the top of the file: LEADERS in the leadership rows, MILESTONES in the horizontal timeline, ROUNDS in the funding timeline, FACTS in the numbers bento. Many totals and labels in the markup are worked out from those arrays, so changing the data changes them with it.

The people sections render an Avatar with an AvatarFallback of initials. The avatar component also exports AvatarImage, so put an AvatarImage with your photo's src and the person's name as alt inside the same Avatar, and the initials stay as the fallback while it loads.

In By The Numbers Bento About the figures sit in a FACTS array and the trend in MONTHLY. Fetch your values on the server, pass them in as props or replace those constants, and keep each fact's note so the page still says how it was counted. The counters roll up when they scroll into view.

Guestbook Customer Wall adds a note to a list held in the page's memory and sends it nowhere, so a refresh clears it: call your API in its submit handler and save the note there. Newsletter Cadence About subscribes locally and says nothing was sent: put your mailing list call in its submit handler.

Add one object to the array, matching the interface declared above it in the file. The list renders one cell per item, so the timeline gains a dot and a grid gains a card without other changes. Keep the order the array is in, because the timelines read as ordered lists.

This page lists 150 of the category's 150 about blocks for React on Ark UI. The category comes in React (Base UI, React Aria, Ark UI and Radix UI), Vue, Svelte and Solid; the framework and UI library pickers at the top of any block's page switch between them.

The about blocks here are written on Ark UI primitives; the layout, the copy and the theme tokens are the same on every base, and the install path follows it (/r/ark/about-accessibility-pledge.json). The other bases are one picker away from /about-block/ark.

Each block is TypeScript and Tailwind CSS v4, styled with your theme's tokens, and imports our components (installed with it) on Ark UI. Icons come from lucide-react.

Open a block, copy its command and run it: `npx shadcn@latest add` with the block's registry URL, such as /r/ark/about-accessibility-pledge.json for Accordion Accessibility Pledge About. The code is copied into your project and it's yours to edit.

The block's file and the components it imports: Accordion Accessibility Pledge About brings Accordion, Badge and Guides, installed before it. Nothing else changes in your project.

Use the filters above the grid: 14 kinds of about block, led by customers (15), press and recognition (15), principles and process (14) and culture and values (13), and sort by popular or name. A good first look: Accordion Accessibility Pledge About, Advisory Board About and Alternating Chapters About. Each card opens the block's live page.

Every block draws the same page column and side rails with a top rule only (the Guides component), so a about block lines up with the one above and below it. Stack one per section and the rails read as a single drawing; pick across the story, people and proof kinds.

Open its page and use the full-screen viewer (/view/about/ark/accessibility-pledge) or the device-width previews. Every preview is free for everyone; only the code needs Pro.

Each about block uses semantic HTML: one heading level, real lists and labelled controls. Interactive parts sit on Ark UI, a headless library that follows the WAI-ARIA patterns, and the layouts use logical properties so they hold in right-to-left languages.

Yes. They use semantic tokens only (bg-card, text-muted-foreground), never palette colors, so they follow your preset, radius and dark mode. The primary color marks one action per block and is never a background.

No animation library: the about blocks' motion is CSS (transitions, entrance animations and SVG), and it stands still under prefers-reduced-motion.

The previews are free for everyone. The code of all 150 about blocks is Pro, as is every block: Pro unlocks the code, the install command and the MCP.

Only with a Team or Organization license: client work, SaaS products and anything your users pay for. The Individual license is for personal, non-commercial projects. See the license page for the full terms.

You keep using what you installed in your existing projects, but get no new downloads or updates, and the MCP stops answering. A Lifetime license includes all future updates.

No. You can use them in your own End Products, but not redistribute the code or designs on their own, or in a UI library, kit, template or website builder.

With Pro, yes: the MCP server (22 tools, one personal URL from /dashboard/mcp) lets your agent search_blocks for a about block, read it with get_block and install it on your React on Ark UI stack.

Pass `category: "about"` to search_blocks to search only the 150 about blocks, or to list_blocks for the 14 groups with their blocks. get_block then returns one with its install command.

plan_page plans a page as a stack of blocks for a brief. Pass `sections` with category ids, such as ["hero", "about", "footer"], to force the order; each section gets a pick and two alternatives, and get_block installs the stack.