💡 GitHub Sponsors and dev.to posts

Yesterday, I read a blog post by Caleb Porzio about making money from Open Source projects, in particular by leveraging the GitHub sponsors program.

His conclusion is that the best way to use GitHub Sponsors is to make both free and paid educational content, such that free content attracts an audience, and then they want to support you to access the advanced, paid, content.

It seems to me that the DEV community, being already connected to GitHub, would be a perfect place to implement this idea.

There could be a tag in the meta parameters of a post, which would restrict its access (fully or partly, e.g. by hiding the end of the article like lots of newspapers do) to the author's GitHub sponsors:

# Restrict to sponsors of the raphink GitHub account
restrict_sponsors: raphink
# Restrict to sponsors of tier $10 or above
restrict_sponsors: raphink/10

What do you think? Is that a feature that would be interesting for the DEV community?

Comments

[Waylon Walker]

It could be cool to see something like early access and exclusive for paid subscribers, but for the most part I would not want to have to pay everyone to see their content on DEV.

[Habdul Hazeez]

Is that a feature that would be interesting for the DEV community?

In my opinion. YES.

[Ben Sinclair]

I think the existing monetisation system is a better idea. Mostly because it's more open, whereas this is restricting people to GitHub, and not everyone wants to use GitHub.