11–20 of 22 posts
Not 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.
- My ISP
- My power company
Earlier 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.
I can host a blog such that it only requires 2nd parties: - My ISP - My power company
edit: Also they're third party. 1st is you 2nd party is the customer (The blog audience).
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.
I would just make a request to Twitter for the profile on build for the two sites. Do you expect to update your profile more frequently than your two sites? ISTM, you can just trigger manual builds when you do update your profile, instead of using a function, which is going to constantly be looking up and returning the same information.
Not 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 the Twitter API is down, then you'll have blank spots on your page where there are supposed to be tweets. 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)