Docs / KATA vs five CSS libraries
DaisyUI, Web Awesome, Basecoat, Pico CSS and Franken UI, from their official pages on 2026-11-07, with the areas where KATA loses.
Every fact below was read from the project’s own site, docs, repository or npm entry on 2026-11-07; each section ends with its sources. Star counts are the rounded figures on each repository page. A fact the official pages do not state is marked “not stated”. KATA facts come from this repository: 136 components, 21 blocks and 7 templates, MIT, no build step, no framework, plain JavaScript only where a part needs behavior, published 2026-11-01 by one maintainer.
Version 5.7.50 (2026-10-13), MIT. Requires Tailwind CSS through a plugin; a no-build CDN path also loads the Tailwind browser script (63 kB compressed, some variant classes excluded). 68 components and 600+ utility classes, no JavaScript. Theming through CSS variables and data-theme, with 35 built-in themes. RTL: “support LTR/RTL in runtime” with dir=rtl. Accessibility: not stated on the pages read.
Where it beats KATA: 42.8k GitHub stars and a commercial ecosystem (templates, charts, a Figma library); 35 ready themes against KATA’s Foundry presets. Sources: daisyui.com, daisyui.com/docs/install/, daisyui.com/docs/cdn/, daisyui.com/docs/themes/, github.com/saadeghi/daisyui, npm daisyui.
Version 3.14.0 (2026-09-24). The core is MIT (“free and open source”); Pro is paid per seat per year at custom pricing, with a perpetual option. No Tailwind and no framework; loads from its CDN with a link and a script. 50+ components, built as Web Components, so JavaScript is required for them (a CSS-only native.css styles plain HTML elements). Themes as design tokens: 3 free, 8 Pro. Accessibility: “built with accessibility in mind”, no WCAG level stated. RTL: dir attribute supported; right-to-left languages are not discussed further.
Where it beats KATA: company backing (Font Awesome) and the Shoelace lineage; components work the same in React, Vue, Angular and Svelte; paid support and a Figma kit exist. Sources: webawesome.com, webawesome.com/docs/, webawesome.com/docs/themes, webawesome.com/purchase, webawesome.com/docs/resources/accessibility, npm @awesome.me/webawesome.
Version 1.1.0 (2026-10-23), MIT, no paid tier found. The npm path is authored for Tailwind CSS; a CDN stylesheet works without Tailwind for “simple static pages and prototypes”. No framework. Count not stated; the docs list 42 entries. Optional plain JavaScript for 11 interactive parts; Chart uses Chart.js. shadcn/ui-style CSS variables and theme compatibility, 8 style packs, “dark mode ready”. Accessibility: “follow accessibility best practices”. RTL: not stated.
Where it beats KATA: it reuses shadcn/ui themes and design language, which many teams already know, and ships Nunjucks and Jinja templates. 4.4k GitHub stars. Sources: basecoatui.com, basecoatui.com/introduction, basecoatui.com/installation, github.com/hunvreus/basecoat, npm basecoat-css.
Version 2.1.1 (2025-03-15), code MIT. The repository was archived on 2026-10-04 and says “Pico CSS is no longer maintained” and “v2.1.1 is the final release”; picocss.com does not mention this. No Tailwind, build step, framework or JavaScript; one link from a CDN. Styles semantic HTML, with 9 listed components and a class-less version. 20 color themes; light and dark follow prefers-color-scheme. RTL: supported with dir=rtl.
Where it beats KATA: plain semantic HTML needs no classes at all, and 16.8k GitHub stars show how many pages used it. It no longer receives fixes. Sources: picocss.com, picocss.com/docs, picocss.com/docs/rtl, github.com/picocss/pico, npm @picocss/pico.
Version 2.1.2 (2026-01-18), MIT per npm and the repository. Its repository now says “Franken is now 0build”; 0build.dev does not mention Franken UI. Built on Tailwind CSS (a pre-built CDN file of about 91 kB gzipped, or a Vite plugin) and on UIkit 3 with LitElement; JavaScript is required for interactive parts. Count not stated; the docs list 59 components and 7 form entries. shadcn-style CSS variables; full theming needs the Vite plugin. Accessibility: examples “comply with the WCAG 2.1 standards”, depending on the author’s markup. RTL: not stated.
Where it beats KATA: UIkit 3 supplies a long-tested behavior layer with documented keyboard and ARIA handling. 2.6k GitHub stars; the project’s direction is unclear after the rename. Sources: franken-ui.dev/docs/2.1/installation, franken-ui.dev/docs/2.1/javascript, franken-ui.dev/docs/2.1/theming, franken-ui.dev/docs/2.1/accessibility, github.com/franken-ui/ui, npm franken-ui.
Community and age: KATA was published on 2026-11-01 by one maintainer, and every library above has a larger and older user base. Ready themes: DaisyUI ships 35 and Pico 20. Framework parity: Web Awesome components behave the same inside React, Vue, Angular and Svelte; KATA markup pastes into JSX but has no framework bindings. Screen-reader verification: 1 KATA part (Button) has a recorded screen-reader pass; the rest are beta.
Unlike DaisyUI, Basecoat and Franken UI, no Tailwind and no build step; unlike Web Awesome, no Web Components runtime; unlike Pico, a full catalog of 136 parts plus blocks and templates under one checked token set, and a registry, MCP server and AI Skill for assistants. RTL is built in with logical properties, and a Japan genre and Japanese docs for ten parts exist.
Corrections are welcome as GitHub issues; this page is dated and will be rechecked before each release.
Introduction · Getting Started · CLI · Theming · Dark Mode · Accessibility · Installation · Plain HTML · Astro · Laravel · React & Next.js · JavaScript · Guide: Building a Dashboard · Guide: Building a Settings Page · Guide: Building a Pricing Page · Guide: Sign-in & Account Pages · Guide: Forms, For Real · Guide: Data Tables That Survive Real Data · AI Prompts · Why Vanilla · The Mold · Anatomy of a Part · Coming from Tailwind · KATA vs shadcn/ui · FAQ · Registry · Forms · MCP Server · RTL · Contributing · Changelog · Mold changelog · Update your mold