Whether it’s a headless solution or a more traditional static generator plugin, there are a few reasons why static sites are popular. Gatsby is an example of a headless WordPress solution, where the WP GraphQL plugin enables the GraphQL API, which is then accessed by Gatsby to generate the static site pages.
#Wp rocket json query strings full#
This is very different from using WordPress as a static site generator, which makes full use of the theme and plugins generating the frontend of the site, and saving the generated pages as HTML files. The WordPress theme and any plugins that would affect the output on the frontend of the site really have no effect when using WordPress as a headless CMS. Headless WordPress refers to not using the frontend of the WordPress website at all. This solution could be a single-page application or a static site generator. With a headless implementation, the CMS only acts in the capacity of content editing, and the frontend is served by another solution.
A headless CMS uses a decoupled architecture to allow it to act as a backend service accessed via an API (or SDK). Making an API available to query the data from a WordPress database is what enables this headless functionality. Headless WordPress is a term that has seen increased interest since early 2017, especially since WordPress 4.7 was released in late 2016, which marked the inclusion of the WP REST API. Headless WordPressīefore we get into the details, it would probably be a good time to talk about headless WordPress. I know and respect many folks who have tried static site generators like Jekyll, Hugo, and Gatsby, but it’s just not something that ever seemed useful to me. While I knew about them, dynamically generated content using either a framework like CakePHP or CodeIgniter or a content management system like Drupal or WordPress was my preferred choice. Back then, static site generators just felt like too much extra work for very little additional benefit. I discovered ASP and then PHP and MySQL, and I’ve never looked back. Then, one day, a question from a friend took me down the rabbit hole of dynamically generating content from a database. I used things like tags for scrolling text animation, tables for layout, and styling was either done using the style attribute, or inline CSS, with a few JavaScript alert functions here and there. My first site was hosted with GeoCities, and looked a lot like this. Like many, I started building websites using good ol’ HTML, CSS, and a little bit of JavaScript. There’s one chapter in the history of web publishing I’ve never quite understood - static site generators.īefore you flip out and start quoting all the benefits, let me start by saying that I do know why they exist, I’ve just never seen the point. Aggressive Page Caching With Fewer Rules.Static Site Generator Plugins for WordPress.
0 kommentar(er)
