This blog is built with Gatsby.
March 20, 2019
6 min read
NOTE: this should have been one of my first posts, so it’s kind of a “pilot” post.
Gatsby is a free and open source framework based on React that helps developers build blazing fast websites and apps
GraphQL is a query language for your APIs and a runtime for fulfilling those queries with your existing data
GraphQL here is used to fetch data from different sources, which allows aggregation of content from a myriad of origins:
- local “classic” React JS views,
- Web services / REST endpoints
- markdown files
- … and anything else because it is extensible!
Gatsby comes with a lot of starter templates provided by the core team and the community. This is really handy and one of the reasons I chose Gatsby: to quickly prototype my website.
It’s the Open Source dream! You get huge quantities of free shared stuff, and you just have to assemble and customize it to make it your own. You can still study all the code and engage in diverse ways to improve it for others who will, in turn, reap the benefits.
- I want to add internal links (anchors) on headings, there’s a plugin for that
- I want to show the reading time of each post, there’s a plugin for that
- I want to use fun icons, there’s a plugin for that.
functional plugins, source plugins, and transformer plugins
All this gives me the opportunity to quickly add functionality with the plugin abstractions which do not require me to fully understand how they work. I could create my own plugin if there I cannot find one filling a particular need. Just finding existing ones spared me a lot of time. I can thus concentrate on the “business” which is writing posts!
Now that I have started writing content, it feels like thoughts are forming by themselves. Kind of a meditative practice where you let the thoughts out. Then comes the “refactoring” where you reorganize everything to make it more linear and express some goal whether it’s telling a story or describing a product or whatever. Instead of a mind dump. Like this post. 🤣🤷♂️ When I’m writing, usually it sparks another idea and I feel the urge to catch it and carve it on the screen with words before it flies away. Like capturing fleeting thoughts. Then they are gone. And give way to others. It’s also cathartic in the way that some persistent thoughts in your head can instead persist inside a post. And as you rework them iteratively, they take on a shining quality and give you the opportunity to make this second brain memory even better. I acquired a new appreciation for books and the mindset of authors of said books. Mind meandering… Flushed the mental toilet. Now back to technical stuff, ready? burp
The Starter already comes with a great list of plugins. I won’t describe how to start, I followed a post that already does this perfectly (thanks, by the way!).
This one is here to transform your markdown into blog post views,
- “Support for an RSS feed”? You can add my blog to your RSS Reader… wait… this is not 2009?!
- “Support for code syntax highlighting”: well, you might have read some of my previous posts, and the code inside wasn’t all that highlighted, merely shown. I might have missed something, here.
- “Includes plugins for offline support out of the box”: this is great, this blog is a PWA you can install it, it will download all contents and you can read the articles while offline. Also, it makes visiting this site much faster after the first time thanks to service workers!
Now that I’m fully into this, I kind of regret my initial choice of starter. Lumen starter I’m eyeing at you, you look so nice with this sexy sidebar (even though with my profile pic of a non-hipster face, that might not be as good) Maybe I can just migrate to another starter?
Other possibilities would have been to use:
- Jekyll, if you’re into Ruby,
- Wordpress, if you’re into PHP or part of 33% of websites that have chosen it,
- Hugo, if you’re into Go,
- Next, another one for React from Zeit,
- Nuxt, using VueJS,
- … there are many others!
ownership of your own content forever
In a way, every post on lacourt.dev is my own content, but as everything is under MIT License, this can also be your’s or anyone’s. Some site could even use crawling robots to find it and publish it on their platform to monetize it. So my goal in the future is to find the best way to push my posts to other platforms (dev.to? Medium? others?) to spread the word, but bring everyone back here. Mainly because most of my posts are explaining how I’m constructing the infrastructure they rely on.
Gatsby is a Static Site Generator. As the name implies, SSRs have fewer security issues when deployed on a live server, because, well, everything is static. You will not expose your API keys, API calls, or anything else, all the content is already included in the pages. Just don’t put your keys on GitHub and you’ll be ok 👌🏼
I will be the main contributor & developer for this blog. Maybe you will contribute and that would be awesome! But I would still be the core maintainer. The website is a blog. This blog will not have many different pages. I don’t need a full-fledged CMS. So a static site generator like Gatsby is a perfect fit for my use-case.
And I can host a simple stupid static website on a free service, no need for a big server with a database, etc. So fewer maintenance costs for me 💸
See also this article.
In this post, I wanted to explain the choice for the technology stack for this blog. If it is not clear, well, maybe I should not have written it at 5am or you could help me with proof-reading 🤣
Anyway, I learned a ton on the way and am quite satisfied with this blog as a result.
I hope you too learned a few things.
Thanks for reading this blog, If you have any questions, please use the Github Repository’s Issues to start a conversation, or use Twitter: my DMs are open.
Tweet Follow @doppelganger9
Written by David Lacourt who lives in Senlis 🦌, and works in Paris 🇫🇷, and 🧡 building things with code.