
A URL architecture the product suite could grow into
Rebuilt Pendo's product pages on headless WordPress and React, cutting new page launch times from 72 to 24 hours as the suite expanded.
Case studies from nine years owning marketing-site lifecycles. Each one starts the same way: an inherited site, a team blocked behind engineering, and a platform that had to be rebuilt while it stayed live. What follows is the architecture underneath, and what marketing could do afterward.
Not the full work history. That's the Experience section. These are the write-ups for the roles worth walking through in detail.

Rebuilt Pendo's product pages on headless WordPress and React, cutting new page launch times from 72 to 24 hours as the suite expanded.

Modular Marketo templates and clean tracking on go.pendo.io, enabling demand gen to run 40+ user conversion paths without an engineering ticket.

Ran the marketing site like a product with an Asana intake and modular Webflow collection templates, achieving a ~30% developer dependency reduction.

Embedded Marketo forms and brand-matched email templates into the native Webflow site, keeping conversion, tracking, and SEO on one domain.

Sole developer on a K-12 ed-tech marketing site, shipping 40+ reusable React components and new lead-gen sections without losing an indexed page.

Modular HubSpot landing page templates for an emergency-care AI platform — one stayed live for nearly five years after a five-month contract.

A reusable ROI calculator template for AppZen's Marketo-to-HubSpot migration, built once and redeployed months later for a second campaign.
Open to senior web developer and platform lead roles, Bay Area hybrid or remote. I reply within one business day.
Also taking select contract work through Sprintz.
Location
Oakland, CA (Bay Area)
GitHub
github.com/RL22