3 ms·
First, seconding everything dgb23 said in this thread. I think if you don't have a need for that dynamic stuff, yes a static site generator is a slam dunk in m
by xp84 3y ago
First, seconding everything dgb23 said in this thread.
I think if you don't have a need for that dynamic stuff, yes a static site generator is a slam dunk in my humble opinion.
The PHP/Wordpress model where pages are composited dynamically for each pageview was an idea that made sense 20+ years ago. Whereas today, regenerating 1000 (or 10,000) static HTML pages can be done in a few seconds anytime a new blog post is made, giving up-to-date sidebars, homepage and stuff. Other code which needs to be dynamic can usually be fully client-side. And for comments, I don't think almost anyone uses the WP comment feature anymore. It's either off due to spam, or delegated to Disqus or similar. That, combined with the constant stream of WP 0-day exploits, really argues for having your actual WP instance behind your firewall and serving your files from an S3 bucket or plain Nginx (etc).