Skip to content

@apriandanailus

Migrating to Gatsby

Journal, Tech1 min read

As I discovered static site generator frameworks, I found this could be the future of CMS. But, somehow it is still quite difficult to navigate the whole concept of this framework. Especially, those who are heavily using CMS like Wordpress, and other blogging platforms.

But, What exactly Static Site Generator (SSG) is?

So, Simply put, a static site generator is an application that takes your site content, applies it to templates, and generates a structure of purely static HTML files ready to be delivered to visitors. The application itself can be written in any language: Ruby (Jekyll), Go (Hugo), JavaScript (Gatsby, 11ty).

Static site generators (SSG) applies data and content to templates, and generate a view of a page which can be served to the visitors of a site.

The greatest difference between a static site generator and a traditional web application stack, is that instead of waiting until a page is requested and then generating its view on demand each time, a static site generator does this in advance so that the view is ready to serve ahead of time. And it does so for every possible view of a site at build time.

While I am still using Wordpress for my blog (blog.apriandana.com) I will soon migrate all content to Gatsby. I believe this is still a long way for SSGs to take over the CMS game, but it offers pretty much anything a modern site should have.

I will cover my opinion on using Gatsby in the next blog post.

See you until the next post!