Skip to content

Installation

Core takes two or three lines in your HTML, with no framework and no build step. Free, MIT license. This page builds your first page and then explains the two ways to get Core into your project.

Your first page in 60 seconds

These three lines, inside the <head>, are all you need. The version is pinned in the URL, so what you paste today won’t change tomorrow.

html
<link rel="stylesheet" href="https://taisho.design/core/0.16.0/taisho.tokens.css" integrity="sha384-+2WHAtu42BCWEq7KajKLeexi0n+E4UXhDgH4f5iQLZWhC0WJf3DNRH2uBr4FrdIV" crossorigin="anonymous">
<link rel="stylesheet" href="https://taisho.design/core/0.16.0/taisho.full.css" integrity="sha384-nXkvfhi45iBlfj6WyOwieVBV1uWh8pQaHK9ObB4RPzCC2Rsj7tXlloB4fMGH4l/9" crossorigin="anonymous">
<script type="module" src="https://taisho.design/core/0.16.0/taisho.core.js" integrity="sha384-AcLAh9bi9NFu/LxLgFXtP6pkTui6MW3eUwTLDBIxFsWjSBwiQqzxo3zTWvBjpnpE" crossorigin="anonymous"></script>

Order matters. The theme goes first, because it defines the variables the system CSS reads. Then the system CSS, and last the behavior JS, which initializes itself.

If the CSS and the JS are from different versions, Core warns once in the browser console and keeps working.

Save this as index.html and open it in the browser. You get a heading, a button, and a modal that opens and closes. Classes are written with the ts scope class on the same element (class="ts button size-md variant-primary").

index.html

From here, every component on the docs home has its HTML to copy. The available classes are in Utilities, and their grammar is in Class names.


Two ways to get Core

The first is the one you just used. The files come from the CDN. The second installs the @taishods/core package and its taisho command, which compiles the CSS with your brand. Both are the same Core, and you can switch from one to the other whenever you want.

Via CDN With the package and CLI
What you needNothing—the files come from the CDNNode 22.18 or newer, and npm
How you install itPaste the lines abovenpm i -D @taishods/core
The CSSPrecompiled, with the system themetaisho generate compiles it with your brand and, with content, only what you use
Your brandYour own variables, in a CSS file after the themeYour color seeds in taisho.config.ts
Responsive variantsA curated set of utilitiesAny utility with any screen you write

With the package and CLI

To get your colors into the CSS instead of the system theme, install the package and run the CLI from your project root. The package is on the public npm registry: no account, token, or prior setup is needed.

bash
npm i -D @taishods/core
npx taisho init       # asks for language, brand, theme, fonts, icons, output folder, and whether to install lucide-static, and writes taisho.config.ts
npx taisho generate   # compiles your CSS and copies the JS to that folder

Your theme

The CDN serves Core precompiled with the TaishoDS Core theme. To use yours (your colors, radii, neutrals), you need to compile it. The theme lives in taisho.config.ts, and npx taisho generate writes the CSS with it.

generate writes theme.css (your tokens), fonts.css, and the system CSS, and when it’s done it prints the exact <link> and <script> lines to paste. The behavior JS ends up in taisho/taisho.core.js, next to the CSS, with only the modules your content names (without content, with all of them). That folder is the one that ships with your site: init asks which it is (it suggests public/taisho, static/taisho, or ./taisho based on the project) and saves it as out in taisho.config.ts. The icons come from the lucide-static package: init offers to install it (npx taisho init --install-icons installs it without asking) and, later, it installs with npm i -D lucide-static. generate only warns, with that command, if the code uses icons that don’t resolve because the package is missing. The details of the commands and the config file are in Theming.

While you work, npx taisho watch keeps the CSS up to date on its own. Every time you save a file, the config, or a custom icon, it regenerates what changed. If you use Vite, the taisho() plugin does the same inside the dev server.

With a bundler

If the project already uses Vite or another bundler, the CSS and the JS are imported by name from the package, with no files to copy or link: the bundler includes them in what you deploy.

js

The base plus only the components you use

