Privacy-respecting analytics

Joh uses Google Analytics to understand which stories and portfolio pages are useful. Advertising storage stays off. Read the privacy notice.

Joh Azores

WordPress product engineering

Build and modernize WordPress products people can support confidently.

I work on WordPress plugins, support products, membership systems, modern admin interfaces, APIs, migrations, integrations, release workflows, and production issues with a focus on long-term maintainability.

Review selected work

Best fit

Built for products with real constraints.

A plugin or WordPress product has accumulated legacy behavior and repeated support issues.

The admin interface needs a modern product experience without abandoning WordPress compatibility.

External APIs, email, membership, ecommerce, or account integrations need clearer boundaries.

A team needs hands-on engineering support for releases, maintenance, and product improvements.

Problems addressed

Large procedural files, duplicated hooks, unclear ownership, and difficult debugging paths.

Admin screens that feel like generic settings pages instead of focused product workflows.

Fragile migrations, background jobs, remote requests, webhooks, or scheduled operations.

Performance problems caused by unnecessary queries, assets, hooks, or work on every request.

Release and support processes that rely on tribal knowledge instead of repeatable checks.

Expected outcomes

Clear plugin boundaries with smaller services, reusable UI, and understandable data flow.

Modern and accessible admin experiences aligned with the actual user workflow.

More reliable integrations, migrations, validation, logging, and failure handling.

Focused performance improvements without breaking existing customer behavior.

Practical release, testing, support, and maintenance documentation.

Working process

Clear decisions before unnecessary implementation.

1

Review the plugin architecture, WordPress lifecycle usage, data model, UI, and production history.

2

Map compatibility requirements and identify changes that can be made without risky rewrites.

3

Implement the highest-value fixes and improvements in focused commits and release-safe stages.

4

Validate upgrade paths, permissions, escaping, sanitization, integrations, and important workflows.

5

Document maintenance boundaries, release checks, known constraints, and next product priorities.