Open FranECross opened 10 months ago
Hey! Just popping in to say I got your ticket and I am going to talk to Mikki about this on Thursday.
Update: We discussed this in more detail in this slack thread.
We decided that the team does not need a staging URL, but we will provide sample URLs for the questions of the flow in line with guidance provided to other teams that are updating the wizard pattern to the subtask pattern.
Hey hey this all looks pretty straightforward -- I see in your mural documentation that there might be a few more screens than show in the sketch file, which is fine. I think our main guidance is to not make unnecessary subdirectories, and just nest all of the questions under the base URL. So if you need to tweak any of these or add, feel free.
So, base URL will stay the same as: va.gov/discharge-upgrade-instructions/
And these child pages would sit under that:
/branch-of-service
/discharge-year
/reason
/changes-requested
/court-martial
/previously-applied
/previously-applied-date
/earlier-honorable-service
/review
/results
lmk if you have any Qs!
@kristinoletmuskat Thanks so much for the quick turnaround and information! 🎉 I'll defer to @chriskim2311 for any technical questions upon his return. cc @jilladams
@kristinoletmuskat @FranECross Following up from the slack thread and the messages here. I think this is a good solution that I can work with. Thanks for your help!
Request has been fulfilled; closing ticket.
Thread about next steps for review: https://dsva.slack.com/archives/C01K37HRUAH/p1725997353585629
Fran confirmed that we can close this intake ticket as complete. I'm moving it to validate for now.
Update: We're going to keep this open for now to track Monica's work on Fran's recent email regarding the results screen.
Content, accessibility, information architecture (CAIA) new initiative collaboration request
Use this ticket to start collaboration on a new initiative with the sitewide content, accessibility, and information architecture (CAIA) team.
Note: If you’re already partnering with us on an initiative, you don't need to fill out this request form. If you don’t have access to your initiative’s CAIA epic, post a message in the #sitewide-content-accessibility-ia slack channel and tag
@Terry Nichols
and@Lily Strelich
.About your team
About your initiative
Which of these descriptions best fits the work we’ll partner on?
Select all that apply.
What's the nature of your initiative and desired outcomes?
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.
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.
To this end, we are requesting a URL so that we can test it in Staging prior to cutting over to the new code in Production. Please see this Slack thread for information from the engineers: https://dsva.slack.com/archives/C52CL1PKQ/p1705605019314219
Collaboration timeframe
Note: 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.
Is this work tied to a Congressional mandate, change in law or policy, or upcoming event with a specific deadline?
Where are you at in your timeline?
Tell us briefly about what you're working on now (such as initial discovery, wireframing, or usability research planning) and add any known dates for upcoming milestones or deadlines.
Collaboration cycle
Which phases of the collaboration cycle have you completed?
Select all that apply.
Collaboration cycle ticket
If you’re going through the collaboration cycle, provide your ticket number and link:
Supporting artifacts
Provide links to any supporting artifacts that can help us better understand your initiative and begin collaboration. Include artifacts like your product outline, user flows, mockups and prototypes, or any draft content.
Next steps
@Terry Nichols
. We’ll reply within 24 hours to acknowledge receipt. We'll then review the artifacts in more detail and work with you to determine timing for collaboration. Depending on the work, we may schedule a kickoff meeting to better understand how we'll partner together.Tasks