So, if you follow me on twitter, you know that I’ve been working on a portfolio using GatsbyJS. While I find it a necessary evil to make a portfolio (I’ve worked on making portfolios more often than I’d like to), it’s been… a lot of fun working with GatsbyJS and being able to learn so much about it (and by extension, of ReactJS’) ecosystem (and yes, it’s been great even though you may find me kicking and screaming on twitter about this whole
ordeal process of making a new portfolio.
While working with Gatsby in this project, I got a taste of GraphQL, but with GatsbyJS being a new technology that is finding it’s place as a technology in real time, the project’s documentation is work in progress. It seems to try to do a lot at once, considering GatsbyJS is this sort of hub of what’s to come in the internet of the near future, including introducing GraphQL to those who might be seeing it the first time. There are those who enthusiastically proclaim that GraphQL will definitely be much needed tool of the future of the internet, I’ve at least had my curiosity piqued just trying to get some of the cool performance oriented features that GatsbyJS relies on through GraphQL.
Of course, Gatsby’s documentation appears to try and give developers a taste of GraphQL on a “need to know basis,” and the prevailing assumption is that new Gatsby users are crafting blogs, but for some (like yours truly), the old slow, non decoupled CMS-as-a-blog service/stack works just fine for the time being. Unlike many of the tutorials on youtube would like to assume, I’m actually building a portfolio, with potentially some unorthodox patterns than those seen in static generated blogs. I decided it might be worthwhile to take a deep dive into GraphQL, and I’m going to use Robin Wieruch’s “The Road to GraphQL”, since I found his “The Road to Learn React” to be a great learning resource.
In Wieruchs’s “Road to” series, he issues a challenge in the opening pages of each title. He asks that readers write or youtube about what they’ve learned from each chapter, with the seeming intent of creating a robust community of crowdsourced materials to support the book series’ content (not a bad idea if correct). So while, the problem I found myself stuck on might have been solved by some of Robin’s other content on his site, GraphQL is a powerful tool that will most likely be an essential tool in many future web products, so I will be blogging about my learning while reading “Road to GraphQL.”