2022-12-21 Meeting notes

 Date

Dec 21, 2022

 Participants

  • @Dina Meek @Conner Saeli @Andrew Pasquale @John-Paul Navarro @Julie Ma @christine Golus, Matt Restorff, Emily Cedar, @Ron Payne @Lavanya Podila @John-Paul Navarro @Gerald Byrket

 Goals

  • Review the RFP with Q, Ltd. to ensure they (contract web developers) understand what the web teams need to better align the user experience

Old Business

SSO - CiLogon; reference implementation - Joe

Item

Presenter

Notes

Item

Presenter

Notes

Trainings, Events News

Dina

RPs are wanting a space on one of the access-ci sites to post news of trainings.

CiLogon

Greg

removed step that required you to select your IDP each time you logged in.

Next step: Joe was working up some reference code to integrate into each track site to allow for seamless login experience.

Update: Joe is still working on it

theme design

Andrew

Any upcoming, expected overall style changes

Resource providers

JP/Tom

We received feedback that resource providers are not as prominently listed in our websites as they should be. What resource provider and integrated resource information can we make more prominent? Share what T2 and T3 are doing, and what else we should do.

Ideas: About Resources (under that dropdown); include in main nav; add to questions blocks on main aco site; each site have context-appropriate content about RPs; possibly create a subpage under ACO site for landing; direct via links to specific info on allocations, support, metrics, etc.

For now - update the question box and point here: https://allocations.access-ci.org/resources

Contact Form

 

Add blurb to the Contact Form intro guiding people to the ticketing system if they are users and need support

 New Business

Notes on RFP:

  • Christine said most of what’s in the list of requirements is very standard; some are already being used at least on the ACO site and/or is in the initial style guide

  • Julie said the detail in the guide should actually be as detailed - rather than high-level - as possible

  • Developers said they are looking more for how to design/use various elements of the pages rather than what a full page might look like

    • JP: We do want to ensure the top banner and footer are identical, but that the middle sections can be different WHILE adhering to uniform styles

    • They don’t need code, per se, but they need a guide to style

  • My ACCESS is ready on the back end so we should be able to put that into the guide

    • Need to determine the selections/what’s in the drop-down list

    • Andrew says there is a list

    • Julie says they don’t need code for this, just what it would look like

  • Discussed News dropdown

    • ACO is OK with there being a universal dropdown that includes:

      • News

        • discussion on how to organize news to pull in from various sites, but also to be vetted for what shows up on the main site

        • The development team needs to decide how to manage the news that’s on the ACO site and also what’s on the Support news site

          • Discussed Support’s site being called “Announcements

      • Events - will be hosted on the Support site, but a dropdown could go there

  • Discussed Login

    • What would it look like and what are the dropdown items

      • Andrew says you’d have a universal login and from there it could be:

        • My ACCESS - your profile and account info

        • ACCESSonDemand - you can get to

  • Resource Providers

    • Perhaps “Resources” in the top nav

      • Team needs to decide where it will go

    • Clarified that we could link from the universal nav to a subpage on the ACO site - much like the current “About” page - that give some general information and then provides links to over sites based on what the visitor is looking for

      • Allocations

      • user documentation

      • becoming a resource

      • metrics about resources

    • Could we share a high-fidelity mock-up with Ruth/RP Forum to show the what the subpage would look like

    • We could also include - via feed - the RP list from either Allocations or Operations page

 Action items

 

 

 Decisions