Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[CAIA Internal]: EDM team WEAMS migration Content changes #99433

Open
1 of 21 tasks
scjwalker opened this issue Dec 18, 2024 · 0 comments
Open
1 of 21 tasks

[CAIA Internal]: EDM team WEAMS migration Content changes #99433

scjwalker opened this issue Dec 18, 2024 · 0 comments
Assignees

Comments

@scjwalker
Copy link
Contributor

scjwalker commented Dec 18, 2024

CAIA Internal Collaboration

CAIA Intake
IA Spec
IA Tracker ticket

Issue Description

What details are necessary for understanding the specific work or request tracked by this issue?

The EDM team is info about reimbursement rates for national tests and for licenses and certifications into the School Comparison tool. The different types of data being added to the Comparison tool need different search and display controls, so as part of this project they're collaborating with the GovCIO team to convert the current School Comparison tool URL into a landing page, where users can choose which type of data they want to look at. There will be three categories - Licenses and certifications data which will be a search+results format, National tests which will be a list, and the current School comparison search+results which will now have the Yellow ribbon data integrated into it. (For more on the Yellow Ribbon changes, see the Yellow ribbon tool content changes ticket and IA Spec.)
weams 5

We are working on controlling scope on this project. The team has received this, along with a framework to guide their content/IA decisions inside the tool: "On this project, CAIA IA support will be focused on the connections between the Comparison Tool and the rest of va.gov. We are not able to support IA and Content decisions within the tool Landing page or sub-pages."

Entry points

Primary entry point for launch

1) Education benefit hub page - Modify

  • Placement description: Keep the entry point's current placement on the Education hub page. Update the descriptive text to reflect the additional content added into the Comparison Tool.
  • Link label: [TBD by CAIA Content]
  • Link destination: va.gov/education/gi-bill-comparison-tool
  • Who will update (IA, content, product team): CAIA Content
  • When will this entry point go live (at launch? After staged rollout? after some designated time?): At launch
    weams 2

Secondary entry points

Any additional locations that the page should be navigable from such as the "About a form" page, additional navigation component (top, left) placements, additional static pages where its prominently linked from, etc. These are secondary, and while they are still very important, are not required for launch.

1. Mega menu - Modifications TBD -

  • Placement description: Mega Menu promo spot
  • Link label: Keep current header text and descriptive text, or update to reflect additional data available in the tool. (Changes TBD by CAIA Content)
  • Link destination: va.gov/education/gi-bill-comparison-tool (now the url of the new Landing page)
  • Who will update (IA, content, product team): Education business line. Beth will coordinate.
  • When will this entry point go live (at launch? After staged rollout? after some designated time?): At launch
  • Notes: Editing a single location updates the promo spot in both the Mega menu and Right rail.
    weams 6

2. Right rail of Education hub page - Modifications TBD -

  • Placement description: Right rail promo spot
  • Link label: Keep current header text and descriptive text, or update to reflect additional data available in the tool. (Changes TBD by CAIA Content). The content here must be consistent with the content in the Mega Menu promo spot.
  • Link destination: va.gov/education/gi-bill-comparison-tool (now the url of the new Landing page)
  • Who will update (IA, content, product team): Education business line. Beth will coordinate.
  • When will this entry point go live (at launch? After staged rollout? after some designated time?): At launch
  • Notes: Editing a single location updates the promo spot in both the Mega menu and Right rail.
    weams 7

Crosslinks

  1. Identify all existing crosslinks to the Comparison Tool and modify the links to direct visitors to the Landing page or the School Comparison, whichever is the best match.

  2. On the Licensing & Certification benefit info page, update to navigate to the Licensing & Certification search flow in the tool. -

  3. On the Licensing & Certification benefit info page, updates may be needed to the "Tips for using the tool" section.
    weams 10

  4. On the National Tests benefit info page, update to navigate to the National Tests page in the tool.
    weams 9


Tasks

  • IA works with product team and CAIA writer to identify entry points and suggested crosslinks
  • IA documents plan in IA Spec in the IA Spec folder on github
  • IA adds the IA spec to the intake ticket for the product team, tags Lily/Megan
  • Lily ensures IA spec is included in content entry point ticket for Megan
  • Lily confirms whether work requires a writer (or if writer is already involved), or SME review. Criteria: Any surrounding content change besides replacing PDF link with online form link
  • Content writer notifies Megan/Chelsea when it’s time to implement
  • If staged rollout: Content publishes the main static page or landing page with the react widget and DOES NOT implement entry points or crosslinks.
  • Once a product is launched to 100% of users (staged rollout or not), content will take out the widget and put the rest of the entry points/crosslinks in in Drupal and publish.
  • Publish
  • Megan or Chelsea will add Kristin or Jenny as an assignee to the entry point ticket
  • Content will let IA know final decisions on crosslinks and why, so IA can document
  • IA will check live site for accuracy of implementation, compared to IA spec
  • Kristin OR Jenny will update sitemaps with color coding to show product/change was implemented

Acceptance Criteria

  • Updated pages are live
  • IA review complete
  • Sitemaps update

How to configure this issue

  • Attached to a Milestone (when will this be completed?)
  • Attached to an Epic (what body of work is this a part of?)
  • Labeled with Team (product support, analytics-insights, operations, service-design, Console-Services, tools-fe)
  • Labeled with Practice Area (backend, frontend, devops, design, research, product, ia, qa, analytics, contact center, research, accessibility, content)
  • Labeled with Type (bug, request, discovery, documentation, etc.)
@scjwalker scjwalker changed the title [CAIA Internal]:<EDM team><WEAMS migration><Content changes> [CAIA Internal]: EDM team WEAMS migration Content changes Dec 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants