Skip to content

docs(website): Add sponsor CTA to website sponsors section#1141

Merged
yamadashy merged 1 commit intomainfrom
docs/add-sponsor-cta-to-website
Feb 7, 2026
Merged

docs(website): Add sponsor CTA to website sponsors section#1141
yamadashy merged 1 commit intomainfrom
docs/add-sponsor-cta-to-website

Conversation

@yamadashy
Copy link
Copy Markdown
Owner

@yamadashy yamadashy commented Feb 7, 2026

Add "Please consider sponsoring me" message with GitHub Sponsor button to the website sponsors section, matching the README layout.

  • Copy sponsor button SVG to website public images
  • Add CTA text and button below the individual sponsors list in sponsors-section.md

Checklist

  • Run npm run test
  • Run npm run lint

Open with Devin

Add "Please consider sponsoring me" message with GitHub Sponsor button
below the individual sponsors list on the website, matching the README layout.
@gemini-code-assist
Copy link
Copy Markdown
Contributor

Summary of Changes

Hello @yamadashy, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request enhances the website's sponsorship section by introducing a prominent call-to-action for potential sponsors. It integrates a clear message and a visually distinct GitHub Sponsor button, aiming to increase visibility and accessibility for sponsorship opportunities directly on the website, aligning with the project's README layout.

Highlights

  • Sponsor Call-to-Action Added: A new 'Please consider sponsoring me' message has been added to the website's sponsors section.
  • GitHub Sponsor Button Integration: A GitHub-style sponsor button has been incorporated, linking directly to the author's GitHub Sponsors page.
  • SVG Asset Inclusion: A new SVG file for the sponsor button has been added to the public images directory of the website.
  • Sponsors Section Update: The sponsors-section.md file was modified to display the new CTA text and sponsor button below the existing list of individual sponsors.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Changelog
  • website/client/src/public/images/github-like-sponsor-button.svg
    • Added a new SVG file containing the visual assets for a GitHub-style sponsor button.
  • website/client/src/shared/sponsors-section.md
    • Modified to include a new HTML div element containing a 'Please consider sponsoring me.' paragraph and an anchor tag wrapping an image, which displays the newly added github-like-sponsor-button.svg and links to the GitHub Sponsors page.
Activity
  • No human activity (comments, reviews, or progress updates) has been recorded on this pull request yet.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai bot commented Feb 7, 2026

📝 Walkthrough

Walkthrough

A centered sponsorship promotion block is added to the sponsors section markdown file. The addition includes a paragraph requesting sponsorship, a sponsor button link, and an associated image, appended after existing content.

Changes

Cohort / File(s) Summary
Sponsorship Promo
website/client/src/shared/sponsors-section.md
Appends 7 lines containing a centered HTML block with sponsorship call-to-action paragraph, button link, and image.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

🚥 Pre-merge checks | ✅ 3
✅ Passed checks (3 passed)
Check name Status Explanation
Title check ✅ Passed The title clearly and concisely describes the main change: adding a sponsor call-to-action to the website sponsors section.
Description check ✅ Passed The description covers the main objectives, lists specific changes (sponsor SVG copy and CTA addition), and includes the required checklist from the template.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch docs/add-sponsor-cta-to-website

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

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

Copy link
Copy Markdown
Contributor

@devin-ai-integration devin-ai-integration bot left a comment

Choose a reason for hiding this comment

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

✅ Devin Review: No Issues Found

Devin Review analyzed this PR and found no potential bugs to report.

View in Devin Review to see 1 additional finding.

Open in Devin Review

@codecov
Copy link
Copy Markdown

codecov bot commented Feb 7, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 87.17%. Comparing base (56d3dcf) to head (8149d4f).
⚠️ Report is 2 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #1141   +/-   ##
=======================================
  Coverage   87.17%   87.17%           
=======================================
  Files         116      116           
  Lines        4382     4382           
  Branches     1019     1019           
=======================================
  Hits         3820     3820           
  Misses        562      562           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@cloudflare-workers-and-pages
Copy link
Copy Markdown

Deploying repomix with  Cloudflare Pages  Cloudflare Pages

Latest commit: 8149d4f
Status: ✅  Deploy successful!
Preview URL: https://c9f402e7.repomix.pages.dev
Branch Preview URL: https://docs-add-sponsor-cta-to-webs.repomix.pages.dev

View logs

