WordPress Blueprints: a real fix for dev environment headaches
Had to onboard a new junior dev last month for a big WooCommerce project. First task was simple: set up the local environment. He’s a…
Had to onboard a new junior dev last month for a big WooCommerce project. First task was simple: set up the local environment. He’s a…
I got a call from a client last week. Their last developer bailed, and they had a “simple” request: add a new delivery option to…
A client’s Resources section had meta box code scattered across functions.php and two include files, so every small change broke something. One reusable meta box class moved the registration logic into a constructor and the form HTML into a template.
A simple VIP discount request stalled on a 1000-line, undocumented function nobody understood. The fix was not more code, it was documenting the intent behind it. A short comment block up front saves hours later.
A client side project plugin grew into an operational crisis of spaghetti code. The lesson: give even a small plugin real structure from day one, a main class and separated concerns, so it stays maintainable.
I got a call from a client with a membership site that’s been around since the dawn of time. They wanted to upgrade their security,…
A client’s product filters broke after a routine WooCommerce update. The old jQuery no longer works with the new block-based, state-driven output, so here’s how to extend those blocks through the Interactivity API instead.
A client wanted to become a WordPress developer but was drowning in acronyms. This is the order I would learn things in: the platform basics, HTML and CSS, JavaScript, PHP, MySQL, then building real projects.
What happened when a client’s multi-block plugin got unwieldy: how we reorganized the blocks, automated registration, and split out shared assets so it kept scaling.
A client hit me up last month. They needed a slick video section on their product pages, with dynamic content and a different video for…