Skip to content
Indiana University Logo
Rivet Design System
  • Components Add-ons Content guide
  • What is Rivet? Blog Roadmap Changelog
  1. January 20, 2021

    Rivet featured on Accessible Code Libraries and Design Patterns list

    Rivet was highlighted alongside the U.S. government, GOV.UK, and Salesforce design systems.

  2. July 31, 2020

    Returning to development

    An update on plans for creating and releasing Rivet 2

  3. January 17, 2020

    Rivet 1.x.x End of Life Plan

    An overview of how we plan to retire Rivet 1

More posts Get updates in your inbox
Install via NPM Download CSS & JS Hosted assets
Navigation
    • Components
    • Add-ons
    • Content guide
    • What is Rivet?
    • Blog
    • Roadmap
    • Changelog
  • Use Rivet
Resources
  • User Experience Office
  • Accessibility Evaluations
  • Rivet Software Design System
  • IU Framework for WCMS

Rivet

Rivet is a focused set of front end UI components, as well as a place for documenting good UX, accessibility, and design practices. It serves as a developer’s guide for when and how to use certain patterns and how to implement them in an accessible way.

  • Should I use it?
  • Why did we build it?
  • Who supports it?
  • How do we develop it?

Should I use Rivet?

Is Rivet right for your project? Or should you use the IU Framework?

Use Rivet for:

  • Internal-facing web applications consisting of dynamic, user-generated content
  • Enterprise systems used by large parts of the IU community and requiring IU Login authentication
  • Task-focused applications technically separate from your department or organization’s website

Use the IU Framework for:

  • Department and organization websites
  • Websites with mostly static text content
  • External-facing marketing or campaign websites
  • News websites and blogs
  • Contact forms contained in any of the above
Illustration showing five web application screens stacked on top of one another

Why did we build Rivet?

We recognized that the lack of standard design patterns in software development led to disjointed user experiences. A design system contains assets developers can use to create patterns across software titles. It also gathers input from designers and developers university-wide to solve problems and suggest solutions. Rivet’s single source of assets makes it easier to work on and maintain projects.

Who supports Rivet?

IU’s User Experience office is home to Rivet’s support team. They’re working to respond and quickly adapt Rivet as the IT landscape evolves. The Rivet team knows developers need guidance and support, and they’re making sure to meet those needs.

See our roadmap

Rivet team

Levi McGranahan
Levi McGranahan
Design System Lead
Rachel O'Connor
Rachel O'Connor
Front-end Developer
Zachary Todd
Zachary Todd
Front-end Developer
Madeline Grdina
Madeline Grdina
UX Architect
Scott Anthony Murray
Scott Anthony Murray
Developer Advocate
Paco Wong
Paco Wong
UX Engineer
Rivet github project board

What is our development process?

A design system is always evolving, and we welcome collaboration with designers and developers to make Rivet even better. Proposals for content or design changes can be submitted as Github issues, then reviewed based on usability, flexibility, accessibility, visual design, and content.

See our backlog
Have a question about Rivet?

We're happy to help! If you've found a bug, typo, or have a request, the best way to get in touch is to create an issue on Github.

For all other questions please feel free to email us at rivet@iu.edu

  • Accessibility
  • Privacy Notice
  • Copyright © 2019 The Trustees of Indiana University