The Favicon.now Blog
Working notes from the icon bench: what browsers actually request, what breaks after a deploy, and what changed in the tools since the last release.
The first post is on its way
Posts are released here on a fixed schedule, one at a time, so each one gets a proper edit before the next arrives. Nothing has reached its publication date yet, so this page is currently a promise rather than an archive.
The sourced reference library already covers the subject end to end, from icon sizes and file formats through platform setup to the reasons a tab still shows a blank square.
What gets published on this blog
The blog is the shorter, faster companion to the reference library. A guide answers a question completely and gets revisited whenever the underlying documentation moves. A blog post is narrower on purpose. It takes one situation, shows what happened, and stops.
Three things end up here. The first is observed browser behaviour: which icon a browser actually picked in a given test, what it requested, and in what order. The second is deployment reality: proxies, caches, catch-all routes, and the other ordinary infrastructure that turns a correct icon package into a broken tab. The third is release notes for the tools on this site.
Every post carries a publication date and the same editorial rules as the rest of the site. Claims are scoped to what was tested. Where a post rests on a specification or a vendor document, that source is linked in the body rather than paraphrased and left unattributed.
How the schedule works
Posts publish one at a time, spaced several days apart, and a post stays invisible until its date arrives. There is no backlog dump: even when several pieces are ready, they queue and appear in order. That keeps the archive readable and gives each piece its own moment on the index above.
- One post per release slot, oldest queued piece first.
- Dated on publication, and re-dated only when the copy is materially revised.
- Listed in the sitemap the moment it becomes reachable, never before.
How it relates to the guides
Use the blog for the specific, and the library for the complete. If you are shipping an icon package today, start with the guides. If you want to know why a particular browser did something surprising last week, the blog is the better read.
The two link to each other freely. A post that touches sizing points at the sizing guide instead of restating it, and the guides link back when a post documents a case worth seeing.
Where to go next
If something on your own site is broken right now, skip the reading. Run the live checker against the page, look at what is actually served, then come back for the explanation.
From favicon idea to verified deployment
Follow one clear path through creation, inspection, installation, and troubleshooting.