Ruixen UI is a multi-stack marketing UI library for shadcn projects. Hero blocks, pricing, footers, navbars, FAQs — plus the primitives, effects, and gradients that go around them. Drop in with one CLI command. Works with Tailwind v3 or v4, Radix or Base UI.
What Ruixen is for
If you're building a landing page or marketing site on top of shadcn, Ruixen is the catalog you reach for. The Sections group ships full landing-page blocks (hero, pricing, footer, FAQs, navbars). The Components group covers the primitives every landing page needs (buttons, inputs, cards, text effects, AI chat inputs, gradients). Everything installs through the standard shadcn CLI.
Why multi-stack matters
Ruixen ships across four stacks. Every component is generated into Tailwind v3, Tailwind v4, Radix, and Base UI variants from one source codebase at build time. Pick the variant that matches your project and install with one command — whether you're pinned to Tailwind v3 for legacy compatibility, evaluating Base UI for accessibility or licensing, or running the latest stack:
# Tailwind v4 + Radix (default)
npx shadcn@latest add "https://ruixen.com/r/staggered-faq-section"
# Tailwind v3 + Radix
npx shadcn@latest add "https://ruixen.com/r/tw3/staggered-faq-section"
# Tailwind v4 + Base UI
npx shadcn@latest add "https://ruixen.com/r/baseui/staggered-faq-section"
# Tailwind v3 + Base UI
npx shadcn@latest add "https://ruixen.com/r/baseui/tw3/staggered-faq-section"What's inside
- Sections (51) — Hero, Pricing, FAQs, Footers, Navbars, Featured, Client. Front-of-website blocks.
- Components (88) — Buttons, Inputs, Cards, Forms, Backgrounds, Text Effects, AI Chat Inputs, Audio & Media, and more. Primitives and effects for landing pages.
- App UI (39) — Calendars, File Management, Pagination, Notifications. A bonus catalog for app interfaces; maintained but not the focus.
Free + Pro
The free open-source catalog stays free, MIT-licensed. Ruixen Pro adds 50+ premium components and full landing-page templates with lifetime updates for $59 once.
A note on motion
A subset of components — buttons, switches, badges, accordions — use motion/react springs and a 3ms Web Audio click for a more tactile feel. They render fine without it; opt out per-component with sound={false}. It's a flavor on the interactive primitives, not a universal feature.
Request a section
Need a section we don't have yet? DM us on Twitter or open a GitHub issue. We'll add it to the registry.