Skip to content

chore: add Deepgram brand icon and social preview - #139

Merged
GregHolmes merged 2 commits into
mainfrom
gh/rebrand-icon-2026-10-29
Oct 29, 2026
Merged

GregHolmes merged 2 commits into
mainfrom
gh/rebrand-icon-2026-10-29

Conversation

@GregHolmes

Copy link
Copy Markdown
Collaborator

Part of the rebrand. Tracked on Naomi's "Rebrand Asks" list as "Add the icon to our Java SDK", due 2026-10-29.

Why this differs from the NuGet ask

The sibling item on that list is "Update the icon on our four NuGet packages", which is a <PackageIcon> change in each .csproj. There is no Maven Central equivalent. The POM schema has no icon or logo element, and the Central artifact page renders only name, description, url, licenses, developers and scm — all of which pom.xml already sets correctly. So nothing here lands on the registry; the mark goes on the GitHub surfaces instead.

That is also why the list says "Add" for Java and "Update" for NuGet: this repo had no image assets at all.

Changes

  • .github/images/dg_logo.png — the new purple D mark, 400×400, from the rebrand asset shared in #team-devrel-internal
  • .github/images/social-preview.png — 1280×640 card, set in the new brand font (Work Sans) on the brand near-black
  • README.md — logo above the title

.github/ is already a permanently frozen entry in .fernignore, so no freeze changes are needed.

Manual step after merge

GitHub does not read the social preview from the tree. It has to be uploaded once at Settings → General → Social preview. The PNG is committed so it is versioned and reproducible.

Verification

  • ReadmeSnippetsCompileTest passes
  • spotless targets Java sources only and is unaffected by this change

Note for review

The mark is the 400×400 JPEG from the Slack thread, which looks like the social-avatar export rather than an official brand-pack asset. Fine at README size; if there is an SVG or higher-res PNG in the rebrand pack, swapping it is a one-file change.

🤖 Generated with Claude Code

Part of the rebrand (Naomi's "Rebrand Asks" list, due 2026-10-29).

Maven Central has no package-icon field — the POM schema has no icon or
logo element, and the Central artifact page renders only name, description,
url, licenses, developers and scm. So unlike the NuGet packages there is no
registry icon to update here; the mark lands on the GitHub surfaces instead.

- .github/images/dg_logo.png: new purple D mark (400x400), sourced from the
  rebrand asset Naomi shared
- .github/images/social-preview.png: 1280x640 card for the repo's social
  preview, set in repo Settings (not read from the tree)
- README.md: logo above the title

.github/ is already listed in .fernignore, so no freeze changes are needed.

@dg-coreylweathers dg-coreylweathers left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good. Checked the assets:

  • dg_logo.png is a real PNG (400x400, no alpha), not a JPEG with a .png name, so no renderer weirdness. Fuchsia matches the brand #E042FF. Solid dark tile reads fine on both light and dark GitHub themes.
  • README header renders, relative path resolves, and ReadmeSnippetsCompileTest only reads java code blocks so the

    swap can't touch it. Nothing in the repo links to #deepgram-java-sdk either.

  • Social card is 1280x640, 228 KB, copy spelled right, Work Sans.
  • chore: is right, no release needed.

Two small things, neither blocking:

  • The brand pack has an official transparent Fuchsia symbol (SVG + PNGs up to 2084px) if you want to swap out the Slack export. Not visible at 44px, so totally optional.
  • PR body still says "logo above the title" and "JPEG". It's inline now and the file's a PNG. Worth a quick edit so the merge record matches.

Don't forget the Settings > Social preview upload after merge.

@GregHolmes
GregHolmes merged commit ed8c4eb into main Oct 29, 2026
8 checks passed
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.

2 participants