The CDN also publishes the system split up: taisho.base.css (reset, utilities, and animations, no components), one taisho.<component>.css per component, and taisho.components.css with all of them. Each file carries only its own rules, so a component that uses another needs both. The Button can show a Spinner, so you also load taisho.spinner.css. Each component page says what else to load (“Also load,” in its “TaishoDS Core” section). Alert Dialog, Container, Field, Stack, and Visually Hidden have no file of their own—they’re built from the base and the components in their example.

base + Button + Spinner

File size

Every size figure in the docs comes from this section and from a single measurement. Measured on 2026-11-14 at commit d00a144a, with the latest published version of each system. Sizes are KB (1 KB = 1024 bytes) with gzip level 9 and, in parentheses, brotli quality 11; each file is compressed separately and the results are added. Fonts and icons are not counted.

A real page, each system in its best form

Three product pages (a team dashboard, a forms screen, and a landing page), each built with every system’s official components and the same list of parts. Each system is used the way it recommends: with purging or by module when it can. The markup for the other systems was written by whoever ran this measurement, from their documentation, and the TaishoDS page uses the text of its official examples. One instance of each component, not a whole project.

System and how it is used Dashboard (KB gzip and brotli) Forms (KB gzip and brotli) Landing (KB gzip and brotli)
DaisyUI 5.8.0: Purged CSS; Cally for the calendar. Forms adds Cally.13.1 (11.3)21.5 (19.1)8.1 (7.2)
TaishoDS Core: Compiled mode: on-demand CSS with a pruned theme and only the JS modules the page uses38.3 (32.8)44.5 (38.0)15.8 (13.5)
Bootstrap 5.3.9: Sass with only the modules used and JS per module. Forms adds flatpickr.48.7 (39.1)47.2 (38.2)23.5 (17.2)
Flowbite 4.0.2: Purged CSS; full flowbite.min.js40.7 (35.6)40.6 (35.5)40.2 (35.1)
UIkit 3.25.31: uikit-core plus the components used. Forms adds flatpickr.67.6 (57.9)80.3 (69.2)63.2 (54.0)
Web Awesome 3.14.0 (gratuita): With a bundler: each component used, separately101.8 (79.2)99.5 (76.4)59.2 (47.7)
Preline 5.1.0: Purged CSS; full preline.js. Forms adds lodash.112.4 (91.5)138.5 (114.6)111.3 (90.5)

In gzip, TaishoDS Core comes in 2nd on the dashboard, 3rd on forms, and 2nd on the landing, among 7 systems; in brotli, 2nd, 3rd and 2nd. Ahead in gzip, page by page: Dashboard: DaisyUI; Forms: DaisyUI and Flowbite; Landing: DaisyUI. DaisyUI comes out ahead because it solves almost everything with CSS and only adds JS for the calendar.

The full file (CDN)

What you download when you load each system’s distribution file, with no purging or modules. The full TaishoDS Core file carries every component and the whole utility vocabulary.

System and files CSS (KB gzip) JS (KB gzip) Total, gzip (brotli) Total uncompressed
Bootstrap 5.3.9: bootstrap.min.css and bootstrap.bundle.min.js30.023.353.3 (42.9)305.7
Flowbite 4.0.2: flowbite.min.css and flowbite.min.js26.728.855.5 (45.6)317.5
DaisyUI 5.8.0: daisyui.css, no JS65.6—65.6 (41.3)1154.4
TaishoDS Core: taisho.tokens.css, taisho.full.css, and the taisho.core.js base66.215.181.3 (55.6)775.4
UIkit 3.25.31: uikit.min.css and uikit.min.js30.352.282.4 (69.9)427.9
Web Awesome 3.14.0 (gratuita): every component in a single file, with a bundler13.8193.3207.1 (155.0)897.1
Web Awesome 3.14.0 (gratuita): CDN with the autoloader, depending on the page13.884.0 to 169.697.8 to 183.4 (80.5 to 152.9)—

As a full file, TaishoDS Core comes in 4th of 6 in gzip and 4th in brotli. Ahead in gzip: Bootstrap, Flowbite, and DaisyUI. Its CSS alone (theme plus full file) is 66.2 KB gzipped and 726.0 KB uncompressed, which the browser has to parse.

TaishoDS Core JS

The JS comes in pieces: the base plus a module for each heavy component, which downloads only if the page uses it. In Direct mode, the sum is what the browser actually requests; in Compiled mode, taisho generate builds one file with the modules your content names.

