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

Hotspotting

Modernizing a membership and property-insights platform

Engineering a maintainable membership experience across a public website, authenticated portal, subscriptions, ecommerce, integrations, and white-label requirements while preserving existing business systems.

Johs role

Software engineer responsible for website, members portal, ecommerce, and platform improvements

Context

The product and operating environment

Hotspotting operates a property-insights membership platform. The technical work spans a Next.js portal, WordPress and ecommerce systems, account and subscription behavior, third-party integrations, enterprise presentation requirements, and ongoing production support.

Important constraints

Improving the member experience while existing WordPress and ecommerce systems continue operating.

Keeping subscription, account, content-access, and integration behavior consistent across platforms.

Supporting enterprise white-label requirements without maintaining separate application forks.

Balancing immediate product requests with a simpler long-term platform structure.

Engineering responsibilities

Next.js membership portal architecture and product implementation.

WordPress, ecommerce, subscription, account, and content-access integration work.

Responsive dashboard, navigation, settings, and member workflow improvements.

White-label controls for company identity, colors, logos, navigation, and selected content visibility.

Production troubleshooting, technical planning, documentation, and ongoing platform maintenance.

Technical decisions

Preserve working ecommerce and subscription systems while introducing a modern portal boundary.

Use one maintainable application with controlled branding and feature visibility instead of client-specific forks.

Keep white-label configuration focused on real customer needs before expanding into a broad theming engine.

Treat responsive member workflows and operational maintainability as core product requirements.

Practical outcomes

A clearer path for modernizing the member experience without replacing every existing business system.

A reusable white-label model based on configuration rather than duplicated applications.

Improved alignment between public website, portal, subscriptions, ecommerce, and enterprise requirements.

A practical example of platform modernization through boundaries and staged migration rather than a rewrite.

Technology and systems

Next.jsReactTypeScriptWordPressWooCommercePrismaMongoDBStripeREST APIs

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.