pauliescanlon

Vercel have controlled the narrative that, managing your own infrastructure is too difficult or, it takes too much time away from shipping products. They want you to put your trust in them, but you’ll have to pay for it. This would be ok if you could trust them.

Many stories are emerging where it’s clear that trusting Vercel is a risky strategy.

Yeah lovely stuff. I'm working on a similar "thing" using Octokit. I like experimenting with things that aren't supposed to be used as CMS's as CMS's

Lovely stuff. Thanks!

A fair point. Also true for any front end that relies on an API to populate its data. Hacker News for instance will use a similar approach. If they concern is that sometimes API's may go down and data won't be displayed you can of course chose not to use API's in your front end. If you're not that bothered like me, that this is just. "one" way you "could" use Twitter as a CMS for you blog.

Hey, and yes that would also work, as you say, for profile information that doesn't change that often it would perhaps be the better option. However, since this is a tutorial blog post it's aim was to inform readers of "one" way you can use Twitter as a CMS. There are of course many other ways to achieve this.

In this post I'm going to explain how you can use Netlify Functions to access your Twitter profile data using the Twitter v2 API and display it on your Gatsby blog.