Framework
oxalorg/sakura avatar
oxalorg/sakura

sakura.css and the case for styling a page you did not write

:cherry_blossom: a minimal css framework/theme.

4,394 stars182 forksHTMLMIT

At a glance

What is it?
sakura.css is a classless CSS theme that restyles ordinary HTML through element selectors alone, aimed at people who want a readable page without touching markup. It covers markdown output, prototypes and legacy markup well, and it offers no hook of its own once you need real layout control.
Who is it for?
Adopt sakura.css when the markup is not yours to change: markdown output, a backend prototype, a small blog, a friend's site, a page full of 1990s tables. Do not adopt it for an application interface where you need named hooks, grid control or a component system, and do not adopt it if your site already has a design system, because element selectors will fight your rules without asking.
Can I use it commercially?
Yes. MIT is a permissive licence: you can use, modify and sell software built on it, as long as you keep its copyright and licence notices.
Is it still maintained?
Activity is slowing. The repository last received commits 7 months ago.
What is it written in?
Mainly HTML, according to GitHub's language statistics.

Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.

From daily snapshots

Star history

  • oxalorg/sakura4,394 ★ · +8
Star history
Repository2026-09-232026-11-15
oxalorg/sakura4.4k4.4k

8 Stars in the last 53 days, measured from the daily GitHub snapshot. Compare with other projects

Editorial analysis

Element selectors do the work, so no markup changes

Most CSS frameworks ask you to learn a vocabulary before you see anything. sakura.css asks for one stylesheet link and leaves your HTML alone, because every rule targets tags such as body, h1, blockquote or table rather than a class you would have to add. That inversion is the whole idea, and it is why the theme suits pages you did not author: HTML emitted by a markdown parser, a CMS export, a backend prototype, or a 1990s page someone found and wants to stop looking like a 1990s page. The author's stated case is exactly this: dropping the file into an existing page and having everything just work, with no recall of framework class names required. The cost of that design is that you have no handles. If a specific heading needs to be smaller, sakura.css gives you no class to target, and you fall back on a selector chain or on inline overrides, which is a worse place to be than having started with utility classes.

Theming is seven Sass variables, and only if you run the build

Colour is the one thing sakura.css lets you change without fighting element selectors, and it does it through variables. Themes are built from the scss folder, where a duotone pair ($color-blossom as the stark accent, $color-fade as the softer tone) plus $color-bg, $color-bg-alt, $color-text and $font-size-base cover most of what a small site needs. Setting $color-blossom to #338618 turns the accent green. The catch is who compiles that. A CDN visitor, the person the README calls its recommended install path, never sees a build step and cannot invent a theme: they get the palette that shipped. Themes compiled ahead of time sit in the css folder of the repository. Theming is therefore not a runtime knob. It is a fork of the stylesheet plus a Sass toolchain.

The dark mode snippet switches CDNs and drops the print path

Dark mode is two stylesheet links with a prefers-color-scheme media query, and nothing more. Copy it literally and the page loads sakura.css from unpkg while the documented main install loads from jsdelivr, so a project that followed the install instructions and then added dark mode ends up pulling two hosts and two cached copies of the same file. Each link is also scoped to media="screen", which is the default you almost certainly did not want to type: print output loses the theme entirely because the first rule no longer applies on paper. The snippet comes with no language tag in the README, which is a small tell that it was pasted rather than composed. None of this makes the approach wrong. It does mean the dark mode path is the least finished corner of an otherwise two-line install.

One stylesheet link, and the exact command that gets it there

The shortest useful setup is a single tag in your head, served from jsDelivr, which is what the README marks as recommended:

html
<link rel="stylesheet" href="https://cdn.jsdelivr.net/npm/sakura.css/css/sakura.css" type="text/css">

Drop that into an existing page and nothing else changes. To vendor the file instead, the project gives a one line wget against the master branch:

bash
wget "https://raw.githubusercontent.com/oxalorg/sakura/master/css/sakura.css"

Once it sits next to your HTML, the link is local and needs no host:

html
<link rel="stylesheet" href="sakura.css" type="text/css">

For anyone with a package manager, the published name is sakura.css, not sakura:

bash
npm install sakura.css

Pick one of the four paths and skip the rest. The repository also keeps a local preview page in test.html.

The npm package ships css and scss but not src, so building a theme means a clone

