Use Netlify Functions and the Twitter API v2 as a CMS for Your Gatsby Blog
1–10 of 22 posts
Re: Use Netlify Functions and the Twitter API v2 as a CMS for Your Gatsby Blog
#2Re: Use Netlify Functions and the Twitter API v2 as a CMS for Your Gatsby Blog
#3Doesn't seem reliable.
Re: Use Netlify Functions and the Twitter API v2 as a CMS for Your Gatsby Blog
#4Not sure if using 3rd party services for a CMS is a good idea. What happens if this API or Netlify goes down? Doesn't seem reliable.
Re: Use Netlify Functions and the Twitter API v2 as a CMS for Your Gatsby Blog
#5Re: Use Netlify Functions and the Twitter API v2 as a CMS for Your Gatsby Blog
#6How about “no”.
Re: Use Netlify Functions and the Twitter API v2 as a CMS for Your Gatsby Blog
#7Not sure if using 3rd party services for a CMS is a good idea. What happens if this API or Netlify goes down? Doesn't seem reliable.
If Netlify goes down, you won't be able to publish, but your statically rendered site should still load just fine unless you are using it to make dynamic queries on the fly (which is, I think not generally done for Gatsby, but very possible to do)
Re: Use Netlify Functions and the Twitter API v2 as a CMS for Your Gatsby Blog
#8Not sure if using 3rd party services for a CMS is a good idea. What happens if this API or Netlify goes down? Doesn't seem reliable.
You are always relying on a 3rd party somewhere down the stack that's not a reason to dismiss a solution alone.
Re: Use Netlify Functions and the Twitter API v2 as a CMS for Your Gatsby Blog
#9Re: Use Netlify Functions and the Twitter API v2 as a CMS for Your Gatsby Blog
#10Earlier quoted context omitted.
You are always relying on a 3rd party somewhere down the stack that's not a reason to dismiss a solution alone.
Given Twitter's track record on APIs, there is every reason to dismiss this solution.