strelichl commented 7 months ago

CAIA Internal Collaboration

WIP

This ticket is designed to coordinate IA and content tasks for PRODUCT UPDATES to update mega menu, left nav, and hub pages in Drupal.

Issue Description

Planning for launch of digitized 20-10207 - Priority Processing form.

[x] IA works with product team and CAIA writer to identify entry points and suggested crosslinks
[x] IA documents plan in IA Spec in the IA Spec folder on github
[x] 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

[ ] 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.)

jennymayoco commented 6 months ago

We are proposing related benefit hubs have a link to the supporting forms page rather than to 10207. I documented this in the IA spec for supporting forms, items 3-5. This is so traffic isn't directed to one specific form, but rather than to a supporting forms page. We're suggesting that for "how to apply" pages, the link is lower in the "more info" / related links section and then higher up on "after you apply" pages as well as adding a more detailed description, such as the one in https://www.va.gov/disability/how-to-file-claim/additional-forms/
I've updated the 10207 IA spec that recommends adding crosslinks to the online applications and to connect with those teams to confirm if the form can be linked from there.

Let me know if there are any questions

jennymayoco commented 5 months ago

Team flagged this page as a potential entry point for the form: https://www.va.gov/disability/how-to-file-claim/when-to-file/.

UPDATE 4/10: Connected with Megan and we are adding it to the IA spec as one for Content to review.

megzehn commented 4 months ago

Update: @tbaker1026 confirmed that 20-10207 is now open to 100% of users and we can add the online link to the Find a form page.

@saratorres2 I've added a link to the Find a form page (node=5787). Could you review and publish?

We're going to hold on adding other entry links until we assess its placement here for a bit.

kristinoletmuskat commented 1 month ago

@megzehn -- hey! Just seeing if we wanted to add any additional entry points for this? Or any other IA work we can support with?