Landing page
A landing page: the promise beside the product alive in a window, a band of proofs, the features as a bento where the main one takes the room, the closing call.
Web uniquement — React, depuis @krizaka/ui/landing-page. Bêta : son API peut encore changer à une version mineure.
Quand l’utiliser
- The home of a company or a product line.
- A campaign page that must sell in one screen.
Quand ne pas l’utiliser
- For one product's page, with its traps and decisions.À la place : Product page
- For a list of entry points.À la place : Docs hub page
Installation
Installer
npm install @krizaka/ui @krizaka/tailwind @krizaka/tokens tailwindcssStyles
@import "tailwindcss";
@import "@krizaka/tailwind";
@import "@krizaka/ui/tailwind.css";Importer
import { LandingPage } from "@krizaka/ui/landing-page";Exemples
Krizaka
The studio's landing: the promise, the console alive, proofs, three products in a bento.
Software studio · Montréal
Products that keep what is yours
Krizaka builds sovereign AI and a platform where creators are paid — open source, on your servers or ours.
$ npx orazaka install
✓ 1,284 answers this week, none left the server
- 34
- public repositories
- Apache-2.0
- every line
- 0
- telemetry calls
What we build
Three products, one way of building
Orazaka — the AI that never leaves home
Chat, image, voice and video on your own server, one governed pipeline.
Orochia
Creators paid 90 % of what fans spend.
Yazakia
Meet by talking first — coming.
Open building blocks
Users, billing, notifications — on Maven Central and npm.
One design system
Krizaka UI, web and mobile, documented from its code.
Something to build together?
Tell us what you need; a person answers within two days.
Props
A landing page: split hero with the product alive, proofs, a bento of features, the closing call.
| Prop | Type | Défaut | Description |
|---|---|---|---|
featuresrequis | readonly LandingFeature[] | — | The features, as a bento. |
titlerequis | ReactNode | — | The promise: the page's h1. |
visualrequis | ReactNode | — | The product, alive, beside the words: a recording, a live demo (framed as a window). |
actions | ReactNode | — | The hero's actions (the main one cut, with shimmer). |
closing | { title: ReactNode; body?: ReactNode; actions: ReactNode; } | — | The closing call: its title, body and actions. |
eyebrow | ReactNode | — | A mono line above the title. |
featuresHeading | { eyebrow?: ReactNode; title: ReactNode; lead?: ReactNode; } | — | The features' section: its eyebrow, title and lead. |
lead | ReactNode | — | One or two sentences under it. |
proofs | readonly { value: ReactNode; label: ReactNode; }[] | — | Figures or facts in a band under the hero: { value, label }. |
visualLabel | ReactNode | — | The window's caption (orochia.app — studio). |
Accessibilité
- The hero's title is the page's
h1; the window is afigure, its bar decorative. - Proofs are a description list; the bento a list of features.
Bonnes pratiques
- One
lgfeature in the bento: the one the visitor came for. - The window shows the real product (a recording, a demo), never a mock-up.
- Three or four proofs, each a fact that can be checked.
- Words and content arrive as props; the motion is the platform's (
[data-reveal], still under reduced motion).
Composants liés
Générée depuis le code de @krizaka/ui 2.10.0 : son meta.ts, ses exemples et ses types.Modifier cette documentation sur GitHub
How-it-works page
How a product works, told in steps along a numbered line — each step its words beside its visual, the sides alternating on a wide screen.
Legal page
A policy or terms: the date in force, the short version in plain words, the sections in a narrow column with their contents beside them.