Why WCKD UI

Because your team needs speed.clarity.momentum.precision.consistency.control.

... and a UI system that layers beside your stack, not one that locks you into a vendor framework.

Build now, standardize later

Same building blocks everywhere.

Marketing, product, and internal tools share one set of tokens and utilities so pages stay consistent as the team grows.

Tokens

Color, spacing, and type live in theme.css.

Components

Demos and copy-paste HTML for menus, tabs, overlays, and more.

Utilities

Shared layout and style classes instead of endless one-off CSS.

Runtime

One small script, only where a pattern needs JavaScript.

Design and code stay aligned.

Shared names

Same token and utility names in specs and in the DOM.

Clearer handoff

Less guesswork between mockups and what ships in the browser.

Easier updates

Change a token or pattern once, then reuse it across pages.

Solid defaults. Your brand on top.

Safer defaults

Sensible spacing, type, and interaction out of the box.

Less drift

Reuse the same layout shells and utilities so CSS does not sprawl.

Your repo

No UI framework lock-in. Ship it like any other static asset.

Adopt in phases

Start small. Add only what you use.

Wire the core bundle first, then pull in optional components per page. Get Started includes a package builder so you skip files you will never load.

Foundations

Load wckd-ui.css, component CSS, and wckd-ui.js. Set your shell and tokens in theme.css.

Selective enhancements

Add optional CSS from wckd-ui-kit/components only where you need that pattern.

Scale over time

Grow brand and layout rules in theme.css and your templates.

Own what you ship.

Start from the kit defaults. Own color, motion, and layout rules in your own files. The kit stays small; your product layer sits beside it. Need a website or landing pages? Contact Us for a quote.