2019-03-04 UX Intensive Check-in Meeting notes

• May need to create the ability to a service with multiple categories

• We want to avoid having HTML links to specific items in our database - this will open up the opportunity to break links

Benefit of getting items programmatically:

• We can re-use those lists elsewhere

Issue with getting items programatically:

• the order of items in the list may be problematic

• we could make them all alphabetical or date created

• we could build in a priority marker

Idea: When the list goes past a certain number of items, we could have a link that goes to “all borrowing” and that would be a programmatic aggregation instead of a curated aggregation

Secondary page navigational structure

• Contact us is icon based secondary nav

Breadcrumbs

• if we have items that exist in two places or listed in two places

• Alternatively, we could have two links “back to…” and “back to…”

• This could be part of the next user testing session

• We can’t dynamically generate breadcrumbs that follow the path a person took to get to a specific page.

Designing for Mobile and Responsive views

• the aggregation pages will lend themselves to a mobile first view

• For the mobile view, creating a way back to the previous level is more important than having the left hand navigation

Mini-homepages

• With this layout, we should discuss whether we need a separate mini homepage

• Question for Joe on 3/18: What level of identity are we creating for a Location?

• What kind of significance to locations have, either buildings or spaces/

Difference between a service description and a service that’s actionable