Introduction
Nexus UI is a library of animated React components, page-section blocks and landing-page templates. You add the ones you want to your own project and the code is yours to change.
What is Nexus UI?
There is no Nexus UI package to install and import from. Each component is a handful of source files that you copy into your project, so you can read them, restyle them and delete what you do not need. They are written for Next.js (App Router) with TypeScript, Tailwind CSS v4 and Framer Motion.
The library has three parts: 371 components, 23 blocks (page sections that come in several layouts) and 42 templates (whole landing pages). 84 of the components are free; the rest need a Pro plan. Every Pro item stays visible with a live preview, and only its source and install are locked.
What is in the box
- Components. One animated piece of interface, such as a button, a card stack, a text effect or a background. Each page has a live preview, a usage example, its props and the install command.
- Blocks. A full section of a page, such as a hero, a FAQ or a sidebar, with several layouts to choose from. They install the same way as components.
- Templates. Complete landing pages built from the components, each with a live preview.
- Icons. 700 animated icons, each one file with its own optional sound. See the icons docs.
- Sounds. Optional interface sounds that some components play. They are off until the visitor turns them on, and the Sounds page lets you hear them.
How a component gets into your project
There are two ways, and both end with the same files in your project. Both start from a Next.js project that has shadcn/ui set up (the Quick Start does that in two commands).
- With the CLI. Connect the
@nexus-labsregistry once, then one command installs a component, the helpers it imports and its npm packages:Free items need nothing more. Pro items also need an API key from your dashboard, kept innpx shadcn@latest add @nexus-labs/glow-button.env.local. - By hand. The component's page lists every source file with the exact path to save it to. You create those files and paste the code. No registry or API key is involved, though Pro source is shown only while you are signed in with a Pro plan.
The exact steps for both, free and Pro, are in the Quick Start, and the CLI page is the reference for the commands.
What shadcn add does
Simulated — nothing runs on your machine
- my-app
- .env.local
- components.json
- next.config.ts
- package.json
- tsconfig.json
Pick an item and press Run. File lists and dependencies match the real wheel-selector registry entry.
Read the docs in this order
- 1.Quick Start — the whole path from an empty folder to a component on screen. If you only read one page, read this one.
- 2.Install Next.js — what the create command does, if you want the detail.
- 3.Install Tailwind CSS — the colour tokens and dark mode.
- 4.Add utilities — the
cn()helper every component imports. - 5.CLI — registry setup, Pro API keys, options and error messages.