Skip to main content

Coming Soon

Pages

For a pre-launch / waitlist page

The pre-launch page: an email-first hero with benefits and social proof, the waitlist with its milestones, and a preview of the features to come.

Make it yours

npx shadcn@latest add https://elabs-ai.com/r/coming-soon-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 "Coming Soon" (coming-soon-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/coming-soon-page.json` — it brings its blocks with it (marketing-features-01, marketing-hero-03, marketing-waitlist-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.

4 blocks

A SectionHeader plus a FeatureGrid of six outcome-led reasons.

2 examples

How do I capture an email right in the hero?

A centred hero with the sign-up inline: an email field that validates on submit, a pending state on the button and a confirmation naming the address, then three benefits and the people already in — stacked avatars, a count and a rating.

4 examples

How do I get in early, and who else is waiting?

A launch waitlist: the pitch, one email field that validates and shows a pending state, and on success the place in line with a referral link and a copy button (clipboard behind a try/catch, with a fallback message). The faces and count show who is already waiting; three dated milestones say what has shipped and what is coming.

3 examples
site-frameThe frame every full-screen template sits in.