The Brief

RevDoc needed a public site that could explain an AI-enabled healthcare product in plain language, and keep up with two hosts (US and Canada) without the design system falling apart.

  • The Problem: Two country hosts, overlapping content models, and a product story that had to stay clear for patients and clinicians while marketing moved quickly.
  • The Solution: A shared visual system and CMS architecture in Framer (Legal, Teams, Services, Blogs) with templated US and Canada versions owned as one family.
  • The Logic: Treat .ca and .com as the same product with local truth: shared foundations, separate state content, and QA gates so new pages don’t silently break the system.

Digital Medical Passport

Mobile navigation

The Approach

I owned color, type, spacing, and page flows used across both hosts, then modeled CMS collections so marketing could publish without inventing one-off layouts.

US and Canada were built as sister sites: shared components, country-specific pages where regulation and service availability diverge, and a post-launch QA pass for Salesforce forms, short-notice pages, and CMS-generated URLs.

The work also touched decisions that looked “decorative” but weren’t: HIPAA-aware layout choices, advisory content patterns, and keeping patient/clinician language readable under an AI-forward product story.

RevDoc Stack section with vitals and concierge cards
RevDoc UI collage and marketing hero composition
RevDoc product feature module grid
RevDoc navigation and mega-menu wireframe sketches

Key Takeaways

Over ~5 months the public rebuild shipped and supported launch. The lasting lesson wasn’t a prettier homepage. It was defining done.

  • Shared vs. local: A catalog only stays coherent when source-of-truth rules are written down: what is shared, what is country-owned, and what must stay field-blank between hosts.
  • QA is product work: Nav pointing at 404s, Salesforce disconnects, and untested form payloads are UX failures. Lock a gate: no “done” until the real route is wired and tested.
  • Measure both hosts: GA4 engagement and bounce need to be read US vs CA separately: same system, different audiences.

Scope

  • Visual system
  • Information architecture
  • CMS modeling
  • Framer build
  • US/Canada templating
  • Launch QA

Credits

  • Lead Design & Build·Alexandra Le

More projects

Interested in working together?

Shoot me a message!