Hanabi journal

Clear thinking for better digital products.

Practical notes on design, engineering, brand systems, and the choices that make digital work feel simple.

September 26, 2026Studio Practice

A founder's map from brand to site to product

Move from a clear identity, to a site that explains it, to a product interface that behaves like the same idea. Keep one sentence stable across all three.

By Hanabi

A workshop where one person points at colorful sticky notes while others sit with laptops, the kind of review that belongs in the weeks after launch.

September 26, 2026Websites

The first 90 days after a site launches

After launch, watch the queries, fix lines people misunderstand, and publish into the real gaps. Give the new site a quarter before you redesign out of nerves.

By Hanabi

Hands typing on a laptop at a wooden desk near a window, a review of the few numbers that show whether the site earned a conversation.

September 26, 2026Websites

Measure calls booked, not vanity traffic

Judge a company site by intro calls or emails from the right buyers. Sessions and pageviews are context for that number, not a score on their own.

By Hanabi

Skyscrapers photographed from street level against a pale sky, a scale a small site should not try to imitate when it says who it is for.

September 26, 2026Websites

Niche positioning on a small site

A small site should name its buyer and its offer on the first screen. A specific position is easier to prove than a claim that you do everything.

By Hanabi

A bright office window ledge with a laptop, a closed notebook, white chairs, and a tall indoor tree, a calm desk for deciding which posts a product needs.

September 26, 2026Websites

Planning a blog that supports a product

Plan each post around a search a buyer already has, then point it at the product or service. Unrelated essays do not carry the product.

By Hanabi

A silver laptop open to a code editor on a white desk, with a monitor, mug, and phone behind it, where a page and the data that describes it are written together.

September 26, 2026Engineering

Schema markup for a company site, in plain language

Schema for a company site should describe the organization, the articles, and any FAQ people can actually read. Clear writing still does the work.

By Hanabi

A person gesturing in a meeting, with a laptop showing a colorful layout, a notebook, and a phone on the table, the kind of working session a case study should explain.

September 26, 2026Studio Practice

Case-study pages that do more than show screenshots

A case study should name the constraint, the decision, and what changed in the work. Screenshots illustrate those sentences. They are not the whole piece.

By Hanabi

A close view of a fountain pen writing on lined paper, the slow choice of a title the page will have to keep.

September 26, 2026Websites

Titles and descriptions that earn the click

A title is a promise the page keeps. Write a concise, accurate title and a description that states the point, then make the visible heading agree.

By Hanabi

A hand pinning string between printed mobile screens on a wall, a physical map of how one screen leads to the next.

September 26, 2026Websites

Internal linking for a small site

On a small site, link from the sentence that needs the next page. A few specific links do more than a footer that lists every URL.

By Hanabi

Hands typing on a laptop at a wooden desk near a window, the quiet work of writing answers a buyer could actually use.

September 26, 2026Websites

FAQ sections that help buyers and search engines

FAQ sections earn their place when they answer questions buyers already ask, in text those buyers can read. Markup should describe that same visible text.

By Hanabi