2022-09-21 Meeting notes
Date
Sep 21, 2022
Participants
@Dina Meek@Julie Ma (Unlicensed) @Stephen Deems @Greg Dean @Lavanya Podila @Conner Saeli @Joseph White @John-Paul Navarro @Andrew Pasquale
Goals
Discussion topics
Item | Presenter | Notes |
|---|---|---|
| Dina Meek Dina | Button Design - After some discussion regarding the ACCESS IAM working group’s request for a “Login with ACCESS” button as either a JPG or PNG, we’ve decided that providing these raster-based buttons isn't within the best practice for how we design and develop UI for sites. Moving forward, buttons and other UI elements should be included as part of the code. A style guide will be attached to this group’s page. Within this guide you’ll find the appropriate styling that is cohesive with the main ACCESS site which uses the ACCESS yellow, dark grey, and Archivo Narrow font Adhering to this styling within the site allows the ACCESS brand to remain cohesive and operate within the best practices of UI/web design and development. |
Nathan | navigation should always open in the same tab (reiterating decision made 9/6) - ACO site needs to adhere | |
| Julie | Usersnap - Support uses; should all of us? Nathan is concerned Allocations will be getting allocation requests. Andrew says you can get data from the app as well - you get context from it, like what kind of browser they’re using. We can reply to the feedback. Very widely used (Amazon). Group agreed it is a good tool, but want to wait a bit to deploy across all sites. Julie says it’s not free but not expensive - perhaps we could get an ACCESS-wide. |
| JP | Various platforms are being used across sites. WordPress, Drupal. Can projects share through Git some of their website implementations. Each project could put their code on a repository on Github. There’s an ACCESS-wide Github organization. https://github.com/access-ci-org/Operations_Drupal_Theme . Track 3 can also develop web apps which they can also share across sites to embed on their pages. |
| Andrew | SSO - need sooner rather than later. Configuration change for identity needs to happen. Jim Basney’s group manages. Team discussed posting a message across sites once the expectation is set for when we will have SSO enabled. We will hold on this until we hear back from the IAM Working Group (after Sept 30, earliest). |
| Andrew | Analytics - watching how people are using their site. Could put the same tracking code across sites and we can see how the same visitor moves across sites. We can all report the same in our Quarterly Reports. |
| Dina | Privacy statements - not everyone has. Acceptable Use Policy is probably being drafted. We should have one to be used across sites. |
|
|
|