Repository navigation
Make sponsorship easy to find on the support page - #151
Merged
Merged
Conversation
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 Support Fullbleed page led with playground and example links, leaving sponsorship below unrelated actions. It now opens with direct monthly and one-time GitHub Sponsors buttons, explains who receives contributions and what they fund, and keeps nonfinancial contributions in a secondary section. The navigation label is now Support Fullbleed.
Validation: strict MkDocs build and diff checks passed. Desktop (1440 px) and mobile (390 px) browser checks confirm both buttons are visible without scrolling, with no horizontal overflow. Each button was followed to GitHub and the corresponding sponsorship frequency and custom-amount option verified. Screenshots were reviewed; no payment was submitted.