Project relationship with Sponsors may require its own lexicon. It may not be enough with a generic flat collection type. There are sponsor types, tiers, resources for each sponsor, logo to use, preferences (visible/hidden), stakeholders for contact (and how to contact them), sponsorship durations, requirements/description of the relationship.
We already had maintainers telling us that they would love to be able to see their sponsors in the npmx package page. Projects are adding sponsors widgets to their readme to do that. A lot of the time, these are not accessible, a image with the logos for example (if we detect a sponsor section in the readme, we could hide it so it isn't duplicated in npmx). We can do this generally, have proper a11y, interactive widgets with hover cards about each sponsor. I would be interesting to do admins, too. To have a way to sync from GitHub Sponsors, Open Collective, Patron, etc.
From the other side, we could work on the future to surface Sponsor CTAs in context for Users and Projects. This should later be its own issue.
Project relationship with Sponsors may require its own lexicon. It may not be enough with a generic flat collection type. There are sponsor types, tiers, resources for each sponsor, logo to use, preferences (visible/hidden), stakeholders for contact (and how to contact them), sponsorship durations, requirements/description of the relationship.
We already had maintainers telling us that they would love to be able to see their sponsors in the npmx package page. Projects are adding sponsors widgets to their readme to do that. A lot of the time, these are not accessible, a image with the logos for example (if we detect a sponsor section in the readme, we could hide it so it isn't duplicated in npmx). We can do this generally, have proper a11y, interactive widgets with hover cards about each sponsor. I would be interesting to do admins, too. To have a way to sync from GitHub Sponsors, Open Collective, Patron, etc.
From the other side, we could work on the future to surface Sponsor CTAs in context for Users and Projects. This should later be its own issue.