You’ve heard the saying: “opposites attract.”
It certainly is true of the two concepts explored in this post.
On one side, WordPress. On the other, static sites.
The first represents the old guard of monolithic CMS; the second, the new frontend wave.
Despite their apparent differences, we hear more and more about WordPress static websites, WordPress static site generators, and so on.
It might sound counterintuitive, but when you think about it, why wouldn’t you want the best of both worlds?
That’s exactly the question I’ll explore today. More precisely, I’ll have a look at:
- Why you should use WordPress to generate static sites
- The benefits & limits of this approach
- The many existing WP static site generators
The rising interest for Jamstack in the WordPress community is quite exciting to observe.
Let’s jump into it right away!
Why use WordPress to generate static sites?
Pairing WP and static sites doesn’t strip away power from the site editors. WordPress users can still use the popular CMS to create and edit content.
So where does the process differ? After an editor hits “Publish”, the site content is exported to HTML, pre-compiled static files ready to be served, instead of the usual PHP-generated views.
There are many available tools & plugins to accomplish this. I’ll list them later on.
However, if terms like Jamstack, static websites, or headless CMS are unfamiliar to you, there are a few things we need to clarify before going further.
This section will lay out the differences with a standard WordPress setup and a Jamtack-inspired one. I’ll then highlight the benefits & limitations of the latter.
→ Read the full post here
Top comments (0)