Repository navigation
feat: ask for sponsorship, in the two places people read - #19
Merged
Merged
Conversation
The .github default FUNDING.yml already puts a Sponsor button on this repo, but the button lives in the sidebar where nobody looks. The README section sits next to the licence, where someone who has just found this useful is already reading; the site footer reaches the visitors who never open GitHub. Wording is identical across every repo on purpose: one place to change if the ask changes, and no per-repo pleading. The footer link is styled by gloam's gl-sponsor class, which arrived with the last asset sync.
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.
The `richardwooding/.github` default `FUNDING.yml` already gives this repo a Sponsor button, so this is emphasis rather than mechanism — the button sits in the sidebar, while the README is what someone reads in the minute after the project turned out to be useful, and the site footer reaches visitors who never open GitHub.
Wording is byte-identical across the sweep so there is one place to edit if the ask changes. Deliberately no badge: about thirty repos have no badge block at all, and forcing one in for this would read worse than the section does.
The footer link uses gloam's
.gl-sponsorclass, which landed in the lastchore(site): sync gloam design assets. gloam ships the style; the anchor is the site's own, so an asset sync can never change what a page asks for.Swept with
scripts/sponsor-sweep.shin richardwooding/.github.