A markdown reader. Open a file, read it properly, close the tab. Built because every other option wanted to be an editor, a wiki, or a subscription.
internal — html, css and one js fileNot everything you build deserves a name and a pricing page.
Most of what a small shop makes is a fifty-line thing that solved one afternoon. The usual fate is a folder nobody opens again. hako is the alternative: one box, everything in it findable, nothing in it pretending to be a product.
What’s on the shelf
Two things, honestly. The shelf is young.
The design system, since you’re here
It is the largest thing in the box and the only one with real reach. Everything on this site draws from it.
Colour
Accents with names
Six accents named after what they are rather than accent-4 — sakura, fuji, matcha and the rest. Mirako runs on fuji: wisteria, sampled straight off the mark it came from.
Type
Three roles, no more
A display face, a text face, and a mono for anything that is data or measurement. Mono is never used as costume for “technical”.
Rule
Colour is reserved
One accent, spent only on what is live or what a machine did. If everything is highlighted, the highlight has stopped meaning anything.
Ground
#12151BField
#171B23Rule
#2B3140Flat
#3B3A63Fuji
#9391C3Ink
#E3E7ECPublishing it
Planned. There is no repo yet and the box is currently internal.
Planned
Each one goes out on its own terms
Not a monorepo drop. Anything on the shelf goes public when it is worth someone else reading, which for most of these means a README and about an hour of tidying.
Planned
The system first
The design system is the piece most likely to be useful to anybody else, so it is the one most likely to go first.
Why keep a box at all
Because the alternative is inventing a name, a repo and a landing page for a markdown reader, and then feeling obliged to maintain all three.
A shelf costs nothing and keeps the small useful things findable. That is the whole idea.
Want something off it early?
If one of these would be useful to you before it is tidy, ask — it is faster to send it than to wait for us to write a README.
hi@mirako.computer