Copy link
Copy Markdown
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

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

Code Review

This pull request adds a sponsorship call-to-action to the sponsors section of the website. The changes include adding an SVG for the sponsor button and updating the markdown file for the sponsors section.

My review has identified a few areas for improvement:

  • The new SVG button for sponsoring does not support dark mode. I've suggested a change to make it theme-aware using CSS media queries within the SVG.
  • The new link that opens in a new tab is missing the rel="noopener noreferrer" attribute, which is a security risk.
  • The use of the obsolete align attribute in the new HTML code. I've suggested using modern CSS for alignment instead.

These changes will improve UI consistency and security.

Copy link
Copy Markdown
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 1

🤖 Fix all issues with AI agents
In `@website/client/src/shared/sponsors-section.md`:
- Around line 32-36: The anchor element that opens an external link in a new tab
(the <a href="https://github.com/sponsors/yamadashy" target="_blank"> element)
is missing rel="noopener noreferrer"; update that anchor to include
rel="noopener noreferrer" to prevent tabnabbing and follow security best
practices when using target="_blank".

@claude
Copy link
Copy Markdown
Contributor

claude bot commented Feb 7, 2026

Claude Code Review

Summary

This PR adds a sponsor call-to-action (CTA) to the website sponsors section, mirroring the layout already present in the README. The changes are minimal and well-focused:

  • New file: website/client/src/public/images/github-like-sponsor-button.svg (copied from .github/assets/)
  • Modified file: website/client/src/shared/sponsors-section.md (added CTA div with message and sponsor button)

✅ What Looks Good

  1. Consistency with README: The sponsor CTA pattern matches the existing README layout
  2. SVG is identical: The new SVG file is exactly the same as .github/assets/github-like-sponsor-button.svg - maintaining visual consistency
  3. Minimal changes: The PR is focused and doesn't introduce unnecessary complexity
  4. CI Status: All linting checks pass; tests are running successfully

AI Bot Comment Evaluation

Gemini Code Assist - 3 suggestions

1. Dark mode support for SVG
Priority: Not needed
The existing SVG in .github/assets/github-like-sponsor-button.svg (used in README) doesn't have dark mode support either. This is a pre-existing design choice and should be addressed in a separate PR if desired, not as part of this documentation update.

2. Missing rel="noopener noreferrer" on target="_blank" link
Priority: Not needed
While this is generally a good security practice, the existing code in the same file (sponsors-section.md) has 3 other target="_blank" links (lines 6, 15, 23) that also don't have this attribute. Adding it only to the new link would create inconsistency. If this should be addressed, it should be done for all links in a separate PR.

3. Obsolete align attribute
Priority: Not needed
The existing code at the top of the file already uses <div align="center"> (line 1). This PR follows the established pattern. Changing it would be inconsistent with the rest of the file.

CodeRabbit - 1 suggestion

Missing rel="noopener noreferrer"
Priority: Not needed
Same reasoning as above - the existing links in the file don't have this attribute. Consistency with the current file pattern takes precedence. This could be a separate improvement PR that addresses all links at once.

Devin Review

No issues found - ✅ Agreed

📋 Recommendations

  1. Consider adding consistency in a follow-up PR: If the maintainer wants to add rel="noopener noreferrer" to all target="_blank" links in the sponsors section, that would be a good separate PR

  2. SVG duplication: The SVG file already exists at .github/assets/github-like-sponsor-button.svg. Consider referencing the existing file or documenting why a copy is needed in the public images folder (likely for website build accessibility)

🔍 Premortem Analysis

Risk Likelihood Impact Mitigation
SVG display issues on certain browsers Low Low SVG uses standard elements and widely supported font stacks
Style conflicts in VitePress Low Low The inline styles are self-contained
Broken image path Low Medium Path /images/github-like-sponsor-button.svg follows existing pattern (e.g., line 16 uses /images/sponsors/tuple/...)

✅ Verdict

LGTM - This PR is ready to merge. The changes are minimal, consistent with existing patterns, and the bot suggestions, while generally valid best practices, would break consistency with the existing codebase and are better addressed in separate PRs.


🤖 Review by Claude (claude-opus-4-5-20251101)

@yamadashy yamadashy merged commit 1f0a69d into main Feb 7, 2026
63 checks passed
@yamadashy yamadashy deleted the docs/add-sponsor-cta-to-website branch February 7, 2026 15:54
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