Skip to content

Conversation

@davidfischer
Copy link
Member

  • Currently sponsor images are stored in git with links and descriptions hardcoded. This change makes them DB driven instead.
  • Sponsors can be easily added, re-ordered, or made inactive (without deleting)
  • A max of 3 sponsors are displayed on the homepage by default

IMPORTANT: When this change is deployed, there will be a migration to run and sponsors to add to the DB.

- Currently sponsor images are stored in git with links and descriptions
  hardcoded. This change makes them DB driven instead.
- Sponsors can be easily added, re-ordered, or made inactive (without
  deleting)
- A max of 3 sponsors are displayed on the homepage by default

When this is deployed, there will be a migration to run and sponsors to
add to the DB.
@davidfischer davidfischer requested a review from a team November 23, 2025 17:41
Copy link
Member

@willingc willingc left a comment

Choose a reason for hiding this comment

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

Nice change! Thanks @davidfischer

@davidfischer
Copy link
Member Author

Thanks @willingc.

The migration has been run in production and the sponsors setup in the DB. This is ready to deploy. I'm going to hold off for a day or two due to the test I'm running in #196 to see if it solves the production crashes I'm seeing.

@davidfischer davidfischer merged commit aea0809 into main Nov 26, 2025
1 check passed
@davidfischer davidfischer deleted the davidfischer/sponsors-db-driven branch November 26, 2025 23:30
@davidfischer davidfischer mentioned this pull request Nov 26, 2025
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.

3 participants