Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

\uD83D\uDDD3 Date

\uD83D\uDC65 Participants

Old Business

  • Style Guide - from the agency

  • Analytics 

    • status update?

    • Dina needs to give Q the emails of all our development teams

  • Universal footer navigation

    • Privacy Policy

    • Conduct (J. Towns working on)

    • Accessibility

  • User Interface

  • Measurements

    • Status update

  • 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

    • Andrew: you could notate a PDF or use XD

    • 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

    • Julie proposes we need to make hard decisions on how things should look and function so as not to confuse users

      • Q will look at this and see what makes the most sense

New Business

  • Subgroup updates

    • Header & Footer - Nathan, Andrew, Greg, Ron/Dina, JP/Dinuka

      • Low hanging fruit was the focus

        • identified things in header/font/spacings/footer and deciding which track had the best look

        • each service area should try to get this done in the next week or so (early Feb)

        • Group agrees we should have a universal footer (the white area) but also some of the same elements in the green bar area

          • And, should we identify that green bar section (with the specific subdomain navigation) with what navigation they are looking at, i.e. “Allocations”

    • Resource Provider Page - JP, Julie, Greg, Nathan, ACO - Ron/Q

      • Next steps:

        • Review with Q

          • 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

          • ACO; bring back to group

          • Vet through RP forum

        • Bring to Q for design

  • 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 GitHub

      • Determine if there should be dropdowns

✅ Action items

⤴ Decisions

  • No labels