5 ms·

I think if WP ever finds a way to do two things: - continuously serialize WP to static files - Make it easier to work with Wordpress as a CRM (No Code or at t

I think if WP ever finds a way to do two things: - continuously serialize WP to static files - Make it easier to work with Wordpress as a CRM (No Code or at the very least don't force developers to touch PHP) JAM stack would near instantly cease to make any business sense (though developers would still love using it of course). A lot of the issues with Wordpress are sort of long-tail -- combinations of plugins exposing leaks in the abstractions, etc. BTW, if anyone is working on solving this, I'd love to know about it.

ozorOzora 6y ago
Or you can just roll with JAMstack as it's literally about what you're asking for.
- hardwaresofton 6y ago
  The problem I'm saying exists with JAM stack is that it's great for developers but bad for non-technical people -- wordpress is the opposite, and if I could get JAM stack properties out of Wordpress, I wouldn't use JAM stack for any projects which involved having non-technical people modify the site (which is a lot of them).
  - illuminea 6y ago
    You could check out Strattic which gives users the best of both worlds - edit your site as usual in WordPress, and click a button to deploy a static, Jamstack version of the site. All the power of WordPress with none of the headache. https://www.strattic.com https://www.strattic.com
marc_io 6y ago
> continuously serialize WP to static files Any cache plugin for WordPress does this already, but if you mean something that does this in order to host elsewhere (like in Netlify), WP2Static is a solution.
- hardwaresofton 6y ago
  Ah thank you -- WP2Static is something I didn't know about. Do some cache plugins actively walk your site and generate the pages? How do they handle when user login plugins are present? I'd expect a naive/basic caching plugin to add to the cache when a page was visited, not necessarily ahead of time.
  - marc_io 6y ago
    This depends on the plugin or cache system being used, but it can be done ahead of time, yes. Generally, the cache is created on the first visit and purged when a change occurs. Highly dynamic pages can be excluded from the cache by default, like the login or the cart page on an E-commerce website. Some solutions even allow to change the caching period for specific parts of the code, on the fly (fragment caching).

ozorOzora 6y ago

Or you can just roll with JAMstack as it's literally about what you're asking for.

hardwaresofton 6y ago
The problem I'm saying exists with JAM stack is that it's great for developers but bad for non-technical people -- wordpress is the opposite, and if I could get JAM stack properties out of Wordpress, I wouldn't use JAM stack for any projects which involved having non-technical people modify the site (which is a lot of them).
- illuminea 6y ago
  You could check out Strattic which gives users the best of both worlds - edit your site as usual in WordPress, and click a button to deploy a static, Jamstack version of the site. All the power of WordPress with none of the headache. https://www.strattic.com https://www.strattic.com

marc_io 6y ago

> continuously serialize WP to static files Any cache plugin for WordPress does this already, but if you mean something that does this in order to host elsewhere (like in Netlify), WP2Static is a solution.

hardwaresofton 6y ago
Ah thank you -- WP2Static is something I didn't know about. Do some cache plugins actively walk your site and generate the pages? How do they handle when user login plugins are present? I'd expect a naive/basic caching plugin to add to the cache when a page was visited, not necessarily ahead of time.
- marc_io 6y ago
  This depends on the plugin or cache system being used, but it can be done ahead of time, yes. Generally, the cache is created on the first visit and purged when a change occurs. Highly dynamic pages can be excluded from the cache by default, like the login or the cart page on an E-commerce website. Some solutions even allow to change the caching period for specific parts of the code, on the fly (fragment caching).