Gatsby with Contentful... or not.

Saturday, March 16, 2019

2 min read

About this post

Today is a “fail!” post.

It happens a lot in software engineering, believe me! Everyone brags a lot about their successes, which is fine, you should too, but we tend to forget that success only happens at the end of a looooong road full of failures.

On the plus side, this will be a short read 🤣

By the way, thanks again MPJ for articulating all this so clearly, go watch this video:

via GIPHY

Well… hum… not really 🤔☹️. This how-to would have been useful If I did not already have a Gatsby blog because it describes how to start a new one from a starter.

Gatsby’s documentation

So, Awesome! I found another one from Gatsby’s documentation website: “sourcing from contentful” .

This one seems to better fit the context of this blog.

via GIPHY

Bwah 🤢 seems too much hassle.

Let’s recap:

Time to re-evaluate the effort based on my “business” need:

Me talking to myself using “business” hat versus “dev team” hat:

Well, let’s decide to avoid Hype Driven Development and just stick to doing what is strictly necessary from a “business” point of view!

via GIPHY

Conclusion

So, I’ll just keep pushing my markdown content to the repo… and refactor this later if I really need to, and if new business requirements emerge.

Also, I – the dev team – still learned a few things in 20 minutes about Contentful + Gatsby, but did not want to extend this time further.

I hope you enjoyed this post! If you have any feedback about how it make you almost laugh, fix my lame jokes, content, or my english, send me a message on Twitter.

👋


portrait

Written by David Lacourt who lives in Senlis 🦌, works in Paris 🇫🇷, 🧡 building things with code.