Resources for developers

There are a variety of tools and resources available to developers wanting to adopt the Penn Medicine design system.

For developers, a design system means less guesswork and more efficiency. Components come with built-in accessibility and responsive behavior, so teams can spend less time rebuilding the basics and more time focusing on complex functionality. It also reduces back-and-forth with designers by providing a shared source of truth in code—making handoff smoother and implementation more predictable. Any changes to the Penn Medicine design system can be easily and automatically adopted by anyone who is using the front-end code library.

Penn Medicine design system front-end code library (Storybook)

Our component library is documented in Storybook. It shows how each component looks and behaves across different states and screen sizes. It’s the best place to confirm behavior and usage before implementation.

  • Storybook – You’ll need to have a Penn Medicine ID and be connected to the Penn Medicine VPN to access. Storybook link

Component usage

Each component in Storybook includes:

  • Example code and props
  • Guidelines for accessibility and responsive behavior
  • Notes on variations and states (like error, hover, or disabled)

Use these examples as a reference when building new pages or updating existing ones.

Design <> Dev collaboration

The design system is managed in both Figma and Storybook. Figma shows how components should look; Storybook shows how they behave in code.

If you’re ever unsure how something should be built, check both — and reach out to the design team if it’s still unclear.

Contact & access

Need access or help?