Wordpress is the most popular way of serving content on the web. According to W3Techs, WordPress is used by over 35.5% of all websites online and is one of the fastest growing CMS-es in the world to date. In spite of its popularity and how beloved its portability and extensibility is in the world of CMSes, the traditional WordPress model butts up against the JAMstack approach of building sites as statically as possible. Traditional WordPress sites are built using a LAMP architecture, which stands for Linux, Apache, MySQL and PHP. As the name suggests, a LAMP stack requires an apache server and linux configurations to handle any routing and serving of static assets. It moreover relies on PHP running on the server to process requests and render pages and assets on the fly. The JAMstack presents a critical change to this approach by moving up a layer. Instead of giving servers the reins to render assets “dynamically”, the JAMstack skews in favor of the client and browsers run the show.
When it comes to speed, security, and maintainability the JAMstack comes out ahead. WordPress’ reliance on servers in addition to its deep investment in plugins has made it far slower, and more vulnerable to attack than many of its contenders. Attaining the benefits of speed and security however doesn’t have to mean abandoning WordPress altogether. A key way to transition to the JAMstack while still using WordPress is to use it like a headless CMS with the help of the WordPress REST API. The API turns content saved in WordPress into a consumable API that developers can then use alongside a static site generator or framework of their choice. This not only makes a site more and secure, it also enables developers and content authors to contribute without getting in the way of each other.
For more on working with the JAMstack and WordPress, check out this case study covering how web agency WayFx increased Perfect Keto’s site speed by over 87%.