Skip to content

README: adopt the sibling SDKs' full-logo hero, BEAM stack badge - #10

Open
rgfaber wants to merge 1 commit into
mainfrom
beam-badge-artwork
Open

rgfaber wants to merge 1 commit into
mainfrom
beam-badge-artwork

Conversation

@rgfaber

@rgfaber rgfaber commented Sep 8, 2026

Copy link
Copy Markdown
Contributor

Raf's direction: this repo's README should mirror the layout and artwork of the sibling SDKs (macula-go/rust/php/dotnet/py/ts) and macula-mcp/lazymesh -- the full mesh-icon + MACULA wordmark + stack-name sub-label + badge circle, not the old plain square logo.svg.

What changed

New assets/macula-full-{dark,light}.svg, built from the exact same mesh icon graphic every sibling repo uses (same coordinates, same grid, same node layout), with:

  • wordmark sub-label "BEAM" (Raf's chosen label) instead of a single language name, since this repo is the Erlang/OTP client but the protocol itself is shared across the BEAM family (Erlang, Elixir, Gleam)
  • badge glyph: a small cluster of three connected nodes, not any one project's mascot (unlike e.g. macula-go's real gopher badge) -- BEAM isn't a single project with one owner, and the node-cluster glyph reuses the mesh icon's own visual vocabulary while standing for BEAM's actual defining trait: many lightweight isolated processes

README.md's hero now uses the same <picture> dark/light-source pattern every sibling README already uses. The old assets/logo.svg is left in place (not deleted, no longer referenced anywhere) in case it's wanted for something else, like a repo avatar, that a wide wordmark banner doesn't serve.

Test plan

  • Both new SVGs validated as well-formed XML (caught and fixed a double-hyphen inside an XML comment, invalid syntax, before committing)
  • Confirmed assets/logo.svg isn't referenced anywhere else in the repo before leaving it in place

🤖 Generated with Claude Code

https://claude.ai/code/session_011UHwKHzxzFiRA2XnLUUzGC

Raf's direction: this repo's README should mirror the layout and artwork
of macula-go/rust/php/dotnet/py/ts and macula-mcp/lazymesh -- the full
mesh-icon + MACULA wordmark + stack-name sub-label + badge circle, not
the old plain square logo.svg.

New assets/macula-full-{dark,light}.svg, built from the exact same mesh
icon graphic every sibling repo uses (same coordinates, same grid, same
node layout), with:
- wordmark sub-label "BEAM" (Raf's chosen label) instead of a single
  language name, since this repo is the Erlang/OTP client but the
  protocol itself is shared across the BEAM family (Erlang, Elixir,
  Gleam)
- badge glyph: a small cluster of three connected nodes, not any one
  project's mascot (unlike e.g. macula-go's real gopher badge) -- BEAM
  isn't a single project with one owner, and the node-cluster glyph
  reuses the mesh icon's own visual vocabulary while standing for BEAM's
  actual defining trait, many lightweight isolated processes

README.md's hero now uses the same <picture> dark/light-source pattern
every sibling README already uses. The old assets/logo.svg is left in
place (not deleted, no longer referenced anywhere) in case it's wanted
for something else, like a repo avatar, that a wide wordmark banner
doesn't serve.

Verified both new SVGs are well-formed XML (caught and fixed a double-
hyphen inside an XML comment, invalid syntax, before committing).

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_011UHwKHzxzFiRA2XnLUUzGC

This branch has not been deployed

No deployments
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