3 ms·

I would also look into the myriad of static site generators that are probably much faster than the WP static site plugin and use modern tools and libraries. ht

I would also look into the myriad of static site generators that are probably much faster than the WP static site plugin and use modern tools and libraries. https://www.netlify.com/blog/2016/05/02/top-ten-static-website-generators/ https://www.netlify.com/blog/2016/05/02/top-ten-static-websi... Roots is mentioned, but the team has since developed Spike which is built on a more modern stack: https://github.com/static-dev/spike https://github.com/static-dev/spike https://www.spike.cf/ https://www.spike.cf/

faitswulff 10y ago
I've looked into Jekyll before, but I'd prefer to use a plugin for ease of migration and Wordpress's user experience.
partiallypro 10y ago
This all defeats the purpose of using Wordpress and making it user friendly for clients. Wordpress could solve a lot of security issues by using a newer version of PHP, but they are scared of breaking legacy items. Also using things like Wordfence and Cloudflare solve most of the basic Wordpress security issues.
- rmccue 10y ago
  > Wordpress could solve a lot of security issues by using a newer version of PHP, but they are scared of breaking legacy items. There's nothing stopping you from running it on PHP 7.1 (and we are on our client sites). There's not a great amount that could be gained by WordPress (the project) by dropping support for the older versions; the main gains would be namespacing and closures. That said, I do think it's time to drop 5.2 support. 5.2 is down to single digit percentages: https://wordpress.org/about/stats/ https://wordpress.org/about/stats/