I was done with Strapi after this comment (from the Strapi Slack):
mmm @flowen changing field names in Strapi doesn't rename them on the DB side
I wouldn't suggest that if you can avoid it
I noticed the same developing experience I had when I was working on dateanomad with Meteor js. Out of the box, everything seems to work great, but once you fiddle a bit and you want something extra or custom.. things get tough, break or just plain annoying. Why the hell would you be able to change field names but won't rename in the DB so everything has to be done manually again? This means keeping 2 resources up to date and I decided to completely drop Strapi from my workflow.
I was hustling with the idea that I could scrape everything straight into MongoDB and source it from there to Gatsby.
Then discovered Gatsby-gram (case study here), a Gatsby clone with a Nodejs scraper. Almost purrrrfect 😻 Apparently Instagram has a great and open Graphql/json endpoint, which they utilise to great extent. I'll have to re-write this to cheerio and Nodejs myself. The scraper (though now an error because of a change in the IG API) was a great example of how to download images as well.
I started the day, pondering about Strapi. When you've worked on something for a bit: trying to understand it, feeling excited by the possibilities and "super powers" it might give you, it is such a drag to dump it and start over again. It felt like my spirit was demolished and I would rather give up and focus on other things. Instead, how lucky I was to find such a great example. In the next few days, I will hopefully finish my scraper. And then I'll be able to say that in hindsight, this was a great decision!