\uD83D\uDDD3 Date
\uD83D\uDC65 Participants
...
Greg Dean John-Paul Navarro Tolbert, Nathan L Andrew Pasquale Matt Yoder Rebecca Eveland Conner Saeli Qltd (Christine , Emily, & Matt)
Style Guide - https://client.qltd.com/access/index.html
Feedback from teams due today 3/8 in the XD files
Reviewhttps://xd.adobe.com/view/85d0f4dc-241a-4f2c-b5e1-e83136c7421e-d083/
Allocations provided feedback to the group
Support has added feedback via the XD document
No additional feedback from operations
No noted feedback from Metrics team
Can we set a date or milestone to say the Style Guide is done?
With the exception of confirmation from Operations, all feedback has been provided.
Tom Gulbransen asked if we were tracking when all the sites would be up-to-date in terms of style. Do we want to track and report that?
The next iteration is available here –
Measurements
Team will review and bring feedback to the 3/1 meeting
Allocations is still working through it
Operations is implementing
JP - has struggled with a single place to go that references all the decisions we’ve made
Dina and Ron to meet to determine best way to organize decisions/actions for group to follow
Dinuka - is the style guide ready enough for their designer
Support is still working through it
They would like XD files
has some additional questions, once he gets those
At some point we declare we’re done; what date do we want to release
Dina mentioned we do have a target date - March 17 - for the RP page and we should all shoot for that as our “end date”
Andrew suggested XD as a way to gather feedback
Final feedback to Q on Style Guide 3/8
https://xd.adobe.com/view/85d0f4dc-241a-4f2c-b5e1-e83136c7421e-d083/
Christine will share links to Style Guide and the UI
Hopefully on the group Google Drive
Analytics
Once the new dashboard is set up we will make sure that all the folks have access:
Allocations: Rob Light/Nathan Silver
Support: Andrew Pasquale
Operations: JP
Metrics/xmod: Ryan Rathsam
access-ci.org: Dina and Ron (and at the moment Q LTD team)
Universal footer navigation
Privacy Policy
Conduct (J. Towns working on)
Acceptable Use (created by the IAM group)
Dina to bring Support's Privacy, Code of Conduct to ACO to determine if we can use this, make adjustments etc.
Then bring back to the group to make sure we all have the same verbiage/links in our footers
Resource Provider Page - JP, Julie, Greg, Nathan, ACO - Ron/Q
There will be a subgroup to put together a decision tree to help new researchers decide which resources they need
Support
Allocations
Operations
Ruth and Tom Maiden - sources of truth for RP logos/page
Dina to get RP copy into the drive and share link with the team asap
Team to review RP copy by 3/8
Q did a very high-level layout based on JP’s team’s outline
We need to run by a small focus group of RPs before we do much more
We need to determine what makes the most sense to show on the page - the Resource Provider names or the actual resources (Bridges) page
We may need to link off to a subdomain that has a list (dynamic pulling from dbase) of all the resources
Draft copy
Group discussed purpose of page
we all agree that this is to make the RPs more visible
The questions at the bottom are how people take action
The various service areas need to help us determine what the questions are and what the links are
The Resource Types will be done away with and that info will be brought up into both the intro (explaining the different types of resource) and then fleshing that out a bit under the blurb that will come under whatever the “levels” titles becomes
Ron has info on how “Levels” are now described within ACCESS
Vet through RP forum
NEXT STEPS: ACO will share updated draft copy based on above with this group for feedback before giving to Q to re-lay out
Once team is satisfied with copy and layout, Dina and Ron will bring to the RP Forum small focus group
For future:
User Interface
Refinements focusing especially on:
Universal navigation dropdown (Login or My ACCESS TBD for future)
Do we want dropdowns
open on hover? open on click?
what do underlines mean? Active?
Q says its most simple to use “Login” on all the sites in the Univ nav bar
All sites aren’t handling login the same;
where we need all sites to go is to CiLogon
We will defer this piece - for the ACO site - until we’ve got style guide finished
Subdomain navigation and drop downs
Subdomain footer refinements
Breadcrumbs
“Home” means different things
So replace that in breadcrumbs with subdomain name
“Home/Tools” would change, for ex, to “Support/Tools”
Would like to add a style - like the inpage navigation (see “Tools” in Q’s layout) - for inpage content boxes
And…
Adding blurb to Contact page with link to ticketing system for allocated users
Dina shared text with Q 2/8
Universal navigation, dropdown menu for “About”, includes file distribution to all
subdomains via GitHubDetermine if there should be dropdowns
Collaboration page
News
Add Events and Outages linking to specific sections of Support’s site
Assuming the Style Guide is finalized this week, the Service Teams agreed to come to the next meeting (22-March) with a target implementation date.
RP Page - https://drive.google.com/drive/folders/1jy00OGHyFF0nF09Dk_Q1YVj8ktjJlXkW
Please review in Suggesting Mode by 3/15
Can we get the link-offs on the bottom of the page determined by then?
Does decision tree subgroup need to have that work done before we can determine language and links?
Next steps
Layout by Q
Dina shares mockup with:
Ruth and/or Tom Maiden to vet logos/systems, then
small group of RPs for feedback
Analytics
Q developing dashboard
Universal footer navigation - all sites should point to:
Privacy Policy (created by the IAM group)
Acceptable Use (created by the IAM group)
Code of Conduct (created by ACO and vetted through EC)
Universal header navigation
Updates?
✅ Action items
Assuming the Style Guide is finalized this week, the Service Teams agreed to come to the next meeting (22-March) with a target implementation date.