New sponsorship site - #606
Draft
dbernheisel wants to merge 1 commit into
Draft
Conversation
dbernheisel
force-pushed
the
new-sponsorship-site
branch
from
August 6, 2026 19:50
bc2b30d to
73cedbd
Compare
dbernheisel
force-pushed
the
new-sponsorship-site
branch
from
August 6, 2026 19:52
73cedbd to
2c3c81a
Compare
maennchen
reviewed
Aug 6, 2026
maennchen
reviewed
Aug 6, 2026
dbernheisel
commented
Aug 6, 2026
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
2 participants
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.
DO NOT MERGE -- awaiting https://sponsor.erlef.org to be complete and serving its json endpoint.
This removes the database-backed sponsors schema, database table, admin interface, and rendering helpers in favor of consuming from a static site at https://sponsor.erlef.org. It's currently set to cache in
:persistent_termand refetch daily so it's not always hitting the microsite; this doesn't change often, so I'm open to extending the refresh interval.before footer
after footer