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

    Rivet 1.8.0 release

    Rivet 1.8.0 is now available. This release adds border removal utility classes and fixes bugs related to the button, dropdown, and collapsible components.

  2. February 15, 2021

    Rivet announcements: Beta timeline, GitHub Discussions, and 1.8.0 release

    Updates about Rivet's development in the spring and beyond.

  3. 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.

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
Go back to the Blog

Rivet quarter in review — Q1 2019

A summary of the Rivet team's progress toward our goals for the first quarter of 2019.

In this article

    • Goal: Hire a new front-end developer
    • Goal: Establish a team project management process
    • Goal: Increase backlog visibility and engagement
    • Goal: Establish and document a QA process

Levi McGranahan, design system lead, hosted a call last week in which he summarized the progress the Rivet team has made toward the goals we laid out for Q1 2019 in the roadmap.

This blog post recaps the key takeaways from Levi’s Q1 progress report.

Audio on
Watch or listen to the quarterly review
Kaltura video
Grid
View the quarterly review slide deck
Google Slides presentation

Goal: Hire a new front-end developer

Status: Done

Rachel O’Connor, formerly of the User Experience Office engineering team, has transitioned into the role of front-end developer for Rivet.

Rachel is still getting up to speed, but since joining the team she has closed a significant number of bugs and maintenance issues. Next quarter, she hopes to shift her focus to the feature requests in the backlog.

Goal: Establish a team project management process

Status: Done

Last year, developers made it clear that Rivet needed a consistent release schedule that they could plan their own workflows around. We resolved to implement a monthly release process, and we’re happy to say that we’ve done so — the end of March saw our third monthly release of 2019.

In addition, we’ve created a comprehensive new wiki that lays out our development, release, and issue tracking processes.

Goal: Increase backlog visibility and engagement

Status: Done

The new project management processes and contribution guidelines we put into place all center around the Rivet public backlog.

A new part of our process this year is soliciting upvotes from the community on feature requests in the backlog. We were encouraged to see more engagement with the backlog than we were expecting when we put out the first call for upvotes, and we hope engagement continues to increase as people become accustomed to this part of the process.

Goal: Establish and document a QA process

Status: Ongoing

On the back of Rivet’s migration to GitHub.com and Rachel’s hiring, we’ve been exploring ways we can leverage continuous integration (CI) tools to run automated tests on any code pushed to Rivet repos.

We’re currently testing a repeatable CI process with Rivet add-on repos like Rivet collapsible.

We’re also continuing to work on documentation on how we carry out manual testing of new or updated components. This documentation will be added to the Rivet wiki when completed.

Previous: Rivet 1.4.0 release Next: Rivet Community Workshop slides — Spring 2019
Scott Anthony Murray
April 1, 2019

About Rivet

Rivet is a university-wide initiative, overseen by the Digital Campus Studio.

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 © The Trustees of Indiana University