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

Back to projects
Publicly shareable engineering case study

Heroic Inbox and HeroThemes

Product engineering for a WordPress support platform

Maintaining and improving a mature WordPress support product where email behavior, user experience, backwards compatibility, performance, and dependable releases all affect real customer operations.

Johs role

Software engineer working across plugin, interface, email, release, and support workflows

WordPress product engineering

Context

The product and operating environment

Heroic Inbox is a WordPress support product. The engineering work combines existing plugin architecture, WordPress lifecycle constraints, email and authentication flows, product UI, release coordination, production support, and incremental modernization.

Important constraints

Improving a mature product without disrupting established customer workflows.

Keeping plugin, browser interface, email, authentication, and external-service behavior understandable across boundaries.

Balancing new product work with maintenance, bug fixes, performance, compatibility, and release safety.

Using AI assistance in support and writing workflows without removing human review or control.

Engineering responsibilities

WordPress plugin and product interface development.

Email, authentication, validation, workflow, and support-related implementation.

Performance reviews, debugging, release preparation, and production issue investigation.

AI-assisted reply composition designed around human approval and operational safeguards.

Clear pull requests, documentation, and coordination around changes that affect existing users.

Technical decisions

Prefer incremental improvements over replacing working product architecture without evidence.

Keep AI output assistive and reviewable instead of making autonomous customer-facing decisions.

Treat compatibility, observability, support impact, and release verification as product requirements.

Use focused components and services where they make complex workflows easier to trace.

Practical outcomes

A product engineering approach that supports continued feature work and long-term maintenance.

Safer integration of AI assistance into an existing support workflow.

More explicit attention to performance, release quality, validation, and production behavior.

Reusable experience for modernizing WordPress products without treating them as disposable legacy systems.

Technology and systems

WordPressPHPReactTypeScriptEmail workflowsOAuthREST APIsCI/CD

This case study describes Johs role and publicly shareable technical scope. It does not expose confidential customer data, private credentials, internal commercial information, or imply an endorsement by the named organization.