Awesome. I’ll just leave the comment there in case anyone else face the same problem.

Ah I see...thank you for the detailed explanation. Actually, I’m new to Gatsby as well so I’m still trying to wrap my head around how it works. In my current Gatsby project with no CMS whatsoever, I can still query for posts that are stored locally within my project. There is no system per say that manages the content; my job is to just write things in Markdown and put the files in a posts directory or something like that. But with Cosmic JS (or other CMS), I can manage my content in a platform that is separate from my Gatsby project. Then, I can just fetch (or transform) the needed content with the Cosmic JS API. Something I like here is if I want to switch from Gatsby, I can just switch and just fetch things as needed with the Cosmic JS API instead of migrating all my project-stored content into the new website. The website and its content to display are not coupled together (which I guess is where the ‘headless’ term comes from). At least, that’s my current limited understanding.

This an excellent comment. With my short experience trying to build a GraphQL-based app, I guess it can be seen as if I’m trying to learn too many things at once: HTML/CSS NextJS Heroku Now CircleCI Apollo (Client and Server) NodeJS and more... But I don’t think it’s overwhelming because all of them gel together into a cohesive whole, that being the app. I’ll learn whatever it takes to get things done, even a new language if I have too. Though, I can understand the author’s message. Maybe the main idea is not “specialisation is king” rather “at any point in time, focus on as few things as possible. Add more to your plate once you’ve learned enough”. A better compromise would be to specialise in something AND mediocre in many things. Mediocre is better than knowing nothing at all since that seemingly mediocre knowledge can aid your ability to see the gestalt.

CosmicJS looks interesting. I normally use Gatsby for blog-like sites and I’m not sure how Cosmic JS fits within that framework.

This looks great. I’ll be sure to try it later. How customisable is the generated app?

Hello, Have you read this Github issue ? It seems to be related to your Babel setup. If you’re using create-react-app , try importing babel-plugin-relay . Here’s a detailed instruction on how to do it.

Wow, this looks neat. I’ve never tried AWS’ AppSync and Amplify. I’ll keep this article in mind if I intend to use AWS in the future.

If you are willing to pay, Wes Bos has a course ( AdvancedReact ) that covers Apollo, GraphQL, and some other technology relevant to building a GraphQL-based app. It’s a good course and a good fit for those who likes to learn from videos (there’s a repo too which is public btw). It covers everything - deployment included. For a free guide, I highly recommend How to GraphQL . It’s insane that it’s free considering the things you learn from it. Similar to Wes Bos’ course, you’re also building a full-stack app except the features are not as complex. Deployment and proper authentication are not covered as well. I’ve written a more detailed review here if you’re interested. Other than that, the Apollo docs is excellent and be sure to check the recipes section in the sidebar when available (For example: Pupstagram example app recipe). I’m still a beginner as well and the above (and countless random articles) had helped me learn enough to build an app (a habit-tracker).