Looking for the current Rivet documentation? View the v1 site.
Version 2 coming 2020

Rivet design system

IU’s physical campuses are thoughtfully built, and its digital campus should be too. Rivet provides the foundations for creating intentional, beautiful, and inclusive experiences. In other words, Rivet helps you support users, solve problems, and tell stories.

See how it works What’s new?

What is Rivet used for?

Version 1 of Rivet was built to help web app development teams (typically within UITS) create consistent and cohesive experiences. Read more about why we built Rivet. Rivet 2 is built for everything digital at IU.

Looking forward

  • Software will remain a core focus of Rivet, but version 2 broadens the scope to include sites, emails, digital signage, and other digital platforms.
  • With the brand at its core, Rivet 2 will offer the basic building blocks of IU’s visual language—the trident, marketing lockups, anniversary marks, and other design patterns that support the stories that IU tells.
  • On top of our brand fundamentals, we’ll build out pattern libraries, layout templates, and a set of guidelines that will help all of IU build usable, accessible sites that are true to IU’s voice, as well as its values.
Photo of Madeline Grdina, User Experience Office Leader, working with a developer in UITS on implementing Rivet in IU Login, a critical touch point on IU’s digital campus

Get involved

For the last two years, Rivet has been a collaborative effort between development teams across UITS and IT at IU. We’ve used their input to create a system that addresses user needs, fits into existing development processes, and gives a flexible foundation for building on the web. For Rivet 2, we need the help of the broader IU community

The RFC process

We want your input to guide Rivet 2’s development. We’ll use a Request for Comment (RFC) process to gather your feedback about design patterns, features, and guides as we’re developing them. We’ll present proposals and ask for feedback from staff, faculty, and students—anyone is welcome to contribute.

Learn more about the RFC process
Upcoming RFCs

We are busy working on a handful of new RFCs for a range of topics including design tokens, updates to the Web Content Management System (WCMS) Framework, and more.

View upcoming RFCs

Open RFCs

  • Design Tokens

    A method of codifying the values (like color and spacing) at the core of IU's visual identity and design system, enabling consistency across platforms and design executions.

  • Web Framework version system

    A simplified versioning and update system for the WCMS-based Web Framework, replacing the current method of manual updates.

  • Web Framework plugin system

    A system for creating and managing plugins for the WCMS-based Web Framework to accommodate custom components and functionality.

  • Rivet 2 header system

    A new header system for brand identity, navigation, and other interface elements that support way-finding and usability in both large and small digital properties.

  • Information architecture strategies for school websites

    Information architecture (IA) strategies for creating simple, familiar, and inclusive user experiences for school websites.

  • (More) Modular Sass

    This RFC proposes a new completely modular approach to Rivet’s Sass (SCSS) code base

  • Container and Grid Simplification

    This RFC proposes a few updates and additions to the Rivet container and grid system

  • Vanilla JavaScript Components

    This RFC proposes a fundamentally new strategy for the way Rivet JavaScript is written