Skip to content

docs: keep the social preview image in the repo - #34

Merged
joseph3114 merged 2 commits into
masterfrom
docs/social-preview-asset
Jul 30, 2026
Merged

docs: keep the social preview image in the repo#34
joseph3114 merged 2 commits into
masterfrom
docs/social-preview-asset

Conversation

@joseph3114

Copy link
Copy Markdown
Owner

The 1280×640 social preview is uploaded to GitHub and live, but GitHub stores it on its own side — there is no API to read it back and no copy in the repository. Committing it means a future variant starts from the real file rather than a screenshot.

Lives at docs/assets/social-preview.png with a short README.md alongside recording two things that are easy to get wrong:

  • The two images behave completely differently. icon.png ships inside the .nupkg, so replacing it only reaches users in a new package version. The social preview lives on GitHub's side and updates every existing link the moment it is uploaded. Same-looking assets, opposite update semantics.
  • Neither uses Emma's branding, on purpose. Emma publishes no brand assets, and the README states this project is unaffiliated — shipping their marks would imply an endorsement that does not exist. The ES lettermark reads as EmmaSharper rather than Emma, which is the point: a bare E invites the misreading that this is a first-party client.

Also notes that uploading is UI-only (Settings → General → Social preview), since that surprised me when I went looking for an endpoint.

65 KB. No build or packaging impact — it sits under docs/, outside anything dotnet pack touches.

@joseph3114
joseph3114 merged commit 10bd2c3 into master Jul 30, 2026
4 checks passed
@joseph3114
joseph3114 deleted the docs/social-preview-asset branch July 30, 2026 15:50
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