Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Improve sponsor promotion #46

Closed
mattstein opened this issue Apr 22, 2023 · 3 comments
Closed

Improve sponsor promotion #46

mattstein opened this issue Apr 22, 2023 · 3 comments

Comments

@mattstein
Copy link
Sponsor Collaborator

#44 implied that we could be doing a better job of promoting project sponsors and acknowledging various levels of commitment.

I propose we do the following:

  • Create/generate a .svg image to embed in the ddev/ddev readme, so we can consistently use high-quality logos from the same source and fix abhorrent spacing issues that aren’t kind to any of them.
  • Visually emphasize top-level sponsors on the ddev.com homepage, and possibly do the same thing with the readme.
  • Again promote top-level sponsors globally in ddev.com’s footer, which has a lot of room for it.
  • Identify any other opportunities within repositories, ddev.com, the docs, etc. that might tastefully promote sponsors without getting in the way of whatever the user/reader is doing.

Whatever “top-level” means, we should also update the GitHub sponsors page to reflect a clear policy for this so it’s fair and always apparent where sponsor logos need to go.

@rfay
Copy link
Member

rfay commented Apr 22, 2023

Sounds great to me!

@rfay
Copy link
Member

rfay commented Aug 15, 2023

I think this one is all sorted out. There's probably more we can do, can follow up in

@rfay rfay closed this as completed Aug 15, 2023
@rfay
Copy link
Member

rfay commented Aug 15, 2023

Thanks for the amazing work on this @mattstein !

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

No branches or pull requests

2 participants