web delivery
metadata, sitemaps, social images, and proof of which commit production serves.
a site has to parse correctly for crawlers, feed readers, social cards, and language models. hraness sites get that from shared discovery and delivery packages.
this category documents that plumbing: typed next.js metadata, crawler policy, sitemap and feed generation, deterministic social images, and checks that confirm which commit production is serving.
lessons
- accept: text/markdown in productionstart here · content negotiation for agents without cloaking
- the app router metadata checklist, and where it silently breaks · typed metadata as a build-time contract
- crawler policy, sitemaps, and feeds that stay truthful · discovery is a contract, not a checklist
- og images as build artifacts: deterministic social cards, zero runtime · every shareable page gets a generated card
- deploy proofs: verifying the published artifact is the reviewed sourcesubscriber · binding the served page to the source commit
projects
- web-discovery · the shared metadata, sitemap, json-ld, and social-image primitives.
- vercel-delivery · proves which commit production is serving.
- aicharts · a sourced benchmark publication built on both packages.
- sleepyland · a sleep research publication with feeds and structured data.
by hraness · drafted with ai assistance