Комментарии:
Thanks Paul, so much good info :)
ОтветитьGreat video... Quick off topic question - which plugin and email service do you use for SMTP
ОтветитьI’d love to see an approach for big sites, for example, how to setup a VPS and allow Redis. That’s poorly documented but this seems game changing.
And great video as always ❤
Perfmatters?
ОтветитьTruly nice video, thank you!
ОтветитьCPT-UI is kind of obsolete nowadays. Most people work with ACF or Metabox where you can create taxonomies out of the box.
ОтветитьAwesome that ASE plugin, never knew of before! And Blocksy always for the WIN
ОтветитьThe easiest way to optimize WP is to remove it from your tech stack. We recently dumped WP and converted everything to cloud micro-services. Cut our hosting bill to a fraction of what it was with WP as our CMS, not to mention the speed and SEO improvements basically paid for the upgrade.
ОтветитьOh wow...i didn't even know this was possible. I'm running 26 plugins for an e-commerce and hate having this many plugins slowing my sites down. Just recently i replaced my BackupBuddy and now using Jetback5 (didn't even know my host provided this) and thanks to you also! I'm gonna dive into this ad this seems like a gold mine for lightning websites. A big thank you Paul!!!
ОтветитьBrilliant as usual, Paul. Thanks for your hard work.
ОтветитьCan't stress enough how important hosting selection is when building a site for yourself or a client. It makes all the difference when it comes to overall performance. Additional plugins can only fix so much.
ОтветитьI see no harm in just using the code snippets plugin. It’s not exactly adding bloat to the front end of my site.
ОтветитьAnother great video. Thank you Paul. I am using Block themes more these days and therefore the need for a child theme is no longer really needed. So what I do with regards to solve the lack of a theme based functions.php file is I create a Must Use plugin, call it something like site-functions.php and place all CPT coding and any other functions I need in that and enqueue a JS file as well if needed. You could also do this same approach with a Classic theme and that way if the theme is ever changed in the future, the functions remain and are not lost, like CPTs for example. This also prevents the must use plugin to never be deactivated or removed by the client by accident. Just my thoughts on that. Thanks again for a great video Paul 🙂
ОтветитьOne of my all time ❤ video tutorial..
Ответитьnice, i always disable CPTUI after going online. That's exactly my workflow <3
Ответить