Voice

Hanji's visual language is restraint, and its voice is the same restraint carried into words. Here is how it speaks, and why.

Plain

We say the thing. No jargon standing in for a plain word, no sentence that could have come from any product on any landing page. If a claim can be made in a shorter word, it is. The reader is a peer, a working engineer or designer who can smell marketing from a mile off, and they get talked to like one.

With an edge

Plain does not mean bland. Hanji takes positions. Git is the store, and a backup target is not good enough. An agent is a reader, not a chat box. The day you charge someone for the right to write down what they know is the day you have become the thing this was built against. The voice is willing to be a little sharp, because a product with no point of view is not worth reading about.

Honest about limits

This is the load-bearing one. When a feature is not built, we say so. When product privacy is real but storage privacy is not - the bytes stay plaintext in your git, readable by whoever holds the repository - the page says exactly that. A benchmark we have not run honestly is marked as not run, not rounded up. It is the Principles page applied to the writing: a promise we cannot keep is worse than no promise, so we do not make it.

In practice

A page reads like a person wrote it, because one did. Sentences vary. Some run long and accumulating, some are three words. There is a wink now and then, and a number wherever a claim can carry one. What there never is: a summary that restates what you just read, or a conclusion that adds nothing. When the point is made, the page stops.

Read The visual language for the same restraint in pixels.