Skip to content

fix(docs): swap the navbar logo files so each one matches the mode it is used in - #2360

Merged
datlechin merged 1 commit into
mainfrom
fix/navbar-logo-modes
Aug 21, 2026
Merged

fix(docs): swap the navbar logo files so each one matches the mode it is used in#2360
datlechin merged 1 commit into
mainfrom
fix/navbar-logo-modes

Conversation

@datlechin

Copy link
Copy Markdown
Member

In dark mode the wordmark rendered dark ink on the dark navbar, so the header read as an icon and nothing else.

I got the mapping backwards in #2356. docs.json pointed logo.light at the file with light ink, on the theory that Mintlify's field names were inverted. They are not.

The markup is:

<img class="… block dark:hidden" src="…logo.light…">

block dark:hidden means shown by default and hidden in dark, which is light mode. So logo.light is the logo for light mode, exactly as the field docs say. I read the class as evidence of an inversion and wrote that into the PR body and the design spec. It was wrong.

Rather than swap the keys in docs.json and leave logo.light pointing at a file called dark.png, the two files are swapped so the names match the mode they serve:

File Mode Navbar Ink Contrast
logo/light.png light #FFFFFF #1F1B16 17.1:1
logo/dark.png dark #0E0D0D #F5F1EA 17.2:1

docs.json is unchanged. Only the two image files moved.

https://claude.ai/code/session_01TvGVLvwiH8ahw2wghtVs8s

@chatgpt-codex-connector

Copy link
Copy Markdown

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.

@datlechin
datlechin merged commit b11c198 into main Aug 21, 2026
10 checks passed
@datlechin
datlechin deleted the fix/navbar-logo-modes branch August 21, 2026 16:11
@mintlify

mintlify Bot commented Aug 21, 2026

Copy link
Copy Markdown

Preview deployment for your docs. Learn more about Mintlify Previews.

Project Status Preview Updated (UTC)
TablePro 🔴 Failed Aug 21, 2026, 6:15 PM

💡 Tip: Enable Workflows to automatically generate PRs for you.

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