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

blog: Thank you to sponsors, fixes #318 #335

Open
wants to merge 12 commits into
base: main
Choose a base branch
from

Conversation

rfay
Copy link
Member

@rfay rfay commented Feb 28, 2025

The Issue

We've been wanting to do a sponsor appreciation blog post.

Review rendered at https://20250226-thanks-to-sponsors.ddev-com-front-end.pages.dev/blog/sponsor-thanks

@rfay rfay force-pushed the 20250226_thanks_to_sponsors branch from 9c508ec to b73df43 Compare March 4, 2025 16:30
Copy link

cloudflare-workers-and-pages bot commented Mar 4, 2025

Deploying ddev-com-front-end with  Cloudflare Pages  Cloudflare Pages

Latest commit: 657b5a0
Status: ✅  Deploy successful!
Preview URL: https://80a155c8.ddev-com-front-end.pages.dev
Branch Preview URL: https://20250226-thanks-to-sponsors.ddev-com-front-end.pages.dev

View logs

@rfay rfay force-pushed the 20250226_thanks_to_sponsors branch from b73df43 to 91016c7 Compare March 4, 2025 16:46
@rfay rfay changed the title [wip] blog: Thank you to sponsors, fixes #318 - not ready for review blog: Thank you to sponsors, fixes #318 Mar 7, 2025
@rfay rfay force-pushed the 20250226_thanks_to_sponsors branch from 83454d2 to 1166f85 Compare March 10, 2025 23:17
@rfay rfay marked this pull request as ready for review March 10, 2025 23:17
Copy link
Member

@stasadev stasadev left a comment

Choose a reason for hiding this comment

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

Looks good to me!

@rfay rfay requested a review from rpkoller March 13, 2025 16:17
Copy link

@rpkoller rpkoller left a comment

Choose a reason for hiding this comment

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

looks good overall, left only a brief comment about the second section heading.

- [Mobilistics](https://mobilistics.de/) and [i-gelb](https://i-gelb.net) both sponsor at the $500/month level.
- All these lovely organizations sponsor at the $100/month (or a bit higher) level: [Lullabot](https://lullabot.com), [Affinity Bridge](https://affinitybridge.com/), [Webikon](https://github.com/claudiu-cristea), [FameHelsinki](https://fame.fi/), [OPTASY](https://www.optasy.com/), [Gizra](https://gizra.com), [Healthcare without Harm](https://noharm.org/), [Cambrico](https://cambrico.net/), [Agaric](https://agaric.coop), [Centarro](https://centarro.io), [Craft CMS](https://craftcms.com/), [Redfin Solutions](https://redfinsolutions.com/), [b13](https://b13.com). And brand new this week (welcome!) [Full Fat Things](https://www.fullfatthings.com/).

## So many more wonderful sponsors!

Choose a reason for hiding this comment

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

the first and the third section heading labels and categorizes the type of sponsorship, while the second is more like an "unspecific" colloquial statement. i wonder if it would be clearer to use something like "Individual sponsors" for labeling the second section? First you have the major sponsor then the individual and then the in-kind?

Copy link
Member Author

Choose a reason for hiding this comment

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

Not sure what to do about this, or whether anybody's still reading unless they're waiting for their name to be dropped :)

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.

4 participants