TaishoDS Core JS, depending on what the page uses JS (KB gzip and brotli)
Direct mode: the base (Tabs, Accordion, Menu, Toast… and no heavy component)15.1 (13.6)
Direct mode: the base plus DatePicker26.9 (24.2)
Direct mode: the base plus Select or Combobox21.4 (19.2)
Direct mode: the base plus command palette18.6 (16.7)
Direct mode: the base plus NumberInput18.8 (16.9)
Direct mode: the base plus Slider18.2 (16.4)
Direct mode: the base plus Table17.5 (15.7)
Direct mode: the base plus Pagination17.4 (15.5)
Direct mode: the base plus FileUpload17.3 (15.5)
Direct mode: the base plus field validation (markInvalid)16.9 (15.1)
Direct mode: the base and all 10 heavy modules (17 files)43.4 (38.9)
Compiled mode: no modules3.5 (3.1)
Compiled mode: a page with only Tabs4.8 (4.3)
Compiled mode: a page with a DatePicker13.2 (12.0)
Compiled mode: every module34.2 (30.1)

TaishoDS Core CSS

If you want less, there are two paths. Load the base and only the components you use from the CDN, or compile with taisho generate and content, which keeps only what your files use in the CSS.

TaishoDS Core CSS, depending on how it is loaded CSS (KB gzip and brotli) Uncompressed
Direct mode: theme and full CSS66.2 (42.0)726.0
Compiled mode: the dashboard reference, with the theme19.0 (15.4)149.3
Compiled mode: the forms screen reference, with the theme18.8 (15.1)164.7
Compiled mode: the landing page reference, with the theme9.8 (8.2)71.5
Compiled mode: the base only, with the theme2.1 (1.7)6.8
Compiled mode: a page with a DatePicker, with the theme11.4 (9.4)93.7
Compiled mode: all 56 components together, with the theme28.5 (22.4)250.4

Troubleshooting

If you pasted the HTML and something doesn’t respond, it’s almost always one of these five. Check them in this order.

What you see Why How to fix it
Everything shows up as plain, unstyled textThe element is missing the ts scope class.Write class="ts button", not just the class name. The ts class goes on every element that uses system classes. In local development (localhost), if the Core CSS is loaded and no element has ts, the Core JS says so in the console.
There are styles, but not the system’s colors or typographyThe theme is missing or comes after the system CSS.taisho.tokens.css always goes first. It defines the variables the system CSS reads.
A component looks half-styledYou loaded the split CSS and the file for that component, or for one it uses, is missing.Each component’s “TaishoDS Core” section says what else to load (“Also load”). The Button, for example, needs taisho.spinner.css. Or load taisho.full.css, which has everything.
The Modal or the Drawer doesn’t open when you press the buttonThe browser doesn’t support invoker commands (Safari before 26.2, Firefox before 144), or the button’s commandfor doesn’t match the dialog’s id.Check that command="show-modal" and commandfor="<dialog id>" are spelled right. In a browser without invoker commands, Core’s JS runs the commands: check that you loaded taisho.core.js, or open it with showModal() from your JS (see Browser support).
Tabs, accordions, the Select, or the Toast don’t respondCore’s <script> is missing, or it isn’t type="module".Add <script type="module" src="…/taisho.core.js"></script>. It initializes itself.

For which JS each component needs and how you find out what happens, see Behavior. For the browsers it supports, see Browser support.


Serving the JS from your own site

taisho.core.js is the base of the JS; the heavy components live in files next to it. What that means:

  • Copy the version’s folder, not one file. If you serve the JS yourself, taisho.core.js requests the heavy components’ modules from the files next to it: copy the whole /core/<version>/ folder or use taisho generate.
  • integrity covers only the file each tag links. The browser checks that file; the modules taisho.core.js loads later with import() aren’t part of the <script> hash. The lines carry crossorigin="anonymous" because a file from another origin is only hash-checked over CORS, and the CDN allows it.
  • Load a single taisho.core.js. If you use taisho generate with content and leave the package’s core.js next to taisho/taisho.core.js, every click is handled twice. Load only the generated one.
  • init() returns a promise that resolves once the page’s modules have loaded.