Skip to content

feat(branding): sim wordmark favicon/OG, docs footer parity, footer peel#5587

Merged
waleedlatif1 merged 6 commits into
stagingfrom
feat/sim-favicon-and-docs-logo
Jul 11, 2026
Merged

feat(branding): sim wordmark favicon/OG, docs footer parity, footer peel#5587
waleedlatif1 merged 6 commits into
stagingfrom
feat/sim-favicon-and-docs-logo

Conversation

@waleedlatif1

Copy link
Copy Markdown
Collaborator

Summary

  • Replace the apps/sim favicon and default OG image with the sim wordmark logo (same asset used for the docs favicon); OG image canvas widened, logo kept at native size
  • Swap the docs navbar logo to the icon-only mark (no wordmark text)
  • Add a scroll "peel" reveal effect to the landing footer — a sticky-positioned illustration revealed after the footer's own content scrolls past, pure CSS (no scroll listeners, no animation library)
  • Port the same footer (full link directory + peel effect) to the docs app so both apps are visually consistent; added Academy to the Resources column
  • Rebuilt the docs OG image template to match the site's existing blog/library cover style (wordmark top-left, arrow top-right, title bottom-left) — this also uncovered and worked around a real Satori (next/og) text-measurement bug that doubled the gap after certain word pairs when wrapping long titles

Type of Change

  • New feature
  • Bug fix (Satori text-wrap rendering bug)

Testing

Tested manually — ran both apps' dev servers and verified via raw HTML/SSR output and rendered OG image fetches:

  • Sim app favicon/icon.svg and OG image serve the new wordmark asset at the correct dimensions
  • Docs navbar and DocsLayout title slot both render the icon-only mark
  • Footer peel effect renders identically (byte-for-byte matching classes) on both apps' footers, all footer links resolve (200s)
  • Docs OG route tested against short/long/default titles, confirmed the word-wrap fix holds and matches the reference template

Checklist

  • Code follows project style guidelines
  • Self-reviewed my changes
  • Tests added/updated and passing
  • No new warnings introduced
  • I confirm that I have read and agree to the terms outlined in the Contributor License Agreement (CLA)

- replace apps/sim favicon and default OG image with the sim wordmark
  logo (OG image widened, logo kept at native size)
- swap the docs navbar logo to the icon-only mark (no wordmark text)
- add a scroll "peel" reveal effect to the landing footer using a
  sticky-positioned illustration, pure CSS, no scroll listeners
- port the same footer (link directory + peel effect) to the docs app
  so both apps are visually consistent; add Academy to Resources
- rebuild the docs OG image template to match the site's existing
  blog/library cover style (wordmark top-left, arrow top-right, title
  bottom-left), working around a Satori text-measurement bug that
  doubled the gap after certain words
@vercel

vercel Bot commented Jul 11, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
docs Ready Ready Preview, Comment Jul 11, 2026 3:48am

Request Review

@cursor

cursor Bot commented Jul 11, 2026

Copy link
Copy Markdown

PR Summary

Low Risk
Presentation-layer changes (OG route, footer, logos, CSS) with no auth or data-path impact; main operational risk is OG generation if the static Season font asset is missing on deploy.

Overview
Aligns docs branding and layout with the marketing site: nav/sidebar logos switch from the full icon+text mark to the sim wordmark, with new SimWordmark / SimLogoIcon components and unique SVG gradient IDs on the legacy full logo.

Docs OG images are rebuilt to match blog/library covers (light gray canvas, wordmark + corner arrow, large Season title at 1200×675). Metadata OG heights are updated accordingly. The route loads a static Season TTF from /static/fonts/, pre-wraps titles with a Satori space-width workaround, and drops Geist/Google font loading.

Footer parity: the landing footer’s full link directory and CSS-only scroll peel are ported to docs (Footer, FooterPeel, SIM_SITE_URL for sim.ai links); the same peel wrapper lands on the sim landing footer. The docs sidebar divider is sticky within the layout grid so it no longer runs into the new footer.

Reviewed by Cursor Bugbot for commit 890d1b3. Configure here.

Comment thread apps/docs/components/footer/footer.tsx
@greptile-apps

greptile-apps Bot commented Jul 11, 2026

Copy link
Copy Markdown
Contributor

Greptile Summary

This PR updates branding assets and brings the landing and docs footer experiences closer together. The main changes are:

  • New Sim wordmark favicon and OG image assets.
  • Updated docs navbar and layout branding.
  • New footer peel illustration effect for the landing and docs footers.
  • A docs footer with matching link columns.
  • A rebuilt docs OG image route using the Season Sans font.

Confidence Score: 5/5

This looks safe to merge.

  • No blocking issues found in the changed code.

Important Files Changed

