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 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 CAS 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
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 roadmapRivet team
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