Blog Network: SEO Content Writing MathematicsDeveloper DiaryLiving with BipolarPortfolio
  • Content Writing that Counts
  • Do you want more business from search engine traffic?
  • Get Help

All About Static Websites and Headless CMS

I have a message!

You can still make a static HTML-based website in 2021. It could be the best solution for you depending on your needs. I can see it in use for a Portfolio or Landing Page. 

Use it in any situation where you only need CSS, HTML, and JavaScript. Use the least powerful solution for your needs. Not everything requires the power of WordPress or other PHP-based blogs. 

I’ve noticed a trend where static sites are now in vogue. Not in the traditional way that we are used to. Through static site generators and Headless CMS. This really isn’t a solution for small business. These solutions are designed for enterprise level websites who need a lot of dynamic parts. This is one way to speed up their websites and make them more secure.

I’m looking to at least try out the workings of a Headless WordPress for at least one of my blogs. Just to get to see the technology in action for myself. This is possible with Gatsby which I will discuss later.

5 Reasons to Consider Headless CMS

One trend that is becoming popular is Headless CMS. This means that the backend is decoupled from the Front-end. It uses a content API to send information to internet applications

1.The website is static and is built based on server requests

The website is generated as it is accessed by the browser. Only loading what is required for the page at build time. This creates a better user experience.

2. It is more secure (no more fear of injection attacks) 

The website is served as a static HTML site. Stored content is sent via API from the backend and is being loaded into a front-end display. Therefore you are safe from hacker techniques like SQL injection. 

3. It is faster 

Because it only pushes content to the Front-End it is super fast. It takes out the middleman in displaying that content. 

4. The content team can work independently of the Dev team 

Content can be worked independently of the dev team. This means the content team only has to focus on their content. 

5. Can publish more than to the Front-End 

A headless CMS means that the API doesn’t just have to push to a “head” something like a website. It can push out that content via the API to many applications on the internet. So imagine, updating a website and a mobile app with the same content through API access. It is pretty cool. 


One of the easiest ways to get started with Headless CMS is with something like Gatsby.js. The reason why I prefer them is because they specialize in Headless WordPress. Which means that I can still use the same content editing system that I know and love. Meanwhile I get the blazing fast speed and security a static site brings.

You can check out the tutorial here.

This link will take you to their cloud hosting platform. This makes things way easier than having to do thing manually yourself. I am going to give this a try in the upcoming months for one of my blogs and see if I like it. I think what I’ll need to figure out is how to make a front-end theme to import the content too. I believe it only uses WordPress for content editing.

I’ve got a lot to learn! It would be so cool though if I could get all my websites setup on Gatsby.

Here are some articles on Headless WordPress for a deep dive on the topic.

  1. What is Headless WordPress?
  2. Headless WordPress: The Ups And Downs Of Creating A Decoupled WordPress
  3. Just How Niche is Headless WordPress?
  4. Headless WordPress: What It Is and How to Use It

The More Things Change the More They Stay the Same

It is so interesting to see us go from GeoCities to these complex websites with bells and whistles back to the basics of HTML, CSS, and JavaScript.

Would you like to try a Headless CMS?

Back to Top