Stanford University & Stanford Medicine

Web Design & Development for Stanford

Since 2001, Wired Moon has partnered with Stanford departments, research labs, and clinical programs to build websites that work. Two decades of institutional experience means we know Stanford’s systems, standards, processes, and we put that knowledge to work on every project.

Stanford University Main Quad, Palo Alto, California

100s

of websites built for Stanford since 2001

Platforms

AEM · WordPress · Drupal · Custom Apps

Which Stanford are you?

Stanford University

Academic departments, research labs, and degree programs. Multi-audience sites built on WordPress, Drupal, and Stanford’s Drupal Sites.

WordPress Drupal Stanford’s Drupal Sites
See our University work ↓

Stanford School of Medicine

Clinical programs, research divisions, and patient-facing sites. Built on AEM and AEM Studio, with WordPress for labs that need more flexibility.

AEM AEM Studio WordPress Custom Apps
See our School of Medicine work ↓

STANFORD UNIVERSITY

Academic departments, research labs, and degree programs. We know how Stanford works.

Whether you’re managing a departmental site, a graduate program, or a research lab, Stanford’s web environment has its own rules: multi-audience navigation, content structures that serve prospective students and current faculty at the same time, and platform choices that range from WordPress to Drupal to Stanford Domains. We’ve been building in that environment since 2001.

PLATFORMS

WordPress: Custom themes and blocks for labs and programs that want full flexibility and independent content management.

Drupal: Scalable, structured builds for departments with complex content hierarchies and faculty profile systems.

Stanford’s Drupal Sites: The university’s templated Drupal system, with customizations that stay within Stanford IT’s guidelines.

WHY DEPARTMENTS CHOOSE US

We understand the multi-audience problem. Your site serves prospective students, current students, faculty, and the public, often on the same page. We’ve designed for that complexity across dozens of Stanford builds.

We know Stanford IT’s standards and approval processes from the inside. No time lost learning how things work here.

We’ve worked across Stanford’s schools and divisions long enough to know which platform decisions serve you well over time.

We train your team to manage the site after launch, so you’re not dependent on a developer for every content update.

Long after the project closes, we’re reachable: for questions, updates, or whatever comes next.

RECENT UNIVERSITY WORK

Working on a Stanford University project?

Tell us what you’re building and we’ll tell you how we’d approach it.

Get in Touch

STANFORD SCHOOL OF MEDICINE

AEM, AEM Studio, and the Medicine ecosystem. We’ve been working in it for years.

Clinical programs, research divisions, and patient-facing sites within Stanford’s academic medical center are built on Adobe Experience Manager. That means working within Stanford Medicine’s design standards, coordinating with TDS, and understanding how AEM and AEM Studio differ and where they overlap. We’ve been in that environment long enough to know it from the inside.

PLATFORMS

Adobe Experience Manager (AEM): Stanford Medicine’s primary platform for clinical and research sites, built on component-based authoring with Stanford’s approved templates.

AEM Studio: A new AEM authoring environment featuring the Almaden template, with more coming. Currently rolling out across School of Medicine divisions.

WordPress: For research labs within School of Medicine that need more flexibility than the standard Medicine framework. We build and maintain those too.

WHY MEDICINE DEPARTMENTS CHOOSE US

We’ve been working with TDS on the AEM Studio rollout. Your team doesn’t have to explain the environment to us, and we can flag what’s changing before it affects your project.

We know the difference between AEM and AEM Studio, between the Almaden template and earlier component sets, and between what TDS controls and what you can customize. Most agencies don’t.

We understand that patient-facing content carries different standards: clarity, accessibility, and trust are non-negotiable.

We’ve merged separate sites, rebuilt complex division structures, and created systems that content teams with no development background can actually use.

Labs outside the AEM requirement aren’t left without options. We build WordPress sites for labs that need flexibility beyond the standard Medicine framework.

RECENT SCHOOL OF MEDICINE WORK

Working on a Stanford Medicine project?

Whether it’s AEM, AEM Studio, or a lab site, tell us what you’re working on.

Get in Touch