| A blog has users coming from two directions. Readers visit the blog and consume the content. The application needs to serve pages that, as you correctly observed, are added occasionally, but don't change much. For a simple blog, there isn't much need for anything other than a static page. From the other end, is the author. Think of the blogging engine as an authoring tool. Just like any application, you can choose to use a tool that runs on your computer (e.g., Jekyll), or you can choose to use a tool that runs as a web app (like WordPress). The lines are blurred here, because it's entirely possible to just run Jekyll on a web server, using ssh to shell in and edit your blog files. If you keep your blog files in a Git repository on Github, as many people do, you can even do fancy stuff like auto-build on commit hooks. Then you can use Github as your authoring environment, and just commit as usual. I think your argument really stems from an architecture shortcoming in the way WordPress works by default. There is certainly never any good reason for a web page that changes infrequently to lack any form of caching. The real question is where you do that caching. Using something like CloudFare in front of your WordPress blog is just as valid a decision as is using something like Jekyll, or adding caching to WordPress through something like WP Super Cache. |