Skip to main content

About

Pages

For a company about page

The about page: mission, story, milestones, values and numbers, the team grid, a careers teaser with open roles and the closing CTA.

Make it yours

npx shadcn@latest add https://elabs-ai.com/r/about-page.json

Skipping the @source line is the most common first failure: Tailwind does not scan node_modules, so every component renders unstyled. The one-time wiring

Prompt for your coding agent

Paste it into Claude Code, Cursor, Codex or any other coding agent. Text in [brackets] is yours to fill in.

Add the brand-ui template "About" (about-page) to this project — a whole screen copied into the app, built from registry blocks and the @elabs-ai/components-* packages.

1. Read https://elabs-ai.com/llms.txt first: it maps every package and the rules. If you can use MCP servers, connect https://elabs-ai.com/mcp and use its search, docs and tokens tools. If not, run the same lookups in the terminal: `npx -y @elabs-ai/components-cli search "<what you need>"` and `npx -y @elabs-ai/components-cli docs <Component>`.
2. Make sure the base is in place: `pnpm add @elabs-ai/components-tokens @elabs-ai/components-ui` (or `npm install @elabs-ai/components-tokens @elabs-ai/components-ui`), then the packages the template imports: . If this is the first brand-ui package in the project, wire it once: import `@elabs-ai/components-tokens/styles.css` plus the `themes/light.css` and `themes/dark.css` stylesheets in the CSS entry, add one Tailwind `@source` line per installed @elabs-ai package (Tailwind does not scan node_modules, so without it everything renders unstyled), and wrap the app root in `ThemeProvider` from `@elabs-ai/components-tokens`.
3. Copy the template in with `npx shadcn@latest add https://elabs-ai.com/r/about-page.json` — it brings its blocks with it (about-story-01, careers-01, marketing-cta-01, marketing-team-01, site-frame); if that url does not answer, copy the folders from https://github.com/mreimitz/elabs-components/tree/main/registry/blocks instead.
4. Mount the page at a route, keep its `WorkspaceShell` frame, and replace the seeded data with ours: [the route, the real data source, and what should change from the template]
5. Rules: use only @elabs-ai/components-* components and the semantic tokens — no raw colours, no raw font sizes, no arbitrary Tailwind values. Look up each component's real props with the docs tool before you use it; never guess a prop.
6. Done means: the typecheck passes, `npx -y @elabs-ai/components-cli audit src --strict` reports nothing, and you have opened the app and looked at every screen you touched in the light and the dark theme.

What it is made of

The blocks and packages the template composes — each has its own page. Copy the template and you copy the blocks with it.

5 blocks

How do I tell the company’s story with a timeline, values and the numbers?

“Our story”: the mission beside the founding prose, a milestone timeline that runs across the page at wide widths and down it at narrow ones with “today” marked, four values with an icon and prose, and the company by the numbers in a StatsBand.

2 examples

How do I list open roles with filters that work and an empty state that keeps the candidate?

Open roles under three reasons to join: team and location selects plus a remote switch narrow the list, roles are grouped by team as rows with location, type, a “New” badge and an apply link, the count is announced, and an empty state takes an email when nothing matches.

3 examples

The closing ask: one primary action, one quieter alternative and what trying it costs.

1 example

Names, roles and one line about each person; container-query columns.

1 example
site-frameThe frame every full-screen template sits in.