Skip to content

feat(web): add sponsors to landing page - #209

Merged
maxktz merged 3 commits into
mainfrom
feat/sponsors
Sep 17, 2026
Merged

maxktz merged 3 commits into
mainfrom
feat/sponsors

Conversation

@maxktz

@maxktz maxktz commented Sep 17, 2026

Copy link
Copy Markdown
Contributor

Summary

  • add a responsive sponsor section to the landing page with hardcoded company and individual sponsor data
  • add Vercel and Efferd branding and sponsor-specific hover/avatar interactions
  • remove the standalone sponsor page, route aliases, and header navigation item
  • add a green development favicon while preserving the production favicon

Validation

  • pnpm --filter web format
  • pnpm --filter web typecheck
  • pnpm --filter web lint
  • git diff --check

Summary by cubic

Adds a responsive sponsors section to the landing page with hardcoded company and individual sponsor data. Replaces the standalone sponsor page with the #sponsors section and serves a green favicon in development while keeping the production favicon unchanged.

  • Removes the /sponsor page, header nav link, and /sponsors redirect; /donate now redirects to /#sponsors.
  • Adds Vercel and Efferd logo assets, hover/focus interactions, and section id support for deep linking.

Written for commit e2e7432. Summary will update on new commits.

Review in cubic

Summary by CodeRabbit

  • New Features

    • Added a Sponsors section to the marketing homepage, displaying company and individual sponsors with links and sponsorship amounts.
    • Added support for linking directly to page sections.
  • Updates

    • The standalone Sponsors page is no longer available, and its navigation links were removed.
    • Donation links now direct visitors to the Sponsors section on the homepage.
    • Updated favicon routing and metadata, including separate development and production icons.

@vercel

vercel Bot commented Sep 17, 2026

Copy link
Copy Markdown
Contributor

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

Project Deployment Actions Updated
paykit Ready Ready Preview Sep 17, 2026 4:27pm UTC

@coderabbitai

coderabbitai Bot commented Sep 17, 2026

Copy link
Copy Markdown

Review Change StackReview Change Stack

Warning

Review limit reached

Next included review available in 19 minutes.

Check out review usage here.

View limit details

Limit details: You’ve used all 4 included reviews currently available.

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

Learn how review limits work.

Review configuration:

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Advanced

Run ID: 25d5df1f-1e16-4cba-b567-222c3501384b

📥 Commits

Reviewing files that changed from the base of the PR and between f658809 and e2e7432.

📒 Files selected for processing (2)
  • apps/web/src/components/sections/sponsors-content.ts
  • apps/web/src/components/sections/sponsors-section.tsx

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Advanced

Run ID: 5d2e96fc-4d30-48ce-9e84-843f2070f539

📥 Commits

Reviewing files that changed from the base of the PR and between be76c96 and f658809.

⛔ Files ignored due to path filters (5)
  • apps/web/public/companies/efferd.svg is excluded by !**/*.svg
  • apps/web/public/companies/vercel-mark.svg is excluded by !**/*.svg
  • apps/web/public/favicon/development.svg is excluded by !**/*.svg
  • apps/web/public/favicon/favicon.svg is excluded by !**/*.svg
  • apps/web/public/favicon/production.svg is excluded by !**/*.svg
📒 Files selected for processing (8)
  • apps/web/next.config.js
  • apps/web/src/app/(marketing)/page.tsx
  • apps/web/src/app/(marketing)/sponsor/page.tsx
  • apps/web/src/app/layout.tsx
  • apps/web/src/components/layout/navigation-bar.tsx
  • apps/web/src/components/layout/section.tsx
  • apps/web/src/components/sections/sponsors-content.ts
  • apps/web/src/components/sections/sponsors-section.tsx
💤 Files with no reviewable changes (2)
  • apps/web/src/components/layout/navigation-bar.tsx
  • apps/web/src/app/(marketing)/sponsor/page.tsx

Included review availability: Your plan provides up to 4 included reviews per hour; 0 remain after this review.


📝 Walkthrough

Walkthrough

The marketing page now includes company and individual sponsors. Sponsor navigation and redirects now target the landing-page section. Favicon metadata and rewrites now use environment-specific root paths.

Changes

Sponsors landing section

Layer / File(s) Summary
Sponsor data and rendering
apps/web/src/components/sections/sponsors-content.ts, apps/web/src/components/sections/sponsors-section.tsx
Adds typed sponsor data and responsive company and individual sponsor layouts.
Sponsor anchor and route integration
apps/web/src/components/layout/section.tsx, apps/web/src/app/(marketing)/page.tsx, apps/web/src/app/(marketing)/sponsor/page.tsx, apps/web/src/components/layout/navigation-bar.tsx, apps/web/next.config.js
Adds section ids, renders SponsorsSection on the landing page, removes the placeholder sponsor page and navigation entry, and redirects /donate to /#sponsors.

Environment-specific favicon routing

Layer / File(s) Summary
Favicon metadata and rewrites
apps/web/next.config.js, apps/web/src/app/layout.tsx
Uses /favicon.svg?v=5 in metadata and rewrites favicon requests to development or production assets based on NODE_ENV.

Priority: ⬇️ Low

Estimated code review effort: 3 (Moderate) | ~25 minutes

Change: Feature

Sequence Diagram(s)

sequenceDiagram
  participant MarketingPage
  participant SponsorsSection
  participant sponsorsData
  participant Section
  MarketingPage->>SponsorsSection: render sponsors section
  SponsorsSection->>sponsorsData: read sponsor entries
  SponsorsSection->>Section: render grouped sponsor content
Loading

Merge Risk: ⚪ Minimal · up to f6588

The sponsor redirect reaches the intended landing-page section. No merge-blocking issue was identified.

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name Status Explanation Resolution
Docstring Coverage ⚠️ Warning Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%. Docstring coverage is scoped to functions touched by this diff. Analyzed 7 functions across 6 files. Write docstrings for the functions missing them to satisfy the coverage threshold.
✅ Passed checks (4 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title clearly and concisely describes the main change: adding sponsors to the web landing page.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
✨ Finishing Touches 💡 1
📝 Generate docstrings 💡
  • Commit to this branch
  • Create a new PR
🧪 Generate unit tests (beta)
  • Commit to this branch
  • Create a new PR

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

A rabbit hops where sponsor cards now gleam
Company stars and donors join the stream
The landing page gathers each name
Tiny favicon paths play the same game
The carrot-shaped anchor points the way

Comment @coderabbitai help to get the list of available commands.

@cubic-dev-ai cubic-dev-ai 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.

All reported issues were addressed across 13 files

Reply with feedback, questions, or to request a fix.

Re-trigger cubic

Comment thread apps/web/src/components/sections/sponsors-section.tsx Outdated
Comment thread apps/web/src/components/sections/sponsors-content.ts Outdated
Comment thread apps/web/src/components/sections/sponsors-section.tsx
@maxktz
maxktz merged commit cdbd24a into main Sep 17, 2026
11 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