Skip to content

docs: add social preview header to assets - #12

Merged
plusky merged 1 commit into
mainfrom
docs/social-preview-header
Jul 27, 2026
Merged

docs: add social preview header to assets#12
plusky merged 1 commit into
mainfrom
docs/social-preview-header

Conversation

@plusky

@plusky plusky commented Jul 27, 2026

Copy link
Copy Markdown
Owner

What

The GitHub social preview image now lives in the repository alongside the
vector source it is rendered from.

  • assets/social-header.svg — 1280×640 vector source: the assets/logo.svg
    mark (inlined, so the file stands alone and cannot drift from the logo), the
    bugwarden wordmark in slate #56656F with an amber #D89327 rule, and the
    tagline, on the #F5F3EA project background.
  • assets/social-header.png — the PNG rendered from that SVG, byte-for-byte
    reproducible with the headless-Chromium command recorded in the SVG header
    comment.

Notes

  • GitHub does not read the preview from the repository — it stays a one-time
    upload under Settings → Social preview. Keeping the artwork in-tree means
    the next person to change the tagline has the source instead of a flat PNG.
  • No README change: the logo is already embedded there, and the header is not
    meant to be shown twice.
  • Assets only; no code, tests, or guard behavior touched.

The 1280x640 image uploaded under Settings -> Social preview now lives in
the repository, together with the vector source it is rendered from, so it
can be regenerated when the tagline or the mark changes. The header inlines
assets/logo.svg so the two stay in sync by construction.

GitHub does not serve the social preview from the repository; a maintainer
uploads it once in the repository settings.
@plusky
plusky merged commit 629c4f5 into main Jul 27, 2026
10 checks passed
@plusky
plusky deleted the docs/social-preview-header branch July 27, 2026 15:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant