Events Feed Similar to how the events feed looks now, we’ll have filtering on the left column, events in the middle, exhibits on the right Talked with communication team about their preferences for filtering, etc. Talked about an ‘audience’ filter, but this felt like it implied an exclusivity Filter by category - Kaitlyn has 20+ in the calendar, but the filter will only show categories that are used on the current/future events.
Removing the “free and open to all” because not all events fall into this “View past events” will be a similar page, but will say “past events”. Question: do we want a page to display past exhibits since we will have these stored in the database? Buttons under each one will display the event type and location. Exhibits are entered manually into a model in rails Question: Can we not use check boxes for the filters?
Landing Pages (FKA Mini homepage) Ambler campus search box - would be the main library search, not pre-faceted to anything Collections on the SCRC page will have an image MAN-50_rev2 SCRC - what did Margery want? - Cynthia go back to notes from meeting with Margery last fall. TODO: Merge landing page tasks into one epic instead of multiple epics
Primary Navigation benefits of a drop-down menu more links off the homepage we don’t have to redirect people to a separate page - instead they can get a preview of the content in a section You can be in an unrelated part of the website, skip the landing page to get to a sub-page NN/Group’s advice: reserve screen space and are an expected website feature
Reservations about drop-down menus will need to have javascript turned on - not based on HTML and CSS there’s a lot that goes into designing them well for the site it’s a convenience feature that doesn’t give you a lot of added value need to be simple if we’re going to use them clunky on mobile devices - has to be modified
Accessibility This is really a conversation about the information architecture and not the design
For next week |