Home
Developer positioning, services, proof, and recent writing.
Sitemap
A cleaner view of the live site structure, with current writing, archive material, and the practical housekeeping pages all in their proper corners.
Core pages
The pages that do the actual work of explaining who I am, what I do, and how to get in touch.
Developer positioning, services, proof, and recent writing.
Background, contribution history, and practical working style.
WordPress development, Shopify troubleshooting, technical SEO, and custom integrations.
Anonymized case studies and plugin footprint.
Technical notes, troubleshooting patterns, and current articles.
Email-first contact page for project inquiries.
Legal and utility
Less glamorous, more useful than people admit.
Featured articles
The strongest current pieces — the ones most aligned with the work the site is trying to attract.
Most software teams do not underperform because people are lazy or unskilled. They underperform because priorities, ownership, and definitions of done are unclear.
Most canonical issues are not plugin bugs. They are logic problems. Here is the audit process I run on client sites.
Secure Custom Fields forked from ACF. Here is what changed and how it affects existing WordPress sites.
Most guides stop at Product markup. This one covers collections, breadcrumbs, and FAQs in native Liquid.
When the DOM changes after load and your event listeners fire too early, here is the pattern that actually works.
Two caching layers sound better than one. They are not unless you configure them to cooperate.
More current writing
Useful pieces that are current, public, and not tucked into the archive.
WordPress 7.0 is a meaningful release for block editing, theme controls, and developer APIs. The practical question is how safely those changes land on real sites.
Astro 6.3 adds advanced routing, safer image handling, and more control over request flow. The useful question is not whether the release is exciting, but what it changes for real content sites.
WooCommerce updates can affect checkout, payments, templates, blocks, emails, tracking, and operations. Treat them like business-critical changes, not routine plugin maintenance.
Performance plugins can help, but they are rarely the whole fix. Start by mapping hosting, caching, theme output, JavaScript, and plugin risk before adding another optimization layer.
Plugin risk is not just about scary vulnerability headlines. It is about knowing what is installed, who maintains it, what it touches, and how quickly the site can be patched safely.
Archive
Still useful, just not the first thing I’d use to introduce the site.
Let's get real about Git – it's great for version control, but it drops the ball when it comes to excluding files on specific branches. But guess what? There's a trick to make it w
You may sometimes have codes that depends on whether some JetPack modules is active or not. If so, there is a quick way to check if the modules are active or not. Just use followin
Whether you are new to African cichlids or have many years of experience, this article contains what may potentially be the most important information you will ever read about thes
Hi everyone, I searched on how to add a dropdown list of bbpress forums and could not find any resource. Most of them were outdated, while some of them didn't work. So I look aroun