Filename Overview
apps/docs/app/api/og/route.tsx Rebuilds the docs OG image route around a static Season Sans font and pre-split title lines.
apps/docs/lib/urls.ts Adds a fixed marketing-site origin for docs footer links.
apps/docs/components/footer/footer.tsx Adds the docs footer with marketing links, docs links, and the peel reveal wrapper.
apps/docs/components/ui/sim-logo.tsx Adds the wordmark and gives gradient-based logo components instance-specific IDs.

Reviews (4): Last reviewed commit: "fix(docs): fix sidebar-divider grid regr..." | Re-trigger Greptile

Comment thread apps/docs/app/api/og/route.tsx
Comment thread apps/docs/lib/urls.ts Outdated
Comment thread apps/docs/components/ui/sim-logo.tsx
- switch the docs OG image title font from Geist to the site's real
  brand font (Season Sans), instantiated as a static TTF weight since
  Satori can't parse WOFF2 or variable fonts; served from /static/
  so the i18n proxy's matcher (which excludes static but not fonts)
  doesn't intercept it
- fix DocsLayout's nav.title (fumadocs' own mobile menu slot) to show
  the wordmark instead of the icon mark
- add an isolated stacking context + higher z-index to both the docs
  and sim app footers so fumadocs' sticky z-20 sidebar can't paint
  over the footer content or the peel reveal
- recalibrate the OG image to the reference cover template's actual
  measured values: 1200x675 canvas (was 630), ~26px margins (was
  56-64px), ink #525252 (was #3f3f3f), larger wordmark/arrow/title
  sizing — confirmed by direct pixel measurement of the reference
  cover.jpg, not estimation
- fix SimLogoIcon/SimLogoFull's SVG gradient ids to be unique via
  useId() instead of a fixed string, so multiple instances on one
  page don't collide (Greptile P2)
- fix SIM_SITE_URL to be a hardcoded sim.ai constant instead of
  deriving from NEXT_PUBLIC_APP_URL, which reflects wherever this
  deployment runs, not the fixed public marketing site (Greptile P1)
@waleedlatif1

Copy link
Copy Markdown
Collaborator Author

@greptile

@waleedlatif1

Copy link
Copy Markdown
Collaborator Author

@cursor review

Comment thread apps/docs/components/footer/footer.tsx Outdated
Every other integration in the footer's Integrations column links to
its own docs.sim.ai guide; Jira was the only one pointing at the
marketing site's landing page instead, despite docs having its own
/integrations/jira guide. Matches the established pattern.
@waleedlatif1

Copy link
Copy Markdown
Collaborator Author

@greptile

@waleedlatif1

Copy link
Copy Markdown
Collaborator Author

@cursor review

@cursor cursor Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

✅ Bugbot reviewed your changes and found no new issues!

Comment @cursor review or bugbot run to trigger another review on this PR

Reviewed by Cursor Bugbot for commit 41f474c. Configure here.

…tioning, OG sizing, and prune stray comments

- #nd-docs-layout::before divider now spans the full grid explicitly
  (grid-row/grid-column: 1 / -1) instead of being auto-placed into a
  real content cell, which was pushing page content down
- footer-peel.jpg moved under /static/landing/ (was 404ing behind the
  i18n proxy's non-static path matcher) and wrapped in a relative div
  so next/image's fill positioning is valid under the sticky container
- OG route: corrected title font sizes and char-width ratio so long
  titles wrap to 2 lines instead of 3, and resized the corner arrow to
  match the reference cover template's proportions
- swapped the icon-only desktop navbar logo back to the wordmark
- removed stray non-TSDoc comments, folded into TSDoc where the
  explanation was worth keeping
@waleedlatif1

Copy link
Copy Markdown
Collaborator Author

@greptile

@waleedlatif1

Copy link
Copy Markdown
Collaborator Author

@cursor review

@cursor cursor Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

✅ Bugbot reviewed your changes and found no new issues!

Comment @cursor review or bugbot run to trigger another review on this PR

Reviewed by Cursor Bugbot for commit 890d1b3. Configure here.

The peel's "reveal window" relied on position: sticky bottom-detaching
into a containing block whose extra height came from padding-bottom —
that combination doesn't reliably work in WebKit/Safari (sticky never
gets room to engage when the surplus height is padding rather than an
explicit height or content), so the peel stayed permanently covered by
the footer regardless of viewport size. Rather than carry that
unreliable technique further, removing it entirely from both apps and
reverting to the plain footer link directory.
@waleedlatif1 waleedlatif1 merged commit f3582ed into staging Jul 11, 2026
10 of 11 checks passed
@waleedlatif1 waleedlatif1 deleted the feat/sim-favicon-and-docs-logo branch July 11, 2026 03:44
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