The work, with the reasoning attached

A casino property needs its site to do two very different jobs: editorial marketing pages that content teams can compose themselves, and an authenticated player portal handling account-level data. Both demand accessibility and both sit on Optimizely CMS 12.

what I built

• Frontend architecture for CMS-driven components — built so editors compose pages without developer involvement
• Player Portal Dashboard Phase 2 — authenticated player-facing UI
• Accessible UI work across the implementation
• Backend and CMS integration points connecting portal UI to platform services

client engagement — implementation specifics generalized

B2B distribution commerce is a different discipline from DTC: enormous catalogs, customer-specific pricing, account hierarchies, and buyers who order by part number. Configured Commerce with the Spire frontend is built for exactly this, and customizing it well requires knowing both halves — the React frontend and the .NET platform underneath.

what I built

• Spire (React/TypeScript) frontend development against Configured Commerce
• Platform configuration and customization on the .NET side
• B2B commerce workflows for distribution catalogs

client engagement — implementation specifics generalized

Industrial suppliers need commerce that handles technical products with deep specification data. This engagement covered both sides of the platform: Spire frontend work and the C#/.NET extension points behind it.

what I built

• Configured Commerce frontend implementation
• Backend platform work — extensions, configuration, and support
• Ongoing implementation support across releases

client engagement — implementation specifics generalized

Not every valuable engagement is a greenfield build. This one was surgical: portal functionality, form work, platform configuration, and precise fixes inside an existing Configured Commerce implementation — the kind of work where reading the platform's behavior correctly matters more than writing lots of code.

what I built

• Portal feature development and configuration
• Custom form functionality
• Targeted platform fixes with minimal blast radius

client engagement — implementation specifics generalized

Beauty supply distribution runs on catalog breadth. The work here centered on how products and categories surface, browse, and merchandise — plus UI enhancements and custom functionality layered onto the platform.

what I built

• Product and category functionality
• UI enhancements across the storefront
• Custom platform functionality

client engagement — implementation specifics generalized

A third commerce platform, same discipline: component-level frontend work inside Salesforce Commerce for a parts catalog measured in the hundreds of thousands of SKUs.

what I built

• Salesforce Commerce frontend component development

client engagement — implementation specifics generalized