This is part 3 of my article series 25+ Tutorials on How to boost the performance of your WooCommerce store. This article shows how to improve Wordpress Debugging in your local development and/or staging environments.
By Erik. Erik Pöhler's Weblog.This is part 2 of my article series 25+ Tutorials on How to boost the performance of your WooCommerce store. This article focuses on completing the initial project setup of your Wordpress & Woocommerce store with a .env file where all your credentials and configurations can be stored in one place.
By Erik. Erik Pöhler's Weblog.Having worked on numerous Wordpress & WooCommerce sites over the last years, I have tried almost everything to speed up and improve page rendering times. Here I will share my key findings with you, put together into 25 tutorials. I hope they help you to achieve a fast, performant and easily maintainable WooCommerce store. This is the Tutorial overview and introduction.
By Erik. Erik Pöhler's Weblog.This is part 1 of my article series 25+ Tutorials on How to boost the performance of your WooCommerce store. This article focuses on the initial project setup of your Wordpress & Woocommerce store. Your main benefit of creating your project structure this way is that you will be able to update Wordpress, all of its Plugins and Themes with a single command in your Terminal. It's faster, more simple and gives you full control over each major and minor version in use. You will be able to revert a single plugin, keep track of core modifications you make and take advantage of the whole Packagist and WPackagist universe in your Wordpress & WooCommerce store.
By Erik. Erik Pöhler's Weblog.This is part 4 of my article series 25+ Tutorials on How to boost the performance of your WooCommerce store. This article shows you how to get started with automated Wordpress Deployments via GitHub Actions.
By Erik. Erik Pöhler's Weblog.I consider this guide an experiment, a test to see if its possible to replace the Wordpress frontend entirely. Getting rid of Wordpress frontend means getting rid of overhead like database requests, bad plugin code. Instead we get performant, clean templates and have more control over the frontend. This is a rather extreme step with downsides. You loose all the frontend logic, plugins, search result pages, category pages, archive and so on – you loose flexibility, have to rebuild all of the thinngs just mentioned from scratch. Still this might be worth it, if you love Twig, and want to bring it's benefits into the Wordpress cosmos. In this article I outline what you need to get started.
By Erik. Erik Pöhler's Weblog.
