Frequently Asked Questions

This site covers practical WordPress development with a focus on WooCommerce payment gateway engineering, ClassicPress and classic editor workflows, Elementor build patterns, plugin reviews, webhook and callback handling, and developer workflow notes. The content comes from direct project experience and is aimed at developers who work with these tools regularly. The main hub pages for each topic area are linked from the Resources page.

All content is written from direct experience working with WordPress, WooCommerce, and related tools. The perspective is that of someone with extensive hands on experience in payment gateway development, plugin implementation, and WordPress project delivery. More detail is on the About Me page.

New content is published when something is worth writing about, not on a fixed calendar. This might mean several updates in one month and then a quieter period. Existing content also gets revised when the underlying tools change, when reader feedback surfaces gaps, or when further project experience adds useful detail. The changelog tracks major updates.

Yes. Code examples and snippets are provided for educational use and you are welcome to use, modify, and incorporate them into your own work. They are provided as is, without warranty. Always test code in a development environment before deploying to production. Code examples illustrate specific concepts and may need adaptation for your WordPress version, PHP version, and plugin stack.

Send an email to the address on the contact page with the URL of the affected page, a description of the error, and what you expected versus what you observed. Include relevant code or configuration details if applicable. Corrections are genuinely appreciated and help make the content more useful for everyone.

The tutorials are written from experience integrating with various payment providers, particularly those serving East African and developing markets where the standard PayPal and Stripe options are insufficient. The patterns described are general enough to apply to most provider APIs, but specific provider quirks vary. The sandbox testing guide covers how to validate behavior against your specific provider.

No. Plugin reviews on this site are independent assessments based on direct testing. No plugin developer has paid for a review, placement, or favorable treatment. If a tool works well, the review says so. If it has problems, the review says that too. The review methodology is described on the plugin reviews page.

Yes. Send suggestions to the address on the contact page. I keep a running list and prioritize based on reader interest and relevance to the topics this site covers. Not every suggestion will result in a published review, but all suggestions are considered.

omukiguy.com is built as a static site and served through Cloudflare's edge network. There is no server side rendering, no heavy client side JavaScript framework, and no database queries on page load. Pages are pre built HTML served from the nearest Cloudflare data center to your location. Search is handled by a lightweight local index rather than a third party service.

This site does not set first party tracking cookies. No advertising pixels, marketing scripts, or cross site tracking tools are used. Cloudflare may set functional cookies for security purposes. The full details are in the privacy policy. For questions about search indexing and technical site practices, see Google Search Central for background on how helpful content indexing works.

The preferred method is email. The contact address is on the contact page. Include a clear subject line and, if your question is about a specific page, include the URL. Response time is typically 2 to 5 working days for substantive questions.

No. This site does not accept paid guest posts, sponsored content, link exchange proposals, or partnership pitches. Content is produced independently and the editorial focus is not influenced by external placement requests.