Build Log
The Grape That Passed Every Automated Check
The favicon loaded, had valid dimensions, and produced no console error. It was also a grape. That small incident changed how visual assets are verified.
Validity is not fidelity
The site header used a beach umbrella, but the favicon had been generated from a different glyph. Automated checks could confirm that the file existed, decoded, and was linked correctly. None could determine that it represented the wrong object for the product.
The replacement set was generated from the exact Font Awesome umbrella-beach glyph used by the interface. SVG, PNG favicon sizes, Apple and Android icons, an ICO fallback, and the web manifest all derived from that same source.
The social card had its own failure
A previous preview card passed size checks while a calendar graphic overlapped the title. The repair introduced multiple platform crops and a visual review step at the actual card aspect ratio. A repeatable generator keeps text, mark, colour, and dimensions coordinated.
The lesson is broader than icons. Screenshots and previews are evidence about perception, while file audits are evidence about structure. A trustworthy visual release needs both.
What became standard
Brand assets must derive from the product’s real mark, and social cards must be inspected at their destination proportions. Automated checks catch absence and corruption; human review catches meaning, hierarchy, and accidental comedy.
Compare the mark in the site header, the identity on the About page, and the cards on this Build Log.