Running a content driven site can become bloated. Losing its appeal for version control, user permissions, and constant updates for plugins. Especially if using a Content Management System like Wordpress. And when your site becomes too large, migration can be an enormous headache for your team.
Like most blogs, many run as Dynamic sites. Every time a user hits sites the page and content are pulled from a database and rendered in real-time. This adds complexity to what should be a simple process. I mean you are only looking at images and text anyway so why should this be rendered every time? Would it make more sense to have it available in the first place?
Not only that but before rendering happens, the site communicates with every plugin that is connected. Which adds time and more complexity. So when a feature or the site is not patched with the latest update, it can break. Causing errors or keeps the site from loading. I am sure you are aware of many articles online articles about fixing Word Press’s white screen of death.
Then, when you are fed up with this system, you realize how painstaking it will be to move your content elsewhere. Like copy and pasting your posts. This is because at first, we find that using site builders may seem easy and there are plenty of them out there. Don’t get me wrong, I love the idea of site builders but over time you may find yourself stuck in a walled garden. I found myself in this position when using SquareSpace. When I decided to try to move elsewhere I found myself with a huge problem. Both content and the domain resided on their servers so I could not simply move them to another system. The domain transfer, for example, I had to go through a month-long process to get it moved. My site even ended up going down for several days and it was awful!
Benefits of using static site generators
To give a quick summary I would say that a static site generator takes the content, applies it to your template theme, then creates a static website. They are fast, secure in nature, and don’t depend on a database to render content. Of course, they reside on a server but everything is already built and is served before the user visits. Only updating when you change or add more content. It is simple and there is a big benefit to this. Your content resides as text files in your repository. Enabling you to connect to any of the large numbers of headless CMSs. Fed up with one? You can move to another. Want to use a separate host for your images to have better pricing? No problem! Want to use Github for free version control? You can do that!
What about forms or subscription-based content? Can you even do that? The answer is yes! There are plenty of services that provide those features like Netlify. I for example like using Lambda functions on AWS to run my forms for cents on the dollar! And think about this. Wouldn’t you rather to use marketing software as you did with Wordpress? Well, chances are they have code snippets you can add to your site. Plus all the ones that don’t have a Wordpress plugin. And with services like Google Tag Manager you can use all sorts of marketing and SEO tools.
So with the simplicity of a static website you can focus most of your energy on your content. No more having to worry about depending on 3rd party services. Or the fact that you need to pay for version control for your database. And you can rest assured that in the long run, you have the ability to change without be having to break your site.
Of course, this is not the best solution for everyone but it should be worth a closer look. There are many kinds of static site generators out there with their own perks and drawbacks. For anyone who wants to spread their resources, it can be a great tool to use across this tech landscape.