System

A layered approach to
marketing websites.

UINUX is not a collection of templates. It is a system with three layers that build on each other.

01

Design Tokens

The foundation. Colors, spacing, typography, radii, and shadows defined as variables. Every decision is encoded once and referenced everywhere. No magic numbers. No drift between pages.

Includes

  • Color scales with semantic aliases
  • Spacing scale (4px base unit)
  • Typography scale with fluid sizing
  • Border radius and shadow tokens
  • Dark mode built into the token layer
02

Components

Composable UI blocks built on top of the token layer. Each component respects the system constraints. Override when you need to, but the defaults are production-ready.

Includes

  • Navigation, hero, feature sections
  • Pricing tables, CTAs, footers
  • Responsive by default
  • Accessible markup
  • Consistent API across all components
03

Templates

Full page compositions assembled from components. These are not wireframes. They are finished, deployable pages that follow the same layout grid and visual rhythm.

Includes

  • Landing pages
  • Product pages
  • About and team pages
  • Blog layouts
  • Documentation shells

What UINUX Is Not

Not a marketplace

UINUX does not sell hundreds of loosely related templates. Every product shares the same system. Quality over quantity.

Not framework-agnostic

We build for Next.js. Optimizing for one stack means fewer compromises and better defaults.

Not a UI kit

UI kits give you pieces. UINUX gives you a system — tokens, components, and templates that are connected by design.

Not disposable

Every product is versioned, maintained, and documented. Built to last years, not weeks.

Principles

Shared source of truth

Change a token, and every component and template updates. No find-and-replace. No broken pages.

Versioned releases

Every product follows semantic versioning. You always know what changed and when.

Framework-aware

Built for Next.js App Router. Not framework-agnostic to a fault — optimized for the tools you actually use.

Maintainable by one person

No complex build pipelines. No monorepo overhead. A solo founder can ship and maintain this.