Open ayush-chak opened 2 weeks ago
@aprocik1 to look into this for next refinement meeting.
@laurwill and @sterkenburgsara are working on this together. I'm moving this ticket to in refinement for now.
@carafrissell1 could you drop a screenshot of the current content an authenticated user sees on this page? Then I can pass back content for the update. Thank you!
Sorry for the 2 screenshots - it's a long page, but this is what a user sees when they are logged on this page.
@sterkenburgsara, @carafrissell1, @laurwill - let's consolidate all discussion to this ticket (so that wires aren't getting crossed - didn't realize we had two tickets in process, my mistake). Thanks!
Hey @laurwill @sterkenburgsara @micahtaylor @ayush-chak wanted to confirm/update 2 things:
Hi @carafrissell1 ,
Here is the Figma frame that has the addition of @laurwill suggestions. Feel free to leave comments or let me know if you need access or want edit access. cc @ayush-chak
I do not believe cartography thinks that we own the sign in widgets for this page. But you can discuss with @wesrowe if you have questions about that, @ayush-chak
On Fri, Nov 22, 2024 at 09:49 Micah Taylor @.***> wrote:
Here https://www.figma.com/design/RJ6OVm0MWD2WprVfO7E3lp/Travel-reimbursement-status-page?node-id=4870-8307&t=5h6V8S1QzP9IpXHt-4 is the Figma frame that has the addition of @laurwill https://github.com/laurwill suggestions. Feel free to leave comments or let me know if you need access or want edit access. cc @ayush-chak https://github.com/ayush-chak
— Reply to this email directly, view it on GitHub https://github.com/department-of-veterans-affairs/va.gov-team/issues/96858#issuecomment-2494069976, or unsubscribe https://github.com/notifications/unsubscribe-auth/A3NULPBZIMS546AVEIVJA5D2B5G7HAVCNFSM6AAAAABRSSKZNKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIOJUGA3DSOJXGY . You are receiving this because you were mentioned.Message ID: @.*** .com>
Hi @sterkenburgsara / @laurwill (sorry, not sure whom this question goes to) - could you explain again how the unauth page might be blocked? Our understanding is that since the widget already exists, we should be able just make a few changes on the widget itself?
In addition, we were wondering if you would be open to removing the "You can file a claim online through the Beneficiary Travel Self Service System (BTSSS)" from the Drupal content so that we can include it in our react widget (basically, we would then be able to change that as the Travel Pay experience changes. As you can probably tell, it's already a slightly confusing experience: the widget currently requires users to "log in to file a claim" - but the authenticated page then links them out to the BTSSS portal, where they would have to log in one more time separately.)
Hi @ayush-chak , I like that approach! So the widget content would include this whole section going forward, for unauth and auth:
As far as the unauth page being blocked, I'm not sure what that means — are you talking about the need to update the sign-in alert to use the new standardized component? I don't think we have any work needed on the unauthenticated content that lives in Drupal.
Maybe this isn’t blocked! I was referring to the new sign-in widgets that are being built now by identity and VADS teams. Defer to Laura!
On Tue, Nov 26, 2024 at 11:55 laurwill @.***> wrote:
Hi @ayush-chak https://github.com/ayush-chak , I like that approach! So the widget content would include this whole section going forward, for unauth and auth: image.png (view on web) https://github.com/user-attachments/assets/0176e076-32c1-4f48-8f0e-17af06659e39
image.png (view on web) https://github.com/user-attachments/assets/7acab4fb-4967-4e8b-8b27-88ccb6ea8dae
As far as the unauth page being blocked, I'm not sure what that means — are you talking about the need to update the sign-in alert to use the new standardized component? I don't think we have any work needed on the unauthenticated content that lives in Drupal.
— Reply to this email directly, view it on GitHub https://github.com/department-of-veterans-affairs/va.gov-team/issues/96858#issuecomment-2501594515, or unsubscribe https://github.com/notifications/unsubscribe-auth/A3NULPGKTLVQZ76PJMPWV3D2CSY2XAVCNFSM6AAAAABRSSKZNKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKMBRGU4TINJRGU . You are receiving this because you were mentioned.Message ID: @.*** .com>
Content, accessibility, information architecture (CAIA) new initiative collaboration request
Use this ticket to request collaboration on a new initiative with the sitewide content, accessibility, and information architecture (CAIA) shared services team. Feel free to delete instructions and unselected options from the ticket to make it easier to scan.
NOTE FROM TEAM: We are looking to add an entry point and were directed here - would love help understanding if we're at the right place! (Further context is here)[https://dsva.slack.com/archives/C01K37HRUAH/p1731084693531749]
Your team
CAIA specialists involved
Filled out by CAIA
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?
Hoping to make this link viewable by Veterans as we roll out to enable them to view travel claim status without having to log into the BTSSS portal.
We're hoping to, at our PO's request, get a link added to this page
Supporting artifacts
Here's the current status page: https://staging.va.gov/my-health/travel-claim-status
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?
This is likely a blocker from VTP to greenlight our rollout, so this remains our last step.
Will you release this new product incrementally (for example, release to 25% of users to start)?
[ ] No
Note: For an incremental launch, we use React widgets to display dynamic content. We'll need at least 2 weeks of extra time to coordinate the content for this and work with your engineer. Learn more about our process for dynamic content. If your launch plans change, notify CAIA of the change as soon as possible so we can talk about how that will impact the timeline.
If you are releasing incrementally:
Enter dates
Name
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 a link to your Collaboration Cycle Request:
Next steps
Suggest an addition or update to the design system team