...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
\uD83D\uDDD3 Date
...
Owner | Topic | Discussion/Update | Actions |
|---|---|---|---|
All | Personas Landing Pages |
From 7/18 meeting, for ref:
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 wants to include headings for the various questions on each Persona page to help visitors better navigate by topic Next steps?
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)
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
We could have a persistent widget for them to identify themselves and/or get back to their persona
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:
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 | 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 For next meeting: Dina/Comms to review the Wiki Persona documents for voice/style consistency first. Dina to get Jesse access to the wiki Q to prep additional homepage layouts to show placement of news, persona boxes All - review the Updated Universal nav doc for next meeting - make comments about anything you think is missing, needs to be changed, etc. ______________________ Compare the copy in the Personas Landing Pages Content Outline documents (in the left menu <<<) with feedback from the Personas groups in the Quarterly Meeting as follows; make any changes/recommendations to the PLPCO docs by 7/31: Researchers - Nathan Educators - Lissie/Andrew https://docs.google.com/document/d/1Zv7gsPPYM3CgZtMLQE2PozDXGWyPMqgZ6kyuO6NIYO0/edit Grad Students - Greg https://docs.google.com/document/d/1EQGVlwpwql1O9TMt-8Ds2BxoyS0ufr0xQqBNhlygZpM/edit Dina & Comms - Community https://docs.google.com/document/d/1VuQBBguoQL92HHqoJveSXZtjmqPLkBkyGnckGBya-ac/edit |
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
Need to identify goals in order to set metric to measure those goals
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. |