In today’s post, I explore the reasons for moving my blog from Squarespace to GatsbyJs. Follow me in my journey!
I'm going to move my blog to a new platform! Since I've been coding in React for some time and I've been a great enthusiast for static-sites and server-side rendering for some time, this is it!
The point here is to document each step so that anyone can follow the process and see how that's done.
Here are the details:
- I'll be using WordPress as a Headless CMS (through their REST API) to fetch posts and feed my React application. There are many possibilities when it comes to managing the data with Gatsby but I found that for my use case, posting to WordPress is the easiest.
Once I'm a bit more comfortable with Markdown, I'll probably write my posts directly in .md and query them using GraphQL.
- The blog will be hosted on Netifly. Netlify is a great hosting service that allows you literally plug your project right from Github and have it deploy on command from your terminal.
Every time you push a commit you can choose to update your site. Pretty cool if you ask me.
- The styling will be done using styled-components which provides a great plugin in Gatsby. If you're not familiar with Styled Components, it literally derives from the "component" philosophy of React.
Styled-Components will generate class names for your components so that your style can't possibly break anything. Writing your styles that way also mean you have access to the power of ES6 to structure your properties.
The reason behind that move is to push myself to publish more regularly and to explore the possibilities offered by GatsbyJS.
I can't wait.
I'll be writing about the first step next week about migrating data to WordPress.
Let me know what you think in the comments section down below!
FreeCodeCamp has recently started an audio podcast. It's very good and you should definitely check it out!:
I've always been keen on podcasts, I think they provide a convenient way to communicate and present content.
- The format is generally short and easy to digest.
- Most of the time, there's only 1 person speaking at the time so it's rather easy to follow and doesn't require deep focus.
- It allows you to learn/listen to content while doing something else.
While listening the the FCC podcast episodes, I realized that those were previously published articles or posts read out loud by Quincy Larson, Beau Carnes or many other contributors.
It was great to re-discover those in a podcast format and listen to great stories and insights on the web development world.
And it got me thinking.
I've always wanted to launch a podcast or/and a Vlog. I used to be a teacher (just like Quincy and Beau actually) and that ability to coach and mentor students, explaining concept, de-jargonizing technicalities was always something incredibly rewarding for me, and something I really miss in my current job. I launched a YouTube page no too long ago but failed to accurately assess the time I would need to publish quality videos (preparation, editing, etc.).
So it got me thinking...
Why not trying the same approach with my own blog. I would be reading out loud my articles, perhaps adding thing in the process (let's be totally honest, I'm not able to accurately read something mechanically without making edits, additions, revisions, etc, I'm a programmer after all aha).
So I'm going to publish my read-out-loud-articles on iTunes as podcasts in the next coming days (I'm working this weekend so I'll probably record a bunch of them on Monday).
What do you guys think?
I think that would also be a great way to help me in my public speaking skills (I'm not an English native speaker 🇫🇷), my pronunciation and tone.