WowShipping Frontend Engineering

Quick answer

Mahmudun Nabi Kajal is a frontend developer at WPXPO who has authored 900 commits to WowShipping, a WooCommerce table-rate shipping plugin, since July 2025. WowShipping's Git history has four contributors - Kajal, Samin Yaser, coderskamrul, and Anik Biswas - so these commits are one part of a shared codebase, not solo work. Each case study isolates one frontend decision from that history, verified against the actual diff rather than the commit message. They're scoped to commits Kajal authored, and where a later commit by someone else changed or removed what he built, that's stated directly. Start with the Select component trade-off or the drag-and-drop case study if you want to jump in directly.

The initiative

WowShipping is a WooCommerce plugin for table-rate shipping with live carrier rates from UPS, USPS, and DHL, built by WPXPO. Its admin interface is a React app inside the WordPress admin, built around a shared UI component library and a set of shipping-method configuration pages. That codebase has three other frontend contributors alongside Kajal. These case studies isolate only his own commits. They aren't a single initiative - four separate decisions, spaced across about four months of the same codebase, readable in any order. Together they show a plugin's frontend maturing on more than one axis at once: adopting a platform primitive and partially walking it back, solving an interaction problem by hand, imposing a naming standard across the component library, and renaming a domain concept without breaking a deprecated path.

The case studies

The Select Component Trade-off →

The anchor piece. In December 2025, I migrated a shared select component to wrap Gutenberg's native SelectControl behind a preserved prop API. Tracing the history later, I found the migration never became the codebase's lasting implementation - a branch that had forked just before it merged took over that file's history within days, with no single commit that reverted it.

Native Drag-and-Drop Without a Library →

The craft piece. I built shipping-method reordering directly on the HTML5 Drag and Drop API rather than pulling in a drag-and-drop library, including a counter-based fix for the dragenter/dragleave flicker bug and a manually constructed drag-ghost element.

A Naming Convention Overhaul, One Week →

The standard piece. Across five commits in one calendar week, I renamed the entire component library, page folders, and context files from PascalCase to kebab-case.

Renaming a Domain Concept Mid-Flight →

The vocabulary piece. In December 2025, I renamed "shipping rules" to "shipping methods" across 45 files - a month after I'd already isolated the legacy implementation into a folder marked deprecated rather than deleting it outright.

FAQ

What is WowShipping? WowShipping is a WooCommerce table-rate shipping plugin by WPXPO, offering live carrier rates from UPS, USPS, and DHL alongside weight-, cart-, and location-based rate rules. Who did this work? I'm a frontend developer at WPXPO and authored 900 of the repository's commits between July 2025 and August 2026. The codebase has three other frontend contributors, and each case study here is scoped to my own commits. Why are these four stories grouped together? They aren't one initiative - four separate frontend decisions from the same codebase, spanning a platform-adoption trade-off, a hand-built interaction, a naming standard, and a vocabulary rename. Together they show a wider range of judgment calls than any one alone would. Did any of this work get reverted or removed later? Yes, and the affected case study says so. The Select component migration didn't survive a branch merge - a parallel branch that forked before the merge became the surviving history for that file within days, with no single commit reverting it. Is this work solo or team-authored? Team-authored. WowShipping's Git history has four contributors - Samin Yaser (935 commits), me (900), coderskamrul (71), and Anik Biswas (1) at the time this series was written. These case studies document my individual commits within that shared codebase, not a solo project.

WowShipping Frontend Engineering - 4 Case Studies