Skip to content

feat(web): update Elixir and Erlang logos with dark theme support - #296

Merged
thiagoesteves merged 2 commits into
mainfrom
thiagoesteves/theme-aware-elixir-erlang-logos
Aug 14, 2026
Merged

feat(web): update Elixir and Erlang logos with dark theme support#296
thiagoesteves merged 2 commits into
mainfrom
thiagoesteves/theme-aware-elixir-erlang-logos

Conversation

@thiagoesteves

@thiagoesteves thiagoesteves commented Aug 13, 2026

Copy link
Copy Markdown
Owner

Summary

  • Replace the Elixir logo with the official Elixir-lang drop (rendered from elixir-lang.github.com), stored as elixir.ico/elixir.png (light) and elixir-dark.ico/elixir-dark.png (lightness boosted +0.15 in HSL space)
  • Regenerate the Erlang logo from the existing erlang-otp.png as erlang.ico (light) and erlang-dark.ico (dark "rlang" text recolored to bright red so the full logo reads on dark backgrounds)
  • Add .elixir-logo and .erlang-logo CSS classes that swap the image source via content: url(...) based on [data-theme="dark"] and [data-theme="night"]
  • Update system_bar.ex and application_card.ex to use the new classes instead of fixed src attributes
  • Add .gitignore negation rules so elixir-dark.* and erlang-dark.ico are tracked despite the existing elixir-* / erlang-* digest patterns

Risk assessment

Impact: the system bar and application cards show crisper, official logos that remain visible on both light and dark themes. No functional change.

Blast radius: only apps/deployex_web static images, app.css, and the two LiveView components (system_bar, application_card). No business logic, no other apps touched.

Regression risk: low. The change is purely visual - image assets and CSS class swaps. No data flow, state, or config changes.

Rollback: revert this commit. The previous elixir.ico, elixir.png, and erlang.ico are restored from git history.

Test plan

  • mix format --check-formatted on changed files
  • mix credo --strict on changed files
  • Start the server and verify the Elixir and Erlang logos render in the system bar on light theme
  • Toggle to dark theme and verify the logos swap to the brighter variants
  • Toggle to night theme and verify the same
  • Verify the application cards show the correct logos for Elixir and Erlang apps

🤖 Generated with Devin (GLM-5.2 High)

Replace the Elixir and Erlang logos with their official versions and add
a brighter variant for each that swaps in automatically on dark and
night themes via CSS `content` rules keyed on `data-theme`.

- Elixir: official drop logo rendered from elixir-lang.github.com,
  stored as elixir.ico/elixir.png (light) and elixir-dark.ico/elixir-dark.png
  (lightness boosted +0.15 in HSL space)
- Erlang: regenerated from the existing erlang-otp.png as erlang.ico
  (light) and erlang-dark.ico (dark "rlang" text recolored to bright red
  so the full logo reads on dark backgrounds)
- CSS: .elixir-logo and .erlang-logo classes swap the image source
  based on [data-theme="dark"] and [data-theme="night"]
- .gitignore: negation rules so elixir-dark.* and erlang-dark.ico are
  tracked despite the existing elixir-* / erlang-* digest patterns

Impact: the system bar and application cards show crisper, official
logos that remain visible on both light and dark themes.

Blast radius: only apps/deployex_web static images, CSS, and the two
LiveView components (system_bar, application_card). No business logic,
no other apps touched.

Regression risk: low. The change is purely visual - image assets and
CSS class swaps. No data flow, state, or config changes.

Rollback: revert this commit. The previous elixir.ico, elixir.png, and
erlang.ico are restored from git history.
@thiagoesteves
thiagoesteves force-pushed the thiagoesteves/theme-aware-elixir-erlang-logos branch from 504bd88 to 3eff756 Compare August 13, 2026 23:36
@thiagoesteves thiagoesteves self-assigned this Aug 14, 2026
@thiagoesteves
thiagoesteves merged commit 75ab7f7 into main Aug 14, 2026
3 checks passed
@thiagoesteves
thiagoesteves deleted the thiagoesteves/theme-aware-elixir-erlang-logos branch August 14, 2026 12:12
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