Practical notes and questions about building websites, applications, APIs, databases, and CMS platforms.
A personal website can feel fast on a second visit for a simple reason: the browser may already have some of its files. But the same mechanism can also keep an old stylesheet alive, show yesterday's HTML, or place a personalized response where a shared cache …
Read article
A website can have an English page, an Indonesian translation, and a German translation, yet still leave an important question unanswered: …
Have you ever shared a carefully written article in a chat, only to see it arrive as a lonely blue URL or with an unrelated image? The page…
A favicon looks like one of the smallest details on a personal website. It may occupy only sixteen pixels in a browser tab, yet its absence…
Some readers arrive through a search engine, read one page, and leave. Others remember a sentence months later and return, only to discover…
Print Stylesheets for a Personal Website — Making Pages Useful on Paper A while ago, I printed one of my own articles and discovered that t…
A broken link feels small until it interrupts someone who was genuinely curious. They may have followed an old bookmark, mistyped a URL, or…
When I first built a personal website, publishing felt like placing a small sign in front of a house: the page existed, the address worked,…
When I first built a personal website, accessibility felt like a specialist subject I could postpone until the design was finished. The pag…
When I first added analytics to a personal website, the dashboard felt like a control room: maps, funnels, sessions, devices, and dozens of…
