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 Content Review] Public Websites: Phase 2 Discharge Upgrade Wizard #71562

Open
1 of 8 tasks
FranECross opened this issue Dec 8, 2023 · 7 comments
Open
1 of 8 tasks

Comments

@FranECross
Copy link
Contributor

FranECross commented Dec 8, 2023

CAIA Content Review

About your team

  • Team name: Public Websites
  • OCTO-DE product owner: Dave Conlon
  • Product name: Discharge Upgrade Wizard
  • Product manager: Fran Cross
  • Slack channel: #sitewide-public-websites
  • Dedicated content writer on your team (if you have one): None
  • Dedicated a11y specialist on your team (if you have one): Laura Flannery

About your request

Describe your project goals

The existing discharge upgrade wizard was built in Vets.gov days. It does not use current design or content patterns. It requires a lot of scrolling due to the legacy pattern. We are also unsure if the information within the wizard remains correct.

Based on learnings from the PACT Act wizard, this effort will improve the ability for Veterans to determine their eligibility for a discharge upgrade by re-modernizing the product to align with current VA.gov design and content standards, and convert to a subtask pattern.

Note that Phase 1 content review has already occurred, and Katherine Fung explained that there will be a Phase 2 content review after stakeholders are identified, and also because a legal review will need to occur. Phase 1 Content Ticket here.

What is your team working on?

  • Making changes to an existing page, tool, form, or app

Describe how you would like to collaborate with CAIA

We are working with CAIA in two phases for this project. They have provided edits in December 2023 for Phase 1 (this ticket) (which didn't require stakeholder review), and Phase 2 (timeline TBD) edits will require legal and stakeholders review of the following areas in the wizard to determine what edits, if any, will be made:

  • landing page
  • results section
  • questions

Type of Collaboration

Check all the types of collaboration you're requesting, below:

Content

  • Creating new content
  • Updating existing content
  • Translating content
  • Something else: insert type of collaboration

Accessibility

  • Wireframes or prototypes review
  • PDF review
  • User research support
  • Something else: insert type of collaboration

IA

  • User flows
  • Page placement
  • URLs
  • Breadcrumbs and left nav placement
  • Redirects
  • Something else: insert type of collaboration

Other

  • Check this box if you're not sure what kind of support you need, and we'll schedule an introductory meeting to learn more about your project.

Collaboration timeframe

We work on nearly every OCTO product and manage all unauthenticated content on VA.gov, so we will need to prioritize intake requests based on overall workload and VA and OCTO priorities.

Your timeline

  • Check yes, if this request is tied to a Congressional mandate or timeline?

Description

Describe where you are in your project's timeline.

Phase 2 timeline is TBD at this time per Katherine Fung; the stakeholders need to be identified, which will then allow meetings/reviews to ensue. Phase 1 timeline will be implemented in January 2024.

Collaboration cycle

If you’re going through the collaboration cycle with the governance team, link to the ticket:

  • Ticket Number: xxxxxx
  • If you’re not going through the collaboration cycle, or you’re unsure, check here, and we can follow up:
    • Not going through collab cycle

Phases Completed

Check any phases you’ve already completed:

  • Phase 1 content review and implementation scheduling
  • Design intent
  • Midpoint review
  • Staging

Supporting artifacts

Please provide links to any supporting artifacts we might need to begin work. This can include your product outline, user flows, mockups and prototypes, draft content, etc.

Link to phase 1 ticket

Next steps

  • Once you’ve submitted this ticket, please post a link to this issue in the #sitewide-content-ia Slack channel and tag @Terry Nichols.
    • A member of the CAIA team will aim to respond to your Slack message within 24 hours to acknowledge receipt - should we need any additional information regarding your request we will reach out to you to confirm.
    • The CAIA Operations group will meet to go over the info in your request and then reach out if we have any questions.
    • Depending on the request, it may make sense to schedule a kickoff meeting to better understand how we'll partner with you!
  • Please review the remaining next steps in the VFS Team Tasks section, listed below.

TASKS


VFS Team Tasks

Preview Give feedback
No tasks being tracked yet.

a11y Tasks

Preview Give feedback

Content Tasks

Preview Give feedback
  1. sitewide CAIA sitewide content
    hermonica

IA Tasks

Preview Give feedback

CAIA Ops

Preview Give feedback
@aprocik1
Copy link
Contributor

From Beth: "For phase 2, when we need a stakeholder, David.Kesselman@va.gov is going to route this for SME review to the Office of Policy and Oversite. He'll need the following info:

  • Description of Project
  • Length of request
  • Anticipated number of hours per week"

@katherine-fung
Copy link
Contributor

I've emailed David with our questions and to request a review.

@katherine-fung
Copy link
Contributor

Hi @strelichl, can you please create a content ticket for this work? David and the SMEs have provided feedback, so we can continue with phase 2 of this work. Thanks!

@strelichl
Copy link
Contributor

Hi @FranECross, I'm doing some cross-linking of our work with Collab Cycle intakes--is this work related to this CC intake?

@FranECross
Copy link
Contributor Author

FranECross commented Aug 16, 2024

@strelichl Thanks for checking! It's not. The CC intake above is for Phase 1, and the implementation is almost done and I'll be able to request a Staging review. We don't actually know when Phase 2 will be. It could conceivably be next year. Let me review this one though and see if I mislabeled it or created it thinking Phase 2 was in the works (back then).

@FranECross
Copy link
Contributor Author

@strelichl This does look like it pertains only to Phase 2, and at the time of creating it, we though we'd be getting phase 2 content fairly quickly.

@strelichl
Copy link
Contributor

Thanks for this context @FranECross! I'll leave it unlinked

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

7 participants