CMS is the mechanism that makes a website even if you do not know the web, but many CMSs such as WordPress which are now the mainstream generate pages by “dynamic generation” method that generates pages every time visitors visit the site.
However, the current trend of shifting from such CMS to CMS using a mechanism called “static site generation” where pages are generated in advance by HTML beforehand is active among overseas developers.
and the reason is that here We’ve been thinking about the static site generation approach, and we’re really excited to see how this works.

Problems of Dynamic Site Generation CMS

• To generate pages per access, you need a corresponding server.
• There are a number of problems with using database servers, both in terms of extensibility and not being able to manage distributed versions of data.
  If you’ve ever had a WordPress article that went out of trouble with your server, or was overwritten by someone else.
• There is a high security risk as CMS must always be running on the server.
  The other day, there was an attack on WordPress.

In short, most sites don't need to dynamically generate pages every time and that means server maintenance costs or security risks are going up.

benefits of static site generation

• Page creation is done in advance, which lowers server cost.
  If you like, you can host it with free services such as Dropbox and Google Drive.
• Because it does not use a database, distributed version control is possible with Git etc.
  There is no risk that an article will go home or be overwritten by someone.
• security-safety because the programs that generate pages can be isolated from parts of the Internet

Problems with Static Site Generation

• not currently available to anyone other than website creators
• be not suitable for sites that are large and frequently updated

next article In this article, I will explain how to create a site using static site generation tools.