Examples ​

Whole applications rather than single components. Each one lives in the repository, so it is built and type-checked alongside the library and breaks the moment a change breaks it.

Dashboard ​

An admin dashboard for a billing product: a shell with navigation that becomes a drawer on a phone, a table with sorting, selection, row actions and pagination, charts, a create form in a drawer, and a settings page with validation.

Running it ​

git clone https://github.com/therok1/iryx-ui
cd iryx-ui
pnpm install
pnpm --filter @iryx-ui/example-dashboard dev

Copying it out ​

Two lines exist only because it runs inside this repository: the iryx-ui alias in vite.config.ts, which points at the library source so a component change shows up without a rebuild, and the @source line in src/style.css, which scans that same source for utility classes. Delete both and iryx-ui resolves to the published package, which is what you want anywhere else.

Marketing ​

A product marketing site, built from the blocks: a sticky header with a mobile drawer, an IHero over an aurora and a ruled grid, banded ISections of features and stats, an IPricingTable, customer logos, testimonials, an accordion of questions, and a split-screen sign-in page with third-party providers.

It is the reference for what the blocks are for — the page files hold copy and data, and almost no layout.

Running it ​

git clone https://github.com/therok1/iryx-ui
cd iryx-ui
pnpm install
pnpm --filter @iryx-ui/example-marketing dev

Copying it out ​

The same lines are local to this repository: the two iryx-ui aliases in vite.config.ts — one for the package root, one for the iryx-ui/marketing subpath the blocks come from — and the @source line in src/style.css. Delete all three and both specifiers resolve to the published package.