Pain Points of Web Development with WordPress

Re:Pain Points of Web Development with WordPress by badrequest on Thursday September 19, 2019 @12:07PM (#21017564)

> For example, imagine you build the plainest possible website, with static content. Do you want WordPress to run PHP on the web server every time someone visits a page? Of course not. But unless you install a caching plugin, that’s the situation you’re in.

Or, and maybe I'm being crazy here: don't use Wordpress if all you need is a static site?

[ Parent | on HN ]

Re:Pain Points of Web Development with WordPress by tomcooks on Thursday September 19, 2019 @12:14PM (#21017647)

Cue in Concerned Client #382716: "but then how do we update the website independently"

[ Parent | on HN ]

Re:Pain Points of Web Development with WordPress by earthboundkid on Thursday September 19, 2019 @01:30PM (#21018488)

NetlifyCMS :-)

[ Parent | on HN ]

Re:Pain Points of Web Development with WordPress by tomcooks on Tuesday September 24, 2019 @05:09PM (#21064665)

Needs server side is, most Concerned Clients have a cpanel shitsite with PHP and mysql

[ Parent | on HN ]

Re:Pain Points of Web Development with WordPress by billars on Thursday September 19, 2019 @12:43PM (#21017956)

caching is not about loading a static version of your website, you could cache parts of the page and/or regenerate whole pages if content changes; diverging from the intent of the post you could also talk about caching php objects in some persistent way etc.. none of which is covered by out of vanilla wp even if the core exposes an object caching api https://codex.wordpress.org/Class_Reference/WP_Object_Cache.

[ Parent | on HN ]

Re:Pain Points of Web Development with WordPress by 4mpm3 on Thursday September 19, 2019 @12:26PM (#21017769)

This means "even if your WordPress site is as simple as you can imagine, there's still PHP running to make it happen"

[ Parent | on HN ]