人生到處知何似,應似飛鴻踏雪泥

Casual note on document typogr…

Tw93 · · Products

Casual note on document typography, from shipping Kami lately.

We have been deleting a lot of decoration. That cleanup taught me more about simple product design than adding features did.

Typography exists so people can read and understand. Not to look clever. Not for the big-company PPT vibe. Content comes first. If you bend a good idea just to fit a template, or pad empty slots with filler, you lose the real voice.

Keep type, tracking, leading, size, spacing, and radius calm enough that the page feels steady. Then ask the harder questions: who is reading, what must be said first, what is the core, what should they take away. Only then turn that into a clear page: where to start, what is important, what is secondary.

Same for charts and images. A chart that shows a pattern, or a picture that explains the point, beats a wall of text. A pretty asset that says nothing is noise.

My rule is Occam for layout: do not add a line, a box, or a fill unless it helps the reader understand something. If size, spacing, and alignment already carry the relationship, stop. Keep weight or color when they genuinely help reading. Minimal does not mean empty.

Recent Kami releases were mostly that kind of work. Side ticks next to titles are gone. Blue bars on callouts are gone. Soft shadows that did nothing are gone. Table rules got thinner and quieter. Spacing opened up. We also added lint checks so agents do not quietly put the clutter back.

I want Kami to handle those boring layout details, so you can spend the energy on what you actually mean. Good content deserves a good layout.