Skip to content

feat: add Franklin Desktop download link - #23

Open
KillerQueen-Z wants to merge 1 commit into
masterfrom
feat/desktop-download-link
Open

feat: add Franklin Desktop download link#23
KillerQueen-Z wants to merge 1 commit into
masterfrom
feat/desktop-download-link

Conversation

@KillerQueen-Z

Copy link
Copy Markdown
Collaborator

Summary

  • add a visible Franklin Desktop download link to desktop and mobile navigation
  • point to the latest GitHub release so macOS and Windows assets stay current
  • localize the navigation label across all 13 supported locales

Validation

  • git diff --check
  • confirmed the latest public Desktop release contains macOS arm64 and Windows x64 installers
  • full TypeScript/ESLint validation is deferred to CI because both local processes stalled against the shared dependency tree

Ready for review.

@VickyXAI VickyXAI 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.

Pre-landing review — 1 blocker, 5 informational

🔴 Blocker

src/components/Header.tsx:10 — the download link 404s for every visitor. DESKTOP_RELEASES_URL points to github.com/BlockRunAI/franklin-desktop/releases/latest, but that repo is currently private — anonymous visitors get a GitHub 404. The v0.1.2 release itself is ready (macOS arm64 .dmg + Windows .exe), so this resolves once the repo goes public, but until then this ships a prominent gold nav CTA in 13 locales that dead-ends with no error and no telemetry. Holding the merge until the repo is public (or the link goes through a site-owned redirect like /download).

Informational

  1. src/app/globals.css:263!important masks a specificity trap and inverts the nav hierarchy. .site-header .nav-link / .site-header-paper .nav-link (specificity 0,2,0) beat a bare class — that's why !important was needed, and it's also why the existing .nav-link-try { color: var(--gold-dim) } is silently dead. Net effect: "Try Franklin" (the primary product CTA) renders gray while "Download Desktop" becomes the only gold, weight-500 item in the nav. Suggested fix: scoped selectors (.site-header .nav-link-desktop, .site-header-paper .nav-link-desktop) with no !important, and decide whether .nav-link-try should get the same treatment so the product CTA isn't outranked.

  2. Nav overflow at 1121–1280px in long locales. The desktop nav doesn't collapse until 1120px, .hdr-inner caps at 1180px, and .nav-link has no white-space: nowrap. The new label is much wider than English in ja (デスクトップ版をダウンロード), ar, ru, ur — links can wrap inside the fixed 72px header. Suggest white-space: nowrap on .nav-link plus verifying ja/ru/ar/ur at 1121–1280px (raising the collapse breakpoint to ~1280px may be needed).

  3. Dark-theme contrast. After visiting /chat in dark mode, data-theme="dark" persists on <html> across client-side navigation; --gold-dim becomes #d8be58 on the near-white header (~1.8:1 contrast), and the !important pins it. Worth verifying whether the dark-theme leak onto marketing pages is in scope.

  4. Pre-existing, surfaced while testing this change: in the 1024–1120px window the hamburger is shown but .mobile-menu never gets display: flex (only @media (max-width: 1023px) sets it), so the menu — including this new link — is unreachable there.

  5. Copy nit: ru "Скачать приложение" drops "Desktop" entirely, which is ambiguous next to the web app the same nav promotes. Also, no accessible indication of the external new-tab jump (matches the existing BlockRun link's gap — fine to fix together or skip).

Notes: all 13 locale dictionaries + types.ts are covered (verified against src/lib/locales.ts), CI is green, rel="noreferrer" is correct. Findings came from a cross-model adversarial review (Claude + Codex); both independently flagged the private-repo 404 as the blocker.

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