
How to keep a site editable without a page-builder mess
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
Hanabi journal
Page 6

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