Keeping 65+ brand websites fast, stable, and secure, and building the applications, automation, and integrations behind them.
A social smoothie recipe platform where members create, share, discover, rate, and review recipes. Built with React and Supabase, including email/Google authentication, protected user dashboards, image uploads, searchable recipes, and PostgreSQL-backed content.
A data intelligence platform combining automated news ingestion, sentiment analysis, and stock market tracking. A scheduled backend pipeline processes external feeds into Supabase, while the React dashboard provides searchable news, sentiment filters, market data, and charts.
A Next.js ad-creation prototype that generates copy through a server-side AI API and lets users upload creatives, configure placements, preview rotation, and generate embeddable ad snippets. Includes protected API-key handling and browser-based ad-library storage.
A full-stack content intelligence proof of concept connecting published Sitecore articles, marketing taxonomy, and GA4 performance. Built with Next.js and Supabase to validate workbooks, normalize URLs, match datasets, surface data-quality issues, and report on content performance without adding CMS maintenance.
For more than ten years, I've kept the websites behind a portfolio of 65+ consumer brands running. I started on the front end and grew into the whole platform: Sitecore on Azure, deployment pipelines, product data, search, SSL, and incidents. More and more of my work is security, and I learned all of it on the job and by training myself.
Learn more about my background →Recurring SSL failures were starving two production servers behind 65 websites. I traced them to an unneeded dependency and rolled out a fix one server at a time, with no downtime.
Read Case Study →Separating harmless firewall alerts from real attacks before blocking was turned on, including the one that looked like a false positive and wasn't.
Read Case Study →A Brand team wanted more insight into its articles. I connected published content, its Marketing taxonomy, and analytics without making the CMS own all of it.
Read Case Study →A PowerShell framework that checks product data from Salsify against what actually renders on the live product page.
Read Case Study →How I traced recurring SSL failures to unnecessary xConnect retries, isolated a configuration issue across two production nodes, and rolled out a targeted fix without platform-wide downtime.
Read →Full-Stack · Data · CMS IntegrationsA Brand team wanted better insight into its article library. The challenge was connecting what was published, how Marketing classified it, and how it performed without creating another CMS maintenance burden.
Read →Automation · Data · IntegrationsThe product existed. The SKU existed. The page existed. Somehow, none of them agreed with each other.
Read →Security · Azure · WAFA web application firewall in prevention mode blocks whatever its rules match, including your own customers. Before we turned blocking on across 65+ brand sites, I had to prove which alerts were noise and which were real attacks.
Read →Engineering · Ownership · Real LifeWhen the people who built a system move on, the system doesn't. Neither do its quirks. Here's what I learned taking over SSL, redirects, a store locator, and a product importer someone spent four years building.
Read →Front End · CSS · Brand SitesNothing was broken. Every page loaded. The site was just a little bit the wrong orange, and on a brand site, that counts as an outage.
Read →Data · Integrations · DebuggingA brand's product filters went sideways after an import. The cause wasn't one bug. It was three, plus a naming collision, plus a mapping that had never worked a single day in its life.
Read →Infrastructure · SSL · IISOne brand site's certificate renewal kept failing. Nothing was wrong with the certificate. The problem was a door I didn't know had to stay open.
Read →The title stayed the same. The scope didn't.
Multi-brand consumer products company · 65+ brand websites
