Our 12-package starter for every new Next.js engagement at Hanova.
The exact dependency list we add to every greenfield project, the rationale behind each choice and the libraries we deliberately keep out of every stack — and why.
A working manifesto from the bench. Essays on the architectures, methodologies and operating principles we use on every engagement — written by the specialists doing the work.
We learned this on three consecutive engagements: when an editorial team cannot publish without an engineer, the entire product loses operational momentum. The CMS-first architecture we now adopt by default — the trade-offs, the failure modes and the precise stack choices behind it.
The exact dependency list we add to every greenfield project, the rationale behind each choice and the libraries we deliberately keep out of every stack — and why.
Eighteen months of measured experiments across ChatGPT, Gemini and Perplexity — what triggers a brand citation, what gets paraphrased away, and how to structure content so the LLMs name you.
Hourly invoicing creates misaligned incentives for client and vendor alike. The contract architecture we use instead — what we sign, how we re-scope, and the language that prevents disputes.
Three small interface decisions made one of our authentication forms 18% easier to complete for non-English-first users. The research that justified them and the rules we now keep.
Why we stopped recommending Google Analytics in 2024, the two-hour migration we now standardise on, and the privacy posture it gives every client by default.
Feature-phone constraints forced Kenya's most successful API into a shape Silicon Valley still hasn't reproduced — a study in operational pragmatism over architectural elegance.
One email when a new long-form post lands — typically every two to three weeks. No marketing sequences, no upsell. Unsubscribe at any time.