Skip to content

Nova's product page said "(no logo)", so here is the logo - #3147

Merged
Flotapponnier merged 1 commit into
devfrom
feat/nova-logo
Oct 22, 2026
Merged

Flotapponnier merged 1 commit into
devfrom
feat/nova-logo

Conversation

@Flotapponnier

Copy link
Copy Markdown
Collaborator

/products/nova-markets has been live since the release, built automatically
from the registry entry, and rendering Nova (no logo) as its alt text
because no file backed it.

Where the logo came from

Nova publishes no logo file. /logo.svg, /logo.png, /favicon.svg,
/icon.svg, /apple-icon.png and four paths under assets/ all 404, and
their assets/logos/ directory holds only the third-party marks they display
(hyperbeat, hyperliquid, kinetiq).

The mark is inlined in their homepage instead, twice, at 44×33 and 32×24
on the same viewBox="37.5 80 325 240", three paths. The larger one is taken
here with width and height stripped so it scales to whatever box the site
gives it.

The part that matters more than registering it

All three paths are fill="#F3F3F3" on transparent. provider-logo.tsx
names this case in its own comment:

//   • white-on-transparent → invisible on white light-mode page → dark chip

So it goes in NEEDS_DARK_CHIP, not just the manifest. Registering the file
alone would have shipped a logo nobody can see on the default
var(--color-paper) ground, which looks exactly like the problem this is
meant to fix.

Checked rather than assumed

Rendered at 300px: a four-pointed star inside a lens shape, clean at 120px on
#0f172a and nearly invisible on #faf9f7. That is the chip decision
confirmed by looking, not inferred from the hex value.

Checks

tsc --noEmit clean. eslint 0 errors. bun test 732 pass. pnpm validate
253 specs valid. The SVG parses as well-formed XML.

🤖 Generated with Claude Code

/products/nova-markets has been live since the release, built from the
registry entry, and rendering its alt text because no file backed it.

Nova publishes no logo file: /logo.svg, /logo.png, /favicon.svg, /icon.svg,
/apple-icon.png and four paths under assets/ all 404, and that assets/logos
directory holds only the third-party marks they display (hyperbeat,
hyperliquid, kinetiq). The mark is inlined twice in their homepage instead, at
44x33 and 32x24 on the same 325x240 viewBox, three paths. The larger one is
taken here with its width and height stripped so it scales to whatever box
the site gives it.

It also goes in NEEDS_DARK_CHIP, which matters more than registering it. All
three paths are #F3F3F3 on transparent, and provider-logo.tsx names that case
exactly: "white-on-transparent -> invisible on white light-mode page -> dark
chip". Registering the file alone would have shipped a logo nobody can see on
the default paper ground, which is indistinguishable from the problem this
commit is fixing.

Checked by rendering it: a four-pointed star inside a lens, legible at 120px
on #0f172a and nearly gone on #faf9f7, which is the chip decision confirmed
rather than assumed.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
@Flotapponnier
Flotapponnier merged commit 37e9aaf into dev Oct 22, 2026
2 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.

1 participant