2024-01-10 Meeting notes

Dina

Dina

Dina

All

All

All

Andrew

NSF Brand Changes

Charter

Allocations new site

Tagging/Tracking/GTM/Google Analytics

Integrating CITAP

SC23 Support Feedback Forums

Recommender / Discovery Systems

Will affect headers and footer

With Shawn for review before he, as our sponsor, brings to the EC

Propose we spend our next meeting reviewing how this impacts the home page’s “Get Started” work

Please add to this list asynchronously and we will check it as we continue to meet

We anticipate a usability study to be done across our sites in Q124

What can we do that might make sense while that’s going on?

Glossary

• Just ACCESS specific

• Dina to add to our Confluence space

• First iteration can be done by

  • terms added

  • group reviewed

  • add to the footer when the whole footer is ready to be updated (disclaimer, logo lockups)

  • We can update quarterly, reviewing together

It would be helpful to have a page describing the recommender systems, the differences between them, and who they are most likely to be helpful for.

• resource advisor is one for newer users

• allocations one (filter)

• Operations has a chatbot

• Metrics is also developing a tool

• various tools like this in development

• Software discovery tool (all RPs will have to install it)

Sitemap

• Andrew/Support will set up a child page on our Confluence space and will guide us through adding to it before we publish

  • Use a webscraper to generate the page URLs

  • Then we can discuss design

  • How do we update and on what cadence

    • Andrew suggests a quarterly update with everyone maintaining their own sections

Megamenus

• Support will build for their secondary menu and we can follow that if we see a good reason for adding it to main nav

ACO and Q working together to update header and footer; all sites will have to update too; we’ll put logos, etc. in Github

• Dina to check on spelling “OAC” out and including “U.S” with NSF

Questions from last mtg:

• where does this make the most sense?

• how do we make this work across the board?

• https://webflow.com/blog/mega-menu-examples

• Glossary might be good for use across the sites; one primary glossary

• How do we make it easier to find the Trainings? People not finding in the hamburger in user testing

• What about a sitemap?

Nathan said we could possibly do something with APIs to automatically update, but work

Could glossary go in the footer when we update the footers

Nathan said we could possibly do something with APIs to automatically update, but work

Per Lissie, at this point they all have their own use cases; in the future how can we help the user know which one to use when

• Dina to suggest to ACO organizing next quarterly meeting that we have a breakout session to discuss best uses and how to organize info to help user understand what to use (need buyin from leadership)

• short-term solution would be for us (this team) to come up with guidance for the user