If you have a similar business problem
Read the plain-English summary, real situation, and result first. Those sections explain what the work changed without requiring you to know the code or platform details.
Selected Work / Case Studies
These are production scenarios and product work, not a gallery of screenshots. Named live work is shown where it can be public, while other client details stay private. Alongside client case studies, in-house products such as ConduitTools show how focused ideas are designed, built, and maintained over time.
54case studies
Featured production work · WAMA Underwear
Wayne Pastoral works on the live storefront across customer-facing features, conversion experiments, performance, accessibility, technical SEO, integrations, and the production work that keeps the store moving.
Ongoing e-commerce engineering · live production storefront

Design, conversion, search, performance, and store operations working as one system.

Documented search presence
Live-store context: WAMA currently reports 130,000+ pairs sold and a 4.7/5 customer rating. Those are WAMA-reported brand facts, not outcomes attributed solely to engineering.


Search example: “best hemp underwear.” Rankings and AI-generated results can vary by location and change over time.

Built by ConduitCode Labs
ConduitTools is a practical collection for image, PDF, time, QR, text, developer, and everyday utility tasks. Open a tool, get the job done, and move on.
Find the tools useful?
merged-document.pdf 6 pages
How to use this portfolio
You do not need to understand every technology mentioned in a case study. Start with the problem and result, then go deeper into the implementation only if it is relevant to your own site or product.
Read the plain-English summary, real situation, and result first. Those sections explain what the work changed without requiring you to know the code or platform details.
Read the constraint and implementation sections. They explain why the obvious fix was not enough and what tradeoffs shaped the final solution.
Use the release-check section as a practical QA reference. It shows what needed verification before a change was safe to ship to real users.
Jump to the reusable lesson. It condenses the case into a principle that can help with future websites, stores, applications, or integrations.
Showing 1 to 9 of 54 · Page 1 of 6
E-commerce
A non-Plus Shopify store needed quantity-tier pricing that the theme could explain to the customer but could not authoritatively apply inside the protected checkout steps. A custom app hosted on Fly.io validated the cart, created a discounted Draft Order, and handed the customer back to Shopify's secure checkout.
Read case studyE-commerce
A long-form brand page had outgrown its page-builder implementation. The content was rebuilt as a native Shopify theme template with reusable sections, consistent spacing, accessible links, responsive tables, and mobile layouts that no longer depended on a third-party page builder.
Read case studyCommerce applications
A targeted internal alerting path reports detected checkout-preparation failures while leaving the shopper's normal checkout flow independent of notification delivery.
Read case studyCustom applications & automation
A private campaign builder lets a marketing team create, preview, and reuse countdown timers in email without manually building each animated graphic.
Read case studyIndependent software product
How an independent utility platform balances reusable architecture with the different needs of image, PDF, time, and developer tools.
Read case studyCustomer authentication
Google and Facebook sign-in were configured and tested with authorized accounts. Provider publication and public-access verification remained separate release steps.
Read case studyAnalytics & CRM integrations
Extended a WordPress-to-CRM lead pipeline to carry GA4 client and session identifiers, while keeping identifier availability and downstream QA explicit.
Read case studyWordPress security
Patching answered one question. This review asked the harder one: who already had access? User accounts, file-editing plugins and logs, documented with care.
Read case studyCommerce applications
An optional birthday field needed to live inside Shopify-hosted customer accounts, beyond the reach of theme code. A custom account extension provided date validation, confirmation before saving, a read-only saved state, and staff corrections through Shopify Admin.
Read case study