feat(standard-site): add document coverImage from blog header#9
Merged
Conversation
This was referenced Jul 22, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Uploads each blog post's optimized header image as the
coverImageblob on itssite.standard.documentrecord, so posts carry a thumbnail/cover in the standard.site / AT Protocol network.How
DocumentSourcegains an optionaldistDirso the publisher can locate the built, WebP-optimized header atdist/<contentType>/<slug>/<header.url>.build.tspassesdistDirfor theblogsource. Material chapters have no headers → source omitsdistDir, no cover uploaded.uploadBlob→ setrecord.coverImage.coverImageis content-addressed, so re-runs with an unchanged image reuse the same CID (idempotent, matches the existing rkey-stable upsert model).Safety
.gif/video header), or oversized (>1MB, per the lexicon guidance) image warns and is skipped — never throws. Publishing already runs inside a non-fatal try/catch with transient-retry.STANDARD_SITE_DRY_RUN=true) logs the intended cover upload without calling the PDS.Verification
tsc --noEmitclean; full test suite green (262 tests).Docs updated in
STANDARD-SITE.md. Rolls out to both consuming sites via a follow-up submodule bump.