Skip to content

Use the deployed BriefLoop mark and match the landing page's type - #607

Merged
Stahl-G merged 1 commit into
mainfrom
codex/brand-logo-live
Sep 10, 2026
Merged

Use the deployed BriefLoop mark and match the landing page's type#607
Stahl-G merged 1 commit into
mainfrom
codex/brand-logo-live

Conversation

@Stahl-G

@Stahl-G Stahl-G commented Sep 10, 2026

Copy link
Copy Markdown
Owner

上一轮我把 /website 的旧检出当成了基准,用错了标志:那是"回环+箭头"的旧图,线上 briefloop.ai 现在用的是 assets/briefloop-mark.svg(文档 + 回环箭头 + 气泡尾,本地检出落后一个提交才没看到)。这次按线上资产重做。

  • 标志:侧栏标记、报告空状态标记、favicon 全部改用线上 briefloop-mark.svg 的几何;favicon 用 briefloop-icon.svg 的纸底圆角版本。
  • 排版:新版落地页其实没有 serif——标题是 system sans、字重 640、字距 -0.02em,等宽只留给数据。上一轮我按旧版网站加的 serif 标题已回退,工作台现在和线上落地页同一套声音。
  • 顺带修一个真 bug:上一轮改 favicon 时替换正则停在 data URI 里的第一个 >,旧值的尾巴留在了 head 里,页面上漏出一个 ">(截图里左上角可见)。现在 head 里只有一条 favicon link,已用无头 Chrome 复验干净。

验证:无头 Chrome 渲染本机服务确认侧栏标志与 "> 已消失;python -m pytest -q 180 passed。

The workbench shipped the older loop-and-arrow glyph; briefloop.ai uses
assets/briefloop-mark.svg (document loop with a bubble tail). Point the sidebar
mark, the empty-state mark and the favicon at that geometry.

The deployed landing page has no serif voice: headings are system sans at
weight 640 with -0.02em tracking, and monospace is kept for data. Drop the serif
headings the previous commit added and use the site's sans scale instead.

Also fix the favicon link the previous change left malformed: the replacement
regex stopped at the first ">" inside the data URI, so the tail of the old
value leaked into the page as a stray `">`.
@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.
To continue using code reviews, add credits to your account and enable them for code reviews in your settings.

@Stahl-G
Stahl-G merged commit 2223353 into main Sep 10, 2026
2 checks passed
@Stahl-G
Stahl-G deleted the codex/brand-logo-live branch September 10, 2026 08:19
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