Page Comparison

All/Q

Navigation - top and footer

Personas Landing Pages

What is a reasonable date to get this done? We’d like to roll out early October

Layouts - Updated!

Updated Universal nav doc

With EC for review by EOW

• Dina and Q will review feedback and Q will make updates next week

• We will meet on Weds. IF we need input on the EC’s feedback

Layouts

Production Schedule (Dina to present at Quarterly Meeting September 23)

• By Sept. 6 

  • Nav decided by our group and laid out

  • Landing pages laid out

• By Sept 9

  • Dina send link to dev site with explanations to EC

• By Sept 13

  • EC sends and revisions back to Dina

• By Sept 23

  • Pages ready for Dina to present at quarterly meeting

OLD NOTES FOR REFERENCE:

From 8/21 meeting for ref

• Find Info For (to replace Info For)

From 7/31 meeting for reference:

• EAB loved the work!

• EC did as well and had some suggestions for us to discuss:

  • Top nav: “Info For:” seems a bit off…pointing to the icons. Maybe a carat or something else to indicate a dropdown. And the word “Solutions” rather than “Info” might be better.

    • Also, I said we want the EC’s blessing on the navigation

    • And anything that goes away from the top nav needs to be well represented on landing pages

  • Could we not have that middle landing page (with the persona boxes) and just have that content right on the home page? Two folks mentioned that. Fewer clicks.

  • One mentioned liking the layout (page 3 of 6) with the blurb under the banner and then the persona buttons.

  • Questions about how we’ll vet the content on each landing page

    • I said we wanted to work closely with the EC

    • Also could have the breakout groups from quarterly meeting review too

  • Landing pages: I don’t understand why, on the Getting Started page, you would have the line “If you’re new to ACCESS, read the FAQ.” Why give that option here? They should be selecting one of the five persona options—each of those is essentially a targeted FAQ. Maybe leave the general FAQ link *below* the persona options, e.g. "Do you need ACCESS for another reason? Read the FAQ."

  • The team felt like “Solutions” wasn’t the right word in the “For Info” space; we need to think of something else

    We’re going to use “Programs & Organizations”

    We can just use “Researchers”, “Educators

    Christine suggested we have actual users (one or two per persona) review the layouts to make sure they work for their needs

From 7/18 meeting, for ref:

• Dina walked us through

• Dina to present to the EAB today

From Comms Team meeting: how do we get folks logging directly into a non-ACO site to find their content?” For example, something floating on each page?

• Team felt having it in top nav and footer were adequate

Team wants to include headings for the various questions on each Persona page to help visitors better navigate by topic

Next steps?

• Could we break off into teams of 2, each taking one of the Personas copy pages to check against the quarterly meeting feedback?

From 7/3 meeting, for ref:

Discussed best way to persistently show the Personas (to navigate back to wherever you are on the web presence)

• Decided to use words rather than an icon in the top nav AND to also list in the footer

• For now, nav language will be “Find info for” with a dropdown listing the personas

From 6/26 meeting, for ref:

Andrew: remember SGX3 liked the idea of us using the question format for headers.

Andrew: we want to be sure people can get to these pages from anywhere on the sites

Nathan: we need to remember we decided these pages would be for ALL members of these personas, so “Get Started” may not be as clear or accurate.

We could ask people to identify when they visit our page and then we can feed them content based on their identification
- problematic if they are members of more than one persona

• also they’d have to be logged in for this to happen

We could have a persistent widget for them to identify themselves and/or get back to their persona

• Or use the white space at the top?

Could incorporate accordions on the landing pages as needed to manage growing content

(From 6/20 meeting for ref):

Rather than “Get Started” as the link-through to a subpage with all the personas we could:

• Repurpose the blocks on the home page with “For (persona)” that they’d click through

When we change the top nav, we need to be sure people can get to what may go away (such as Operations and Metrics)

We’ll table HOW they get to the personas pages until we’ve got the pages finalized

Christine to set up a document in Confluence for all of us to add our feedback to by EOD Weds., 9/4. this will include review of the Nav as well.Matt Yoder can share Javascripts to help make this update easier; should integrate with any CMS

https://github.com/access-ci-org/access-ci-ui

access-ci-org/access-ci-ui

User interface components for ACCESS CI

Website

https://www.npmjs.com/package/@access-ci/ui

We need to make some design decisions first - colors, icons, etc.

Oct 10 tentative date; team will look at this week and we can converse via email/Slack to determine if that date will/won’t work

Matt Y and Matt R will meet and discuss in the coming week any issues

Everyone should be reviewing links once we put this in place to be sure nothing is broken for launch

We will not be making any major changes, even if there is feedback suggesting that. Just glaring errors or omissions; reasonable requests

Parking Lot

Tagging/Tracking/GTM/Google Analytics

Megamenus

Integrating CITAP

Allocations new site

Analytics page

Thoughts on deferring this work until after the SGX3 work?

“Get Started” Tagging

• How are people getting to the subpages?

• We need to decide what metrics we’re really interested in tracking

• Looked at tagging the dropdowns on the “about” page of “Getting Started”

• You want to tag things that are actionable by the user

Need to identify goals in order to set metric to measure those goals

• Program-wide goals might be a good place to start

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

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

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

Team agrees we should wait until we consolidate all the web feedback and bring to the EC for direction before deciding how to move forward with tagging for analytics.

Per Dina: still like the idea of organizing our future work around program goals.

Perhaps while SGX3 is doing their work (should be done early May) we can discuss what to tag, but not do any tagging yet.