Web Decision Tracker

Owned by Dina Meek
Last updated: Oct 24, 2024
3 min read

 

Decision

Assigned To

Status

Meeting Date

Decision

Assigned To

Status

Meeting Date

Subsites Navigation

all

Subsites should:

  • Have the NSF/ACCESS logo linking to the access-ci.org home page OR

  • Have the NSF/ACCESS/service team logo linking to the service team’s home page

10/24/24

How to Acknowledge ACCESS

Q

To make this content more visible, a link will be added to the footer

10/24/24

@John-Paul Navarro would interface with the Identity group to ensure their site matches the rest

JP Navarro

done, ldentity group moved their content to operations.access-ci.org/identity/

7/12

Team thought it would be best, for now, to go to a landing page that shows you’ve been logged out upon logout from My ACCESS

All

Team to discuss 7/5/23

6/7/23

Under Login, to save length change to:

  • register

  • questions

Q, all with Login in nav

done

5/10/23

We like the word “Login” as opposed to an icon

Q, all with Login in nav

done

5/10/23

Mobile

  • Change icons to words

  • Leave the hamburger open

Q

in development; done on ACO and Allocations sites;

5/10/23

Team agreed Q could own and manage a GitHub repository as long as they continue to be working on our project.

Q

done

Q to work with JP on setting up a repository

5/10/23

Add two items to My ACCESS dropdown (you have to login to see the “My ACCESS menu)

  • Share with ORCID

  • My Publications

All

Teams updating as of 6/20/23

4/19/23

Team agrees to have headers, footers and secondary navigation aligned with ACO site (according to style guide) by April 30 (Support may be later).

All

Everyone has what they need in Style Guide on GitHub

3/22/23

Team agrees Top nav “ACCESS Home” dropdown will also now include “Events” linking to Support’s Events & Trainings

All

Called Events & Trainings (in GitHub)

3/22/23

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

 

in development (in Style Guide)

 

RP Page - Team decided purpose of the page is to make the RPs more visible; links will give people a path for further action.

 

done

 

Style Guide - Team decided we would all now work to implement the styles and then determine if anything more was needed.

 

done

 

Add “Resource Provider” to top navigation (need to first develop ACO subpage that this will point to)

All

done

in hamburger

 

Team agreed to update copyright line in footer to mention “unless otherwise indicated”

All

 

6/21/23

Group decided About dropdown in universal nav will be in this order: Allocations, Support, Operations, Metrics, Coordination

All

ACO - in backlog

done

 

All service areas will replicate footer as appears in GitHub documentation

All

ACO - Done

Allocations - in process

Support - in process

Operations - in process

Metrics - Done

 

All sites should implement Google Tag Manager code so we can track users across sites.

https://access-ci.atlassian.net/wiki/spaces/~5570585f50afbdfa1e4702ab056e9e6c9ad392/pages/83525641

All

Done

 

  1. Per EC - Reserve use of main ACCESS logo for ACCESS-wide communications; use individual service area/track logos for communications specific to your audiences about your topics

All

Ongoing

 

  1. We will move the original group meeting from Thursday to Wednesday at 3 (CT) and rename, reformat as “Web Presence Working Group” that will be more inclusive of others working on the web presence, beyond branding.

All

Done

 

  1. navigation should always open in the same tab

All

ACO updating some on homepage

 

  1. Add “Coordination” to left side main nav pointing to the Coordination office page (link toAbout ACCESS )

All

ACO - Working on

Allocations - Working on

Support - Done

Operations - Working on

Metrics - Working on

10/12/22 Group decided NOT to do this after all.

 

  1. For enhancements and bugs, we’ll use the ticketing system to collect, triage and status; each track will decide whether to bring it into Jira for their operations. We will set up a queue in the ticketing system.

Ron/ACO

Done

 

Team will develop a features roadmap so we can be on the same page with next phase site(s) upgrades after September 1

All

Working on - post holidays

 

  1. Track 4 is ok with “Metrics” as their navigation name; will confirm in EC 7/19

n/a

 

 

  1. Group approved @Julie Ma's proposed sitemap update which will be shared with EC 7/19

 

Done

 

  1. Group agreed “Track” and track acronyms should not appear on access.org; may be introduced at the various track levels

All

Ongoing

 

  1. Group agreed on dropdown menus for universal navigation; will provide those suggested subnavs in the “input collection page”

All

Moved to Roadmaps process