Starting my blog with Gatsby

Finally my blog is up and running!

A couple of years ago I thought about creating my own blog and start typing my thoughts, learnings and notes about software and sometimes adding a bit of my life events.

The idea behind this was to write things down to remember the stuff. To write things down so I can come back in the future and "access my memory".

I have plans to publish here my side projects as well. Maybe sooner than later. I love to test new techs and make small projects, by they usually end up in the bin or forgotten in the file system or in a repo in Github. My idea is to deploy them together with this site and make them accessible for other to check them and reuse them. "Sharing is caring" :)

If the person who is reading this is Rafa in the future, I just wanna say "Hey Rafa! This was your first post. Remember to keep writing". If it is someone else, I hope you enjoy the blog content and you can get the most of it.

For all of you here my nerdy welcome message!

export class WelcomeMessage {
  constructor = (name) => {
    this.name = name;
  };

  greatings() {
    const greatingsMessage = `Hi ${this.name}! Welcome to my blog.`;
    console.log(greatingsMessage);
  }
}

const welcomeMsg = new WeolcomeMessage('my friend');
welcomeMsg.greatings();

Technologies used and why

I chose Gatsby to build this blog. Behind the scenes also React and Styled Components to code the different templates and components. As global state manager (for the theme basically) I'm using Recoil. And as hosting I'm using Netlify.

The main reasons behind are:

1. The speed Gatsby have when loading all pages
2. The big ammount of pluggins to extend the basic functionality in a very easy way. (For example, image optimization, code blocks styling, ...)
3. Writing my content using the wonderful benefits of Markdown.
4. React and StyledComponents. I love this combination when building websites. It is fast, intuitive, and easy to have a very wel structure,
5. Netlify makes things extreamly easy to deploy, with preconfigured pipelines for this kind of project, bound to GitHub branches, which makes very easy to push new blog posts just as a new markdown file.

Disclaimer

Keep in mind that all the articles I write here are based on the knowledge about the topic I had on the specific moment I wrote it. That means, it might not be a perfect implementation of many things, but at least it will be the implementation that worked for me in the moment I wrote it.

Firthermore, I will probably not update the code in all my posts, so probably they might get deprecated at some point. I hope it won't happen very often, but if so, just take the article as guidance, and then use the most up-to-date techniques, commands, etc.