docs(sponsor): conversion-focused sponsors section in README + full tier pages (en/zh-Hans/zh-Hant) - #217
Merged
Merged
Conversation
…ier pages (en/zh-Hans/zh-Hant) README previously buried a single buy-me-a-coffee line at the very bottom while the GitHub Sponsors tiers (Gold/Silver/Bronze) promised README logo placement that did not exist anywhere. Add a real Sponsors section with open Gold/Silver/Bronze placeholder slots, a 1.6M installs/month pitch, and a Sponsor badge in the header; rewrite the one-line sponsor.md into a full pitch page (tiers, reach stats, invoicing, contact) in all 3 locales. llms.txt / llms-full.txt are prebuild-regenerated; the diff also catches up stale useCookie doc content generated since the last snapshot. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Gold tier promises top-of-README placement; put the section right under the badges (VueUse-style) so the slots sit above the fold. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
… API on sponsor pages) Replace the hardcoded 1.6M+ figure: the README Sponsors section now shows live npm installs/month and GitHub stars via shields.io, and the three sponsor pages fetch api.npmjs.org client-side, falling back to the static figure when unreachable. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
buy me a coffeeline buried at the bottom with a real Sponsors section placed right after Who's Using This — open 🥇/🥈/🥉 placeholder slots ("your logo here") linking to GitHub Sponsors, a pitch line built on the real number (1.6M+ npm installs/month), Sponsor + Buy-me-a-coffee buttons, and a ❤ Sponsor badge in the header badge row. The old bottom section becomes a short Support ReactUse note for individuals.Why
GitHub Sponsors is already set up with tiers that promise "logo on README", but the README had no sponsors section at all and no visible entry point — the promise looked unbacked and there was nothing to convert an interested company. Goal: maximize sponsor conversion using only real, verifiable claims (no fake sponsors).
Test plan
pnpm lintcleanpnpm --filter website-astro build— 483 pages built;/sponsor/,/zh-hans/sponsor/,/zh-hant/sponsor/all render with correct titles and 5 sponsor links each🤖 Generated with Claude Code