Contact

If you have a question about something published on this site, found an error in a tutorial, want to suggest a topic, or just want to say hello, this page is where to start. I read every message that comes in. Response times vary depending on workload, but I aim to reply to substantive questions within a few working days.

What I Can Help With

Questions about the tutorials and guides published on this site are the easiest to answer because the context is already shared. If you are working through the WooCommerce payment gateway tutorial and something is not behaving as described, or if a code example in one of the webhook handling notes needs clarification, those are the kinds of messages that get the most useful replies.

Plugin review requests are welcome. If you are evaluating a WordPress plugin for a project and want to know whether I have tested it, or if you want to suggest a plugin for a future review, let me know. I cannot promise that every suggested tool will get reviewed, but I keep a running list and prioritize based on how many people ask about the same tool and how relevant it is to the topics this site covers.

Corrections and improvements to published content are genuinely appreciated. If a code example has a bug, if an explanation is unclear, or if a guide is missing a step that tripped you up, I want to know. Good technical content gets better when readers who actually use it point out what needs fixing.

What I Cannot Help With

I do not provide free consulting for production projects. If you need someone to build a custom WooCommerce payment gateway for your specific provider, debug your existing checkout flow, or migrate your site to ClassicPress, those are consulting engagements and they have a different scope than answering questions about published content.

I do not accept paid guest posts, sponsored content, link exchange proposals, or SEO partnership pitches. If your message starts with a proposal to add a link to your site or to publish a guest article, it will not receive a reply. Nothing personal. These messages arrive in volume and none of them result in content that would be useful to readers.

How to Reach Me

The preferred contact method is email. Send your message to the address below with a clear subject line that describes your question or topic. Include the URL of the relevant page if your question is about something specific on this site. For code questions, include the relevant code snippet and a description of the behavior you are seeing versus what you expected.

Response Time

I aim to respond to questions about published content within 2 to 5 working days. Complex technical questions may take longer if they require testing or research to answer properly. Plugin review suggestions are acknowledged but reviews are published on their own timeline based on testing availability.

If you reached out and did not hear back within a reasonable time, feel free to send a follow up. Messages occasionally get buried during busy project periods and a polite nudge is always welcome.

Other Pages That Might Help

Before writing in, check whether your question is already addressed:

• Frequently Asked Questions covers common questions about the site and its content.
• Resources has the full index of tutorials and guides.
• Search lets you find content by keyword.
• About explains what this site covers and how content is produced.