Blog archive, page 2

A close view of a fountain pen writing on lined paper, a sentence slow enough that another person could quote it without guessing.

September 26, 2026Websites

Writing pages that AI search engines can cite

Write pages an AI answer can quote: define the term first, attach a real source to any number, and skip keyword stuffing. The GEO study measured a cost for stuffing.

By Hanabi

A dim desk with an iMac showing a code editor beside a portfolio page, a second monitor with a mountain wallpaper, and a lit lamp. The page on screen is what search has to understand.

September 26, 2026Websites

Make the site search-ready before decorating it

A new site is search-ready when titles, headings, speed, and a plain sentence say what the company is. Decoration on a vague page does not earn the click.

By Hanabi

A workshop where one person points at colorful sticky notes while others sit with laptops, the room where access and ownership should be settled early.

September 26, 2026Studio Practice

Questions to ask about performance, access, and ownership

Ask who writes, who builds, what you will own, how reduced motion is handled, and how the site stays within Core Web Vitals. Specifics are the answers to trust.

By Hanabi

A dim desk with an iMac showing a code editor beside a portfolio page, a second monitor with a mountain wallpaper, and a lit lamp. The pair of screens asks what the work is and whether it was built.

September 26, 2026Studio Practice

How to read a studio portfolio

Evaluate a studio portfolio by the problem, the restraint, and whether they built the work. A gallery of screenshots with no decision is decoration.

By Hanabi

A person in a purple shirt typing on a bright blue laptop at a round table, writing a reply while the question is still the same day.

September 26, 2026Studio Practice

What a same-day response should mean

A same-day response is a human email that names the next step, sent the day you write. The design itself stays on the project schedule.

By Hanabi

A long, quiet office corridor with glass rooms, a teal sofa, and a dark kitchen, a settled workplace for work that continues after a launch.

September 26, 2026Studio Practice

Fixed project or ongoing partnership

Choose a fixed project when the launch has an edge you can describe. Choose an ongoing partnership when the product keeps changing and you want the same people on it.

By Hanabi

Hands sketching a user-flow diagram labeled user goals, the sheet a round of design feedback should stay attached to.

September 26, 2026Studio Practice

How to give design feedback without restarting the project

Give feedback against the goal: clearer, more serious, or easier to scan. Redesigning in the margin restarts the work unless the goal itself was wrong.

By Hanabi

A hand pinning string between printed mobile screens on a wall, planning that depends on an approver and on access already being in place.

September 26, 2026Studio Practice

What to have ready before kickoff

Before kickoff, gather the accounts, a rough offer, access to the current site, and the name of the person who can approve. Missing access spends the first week on waiting.

By Hanabi

A person gesturing in a meeting, with a laptop showing a colorful layout, a notebook, and a phone on the table, a review where working habits become visible.

September 26, 2026Studio Practice

Quality, clean code, flexibility, speed, and communication

Quality, clean code, flexibility, speed, and communication are behaviors you can see on a project. Each one shows up in the work, the repository, or the way a change is handled.

By Hanabi

Five people working on laptops around a wooden table, a shared session where a build's decisions can be written down in one place.

September 26, 2026Studio Practice

Communication habits that keep a build on track

Keep a build on track with one shared channel, decisions written down, and a cadence both sides keep. Clear updates and honest timelines prevent late surprises.

By Hanabi