package.json is short enough to read in full, and two details matter. The published files array lists css, scss and package.json, so an installed copy has no src directory, no preview.mjs and no release.sh. If you install from npm hoping to run the repository's own tooling, you have none of it. Second, the scripts block assumes that tooling: scss compiles scss to css with sass --no-source-map, scss:watch does the same in a loop, and build calls the first of those. Both need devDependencies that an installed package does not carry into your node_modules. Contributors work from a git clone with vite ^6.0.0 and sass ~1.53.0 pinned in devDependencies; consumers get a prebuilt stylesheet and a source folder. Those are two different products sharing a version number, and the package description does not tell you which one you have.

Where it breaks: any layout you have to name

Here is the concrete failure mode. A classless theme can restyle a document but cannot express a two column layout, a sticky sidebar or a card grid, because none of those exist without a class or a wrapper the theme does not target. The moment a page stops being a document and becomes an interface, you start writing your own CSS beside sakura.css, and now you maintain two stylesheets and decide who wins on every element they both mention. Normalization is offered as optional but recommended, which means the page's baseline box model depends on whether normalize.css loaded first; forget the order and margins change under you. There is a second, quieter limit: the stylesheet targets bare tags, so a page that already has opinions, a CMS theme or a design system of its own, gets its rules overwritten by specificity rules the author chose rather than by anything you asked for.

Where the alternative sits: normalize.css and hand-written CSS

normalize.css is the honest comparison, and the README already points at it. It is a reset: it makes browsers agree on defaults and stops there, leaving every visual decision to you. sakura.css does the opposite, shipping its own type scale, spacing and two tone colour scheme, so you spend no design decisions and get a specific look you did not choose. Pick the reset when you have a design system and a build pipeline and want a predictable floor. Pick sakura.css when you have no design decisions to make and a page you cannot edit. The class is where the line falls, and any framework with named utilities is on the other side of it from sakura.css, giving you control it deliberately withholds.

Editorial conclusion

Adopt sakura.css when the markup is not yours to change: markdown output, a backend prototype, a small blog, a friend's site, a page full of 1990s tables. Do not adopt it for an application interface where you need named hooks, grid control or a component system, and do not adopt it if your site already has a design system, because element selectors will fight your rules without asking. Version 1.5.1 shipped on 2025-06-24 and the last push was on 2026-04-07, so pin the version rather than tracking master. First, open css/sakura.css and read which element selectors it sets, because that file, not the README, decides whether your existing rules survive the drop-in.

Frequently asked questions

How do I install sakura.css?

Add a stylesheet link to your head pointing at https://cdn.jsdelivr.net/npm/sakura.css/css/sakura.css, or install the npm package named sakura.css and link the local file. A wget of the raw file from the master branch also works if you prefer to vendor it.

Does sakura.css require adding classes to my HTML?

No. The theme is classless and styles plain elements, which is why it can restyle existing or generated HTML without editing the markup. The consequence is that you have no named hook to target a single element later.

How do I make my own theme with sakura.css?

Override the Sass variables such as $color-blossom, $color-fade, $color-bg, $color-bg-alt, $color-text and $font-size-base in a copy of the scss file, then compile it. That requires Sass, so themes are built ahead of time and shipped as CSS rather than chosen at runtime.

How does sakura.css handle dark mode?

It links a second stylesheet, sakura-dark.css, with media="screen and (prefers-color-scheme: dark)" so the browser picks it when the system asks for a dark colour scheme. The README's snippet scopes both links to media="screen" and loads them from unpkg rather than the jsdelivr path used in the install instructions.

What does the npm sakura.css package contain?

The published files array lists css, scss and package.json, with css/sakura.css as the entry point. The repository's own tooling, including the vite preview and release script, is not part of the package and only exists in a clone.

Official sources

  1. License: MIT
  2. oxalorg/sakura on GitHub
  3. Project website
  4. README
  5. Releases
Add this badge to your README

If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.

Add this badge to your README

markdown
[![Hysen Labs](https://hysenlabs.com/badge/oxalorg-sakura.svg)](https://hysenlabs.com/projects/oxalorg-sakura)

Star history chart for your README

markdown
[![Star history](https://hysenlabs.com/chart/oxalorg-sakura.svg)](https://hysenlabs.com/projects/oxalorg-sakura)

Was this useful?