Technology
Tailwind CSS
Tailwind is how tokens reach the page without a second language. We configure it to match the design system, then we stop inventing spacing.
What it is
Tailwind CSS is a utility CSS framework: small classes that map to CSS properties, composed in the markup instead of inventing a class name for every new layout. GitHub, Laravel's marketing, and a large share of new product UIs use it because the system is the classes, not a 400-line SCSS file nobody owns.
It does not replace design. A bad type scale in Tailwind is still a bad type scale. What it replaces is the argument about where the CSS lives. Used with a small set of tokens, it stays a system. Used as a junk drawer, it becomes a junk drawer.
What it does
Teams use Tailwind to ship interfaces quickly with a consistent spacing and type scale, especially in React and Next.js apps. Designers who can read the classes can review a pull request without opening a second tool.
We set tokens first, then utilities. We do not paste a landing-page dump of arbitrary values. The system has to survive a tenth page.
Why we use it
The CSS system that keeps pages consistent.
Marketing sites and product UI on the same scale. Dark or campaign themes that swap tokens, not templates. A CMS block cannot go off-brand because the utilities only expose the system. The handover matches the Figma file so nobody is guessing 17px.
If a lander does not look like the product, the config failed, or the brief did.
Built on it
GitHub
Has used Tailwind on marketing and product surfaces.
Laravel
The PHP framework's official sites and starter kits are Tailwind-first.
OpenAI
Marketing and product web UI have shipped with Tailwind utilities.
Shopify
Hydrogen templates and many Hydrogen storefronts start on Tailwind.
Vercel
Templates and a large share of the Next.js example ecosystem are Tailwind.
Tell us what needs to ship.
You use a working prototype before the production build goes ahead.