Page Comparison

...

Attendees

Generating and managing UX tickets
- Waffle?
Nurax vs Hyrax
How soon to spin up usability testing WG
- What to test? Review guidelines for establishing a WG.
Documenting a UX style guide
- Create a dead simple style guide for starters. This will bring up a lot of questions regarding Bootstrap dependencies/versions/future.
- Create a shared repo of small HTML modules (ie. form input element, button, label, modals, radio buttons, multi-select dropdown, etc.)
Ideas on how to get buy-in from our managers for Samvera UX community time.

...

Testing - make sure that we are addressing defaults, instead of what changes are present in Nurax.

Should there be a customization guide that helps with accessibiltiy? Could be as simple as providing links to resources.

Mike Tribone tends to rank tickets in terms of effort.

Hyrax - labels exist for UI issues. Anyone can add these existing labels.

Developer documentation site - some UI information exists, would be good to augment it.

Some insitutions (Stanford) have created gems for their themes.

Permissions group - we need to have a user-oriented perspective on implementation.

UXIG should review Hyrax roadmap with attention to UX issues.

Basic agile principle: teams should be cross-functional. This does not seem to be the case for some of our sprints.

More UX time from managers?

Whoever is running a cycle should make sure UX resources are allocated.

Documented recognition letters are helpful in demonstrating value of this work to managers.

Concept of "UX debt" to burn down, just like we did tech debt.

Lots of UI/UX tickets are written up. Might be good to incorporate these into a dedicated sprint.

We also need to figure out what resources / availability exists.

Over 160 issues in Github are tagged as UI/UX. However, the label has been used inconsistently and needs to be reviewed.

Next call will be in December.