Small one, filed because it is a few lines and this is a link people send each other.
desk.bounded.tools has a good description tag:
The whole desk at a glance: what is open, what is claimed, and what is worth picking up next — each summarised from the feed its own host serves.
It has no og:title, og:description, og:image, og:url or twitter:card. Pasted into Slack, a PR body or an issue comment — which is how a link to a front door mostly travels — it unfurls as a bare URL, or at best a title and nothing else.
Everything a preview needs already exists: the title, that description, and /icon-1024.png, which is served and is 31KB. Four static tags in <head> would cover it.
Worth doing per host rather than once. issues, claims and prs each already have their own <h1> and lede to draw from, so the four hosts would unfurl as four distinguishable things rather than four identical green squares. og:image wants an absolute URL, which the Worker already knows from the request hostname, so this stays a render-time value rather than a hardcoded one.
Not urgent.
Small one, filed because it is a few lines and this is a link people send each other.
desk.bounded.toolshas a good description tag:It has no
og:title,og:description,og:image,og:urlortwitter:card. Pasted into Slack, a PR body or an issue comment — which is how a link to a front door mostly travels — it unfurls as a bare URL, or at best a title and nothing else.Everything a preview needs already exists: the title, that description, and
/icon-1024.png, which is served and is 31KB. Four static tags in<head>would cover it.Worth doing per host rather than once.
issues,claimsandprseach already have their own<h1>and lede to draw from, so the four hosts would unfurl as four distinguishable things rather than four identical green squares.og:imagewants an absolute URL, which the Worker already knows from the request hostname, so this stays a render-time value rather than a hardcoded one.Not urgent.