
Tokens, type, and the decisions that stop visual drift
Design tokens are named decisions for color, type, and size. Visual drift starts when a screen pastes a one-off value instead of using the name.
By Hanabi
Author
Page 3

Design tokens are named decisions for color, type, and size. Visual drift starts when a screen pastes a one-off value instead of using the name.
By Hanabi

A design system for a team of five is type, color, space, and a few shared components. Keep it small enough that the team uses it while shipping the product.
By Hanabi

A custom website vs page builder choice is about what editors may change. Give them fields for those things. Keep the layout out of a free-form canvas.
By Hanabi

A website launch DNS checklist is unglamorous on purpose: a staging URL, a content freeze, DNS with a written rollback, and a person watching the first hour.
By Hanabi

Website code ownership means the repository, the domain, the analytics, and the content logins sit with you. A studio that keeps those is a dependency.
By Hanabi

A CMS for a small marketing team should match who edits, how often, and whether drafts matter. A tool the founder will not open is not a publishing system.
By Hanabi

TypeScript for websites is protection for the next person in the repo. It catches broken props and unsafe edits. It is not a badge to put in the footer.
By Hanabi

Prefers reduced motion means you ship two versions: the move you intended, and a still or instant version when someone asks the system for less motion.
By Hanabi

Website animation best practices come down to one test: motion should show a relationship or a state. Looping decoration that fights reading should go.
By Hanabi

Core Web Vitals explained: how fast the main content appears, how fast a tap responds, and whether the page jumps. The good thresholds are 2.5s, 200ms, and 0.1.
By Hanabi

A Next.js marketing website should give you a fast public site, a repository you own, and a clear place to edit content. The framework name is not the outcome.
By Hanabi

A fast marketing website earns the right to be clever. Paint the page quickly, then add the one motion that explains something. Slow decoration reads as carelessness.
By Hanabi

Rebrand when the offer or the audience changed, not when the team is bored of the old site. Keep the paths regulars already use while the surface changes.
By Hanabi

Brand and UX alignment means one idea survives from the homepage into the product. A quiet site and a loud app are an unfinished brand.
By Hanabi

Brand photography direction is a decision about subject, crop, and what you will not show. A young brand gets consistency from those limits, not from more pictures.
By Hanabi

Test a product name against the URL, the sentence a stranger will say, and the next product the name must still allow.
By Hanabi

A brand asset portal keeps logos, tokens, docs, and project updates findable after delivery, so the current file is obvious months later.
By Hanabi

Engineers open a short page of logo files, hex values, and type settings. A mood film stays closed in the middle of a sprint.
By Hanabi

Brand voice is three sentences you will say and three you will not. Apply them to the homepage, the button, and the error a customer actually reads.
By Hanabi

Brand guidelines for startups get used when they stay small: one type pair, a short color list, logo files, and three sentences of voice.
By Hanabi

A logo has to work small, on a dark surface, and beside type. The system around it is what keeps the next page from inventing a new palette.
By Hanabi

A startup brand can begin with a name if you settle the audience, the offer, and the feeling you refuse. Type, color, and one sentence do the rest.
By Hanabi

Accessible web design basics are contrast, focus, names, and reduced motion, treated as part of done. WCAG is the reference. A launch is not a certificate.
By Hanabi

Use Figma vs browser prototyping as a split: Figma for structure and options, the browser when type, motion, and real content decide the question.
By Hanabi