For images to load in production and preview:

1. GITHUB_ACCESS_TOKEN – Required for journal/project images (asset-proxy fetches from the private db repo). Set for both Production and Preview in Vercel project settings.

2. GIT_USERNAME + GIT_ACCESS_TOKEN – Optional but recommended for the build. Used by vercel-install.sh to clone the db repo. If missing and the repo is private, move-assets will copy 0 files; images will still load via the asset-proxy if GITHUB_ACCESS_TOKEN is set.

3. Regenerate feed – After deploying, run npm run generate-feed (or npm run update-feed; both use the same pipeline) and commit public/data/feed.json so Bluesky post images appear in the feed.

Logs: title (required), categories, tags, type, publishedAt, published; optional heroImage / heroImagePoster / first image in body for cards (same rules as projects, but wikilinks resolve like journal/log MarkdownContent — assets/… only, no projects/ prefix) Projects: title (required), categories, publishedAt, url, heroImage (path/URL to card image), heroImagePoster (optional static image when heroImage is a GIF — otherwise first non-GIF image in the body is used as the poster) Journals: title (required), categories, tags, type, publishedAt, published

Project card images: heroImage is used when set (valid image path/URL). If omitted, the first image in the markdown body is used (![[…]] or ![]()). Animated GIFs show a poster until hover; set heroImagePoster to pick the still explicitly.