Collaboration Cycle Kickoff [Search and Discovery, R&S Article UI Consistency]

[nicole-leonard]

Steps to complete the Collaboration Cycle Kickoff

VFS Product Manager- Nicole Leonard

• [ ] Create this issue and notify the Collaboration Cycle team of this ticket in the in #vfs-platform-support (see Slack Workflow (User guide).
• [ ] Answer the questions below and attach any artifacts you have available.
• [ ] Close this ticket when kickoff is complete and Platform has provided the recommended touch points.

Platform

• [ ] Review the responses and comment in ticket with recommended touch points and practice area involvement.
• [ ] Platform: Add project to the Platform Collaboration Point Tracker.

Artifacts (if available)

Provide links or documents for the following:

-Initiative Brief- https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/products/resources-and-support/ui-consistency-initiative-brief.md

Questions

Please refer to the guidance in Getting Started with the Collaboration Cycle for detailed information and examples for the below questions.

1. Will your work result in visible changes to the user experience?

• [ x] Yes
• [ ] No

2. Is your work a new product or an iteration to an existing product?

• [ ] New
• [ X] Iteration

-->

3. If this is an iteration, please tell us what product or feature you're iterating.

Product or feature: All R&S Article Pages

4. Are you making changes to the visual design?

• [ X] Yes
• [ ] No

5. Are you doing research with VA.gov users?

• [ ] Yes
• [ X] No- This change is to bring the R&S Article pages up to par with the design system.

6. Will your work involve changes to: (select all that apply)

• [ ] Tools and applications*
• [ X] Static pages
• [ ] Both

For tools and applications, take into account if any static page entry points will need updates.

7. Will your work include:

• [ ] New content
• [ X] Changes to existing content- Design only

8. Are you making a change to the user flow?

• [ ] Yes
• [ X] No

-->

9. Are you making a change to urls, navigation, or entry points?

• [ ] Yes
• [ X] No

10. Does your product or feature have Google Analytics tracking and a KPI dashboard in Domo?

• [ ] Yes
• [ X] No

11. If yes, do you need to capture any other analytics or metrics in addition to what you're currently tracking?

• [ ] Yes
• [ ] No

12. Is there a GitHub label in the va.gov-team repo for this product?

• [ X] No.
• [ ] Yes. Please specify: ____

13. Who is the VA business owner for this body of work?

• [X ] VHA (Veterans Health Administration)
• [X ] VBA (Veterans Benefits Administration)
• [ X] NCA (National Cemetery Administration)
• [ X] VACO (Veterans Affairs Central Office)
• [ ] Other. Please specify: ____

Additional information

FYI: @shiragoodman , @chaseakirby

[shiragoodman]

@nicole-leonard is this ready? We ask that you post on Slack in #vfs-platform-support (per the first bullet above) when it's ready. The post on Slack is how we know to respond.

[nicole-leonard]

@shiragoodman It is. I will post it there now.

[shiragoodman]

Hi @nicole-leonard. Thanks for completing this Collaboration Cycle Kickoff ticket! Based on your responses, your project is an iteration to static content page(s) so we are recommending the following Collaboration Cycle touchpoints:

• Design Intent

• Staging Review

• Privacy, Security, Infrastructure Readiness Review

Since your work impacts static pages, please reach out to Dave Conlon to review how your work may overlap with any existing work. This will help them prioritize and identify possible areas of support needed from other teams.

The following practice areas will be included throughout the Collaboration Cycle process:

• Design
• Content
• Information Architecture (IA)
• Quality Assurance (QA)
• Accessibility
• Product

We understand that scope of work and/or solutions can change as you work through your design process. If you find that your scope and/or solution changes, please reach out so that we can update and/or modify your touchpoints appropriately.

Your project has been added to the Platform Collaboration Point Tracker. When you’re ready to schedule your recommended Collaboration Cycle touchpoints, please review the guidance outlined on the Collaboration Cycle Touchpoints page.

In addition, Resources & Support articles are out of scope for Collaboration Cycle, but since this work impacts the look and feel of all R&S pages, I think it makes sense for us to provide feedback. Thanks for bringing it to us!

[nicole-leonard]

https://github.com/department-of-veterans-affairs/va.gov-team/issues/36564 Confirmed with Dave.

[mgleo]

@nicole-leonard @shiragoodman Updated design for all Resources and support articles:

Updated sections styles:

Related information: Using the style, "Related Links, for navigating to related information outside a content section". While most links are within Resources and Support, there are times where from outside R&S are used. There could be an argument to use the "Major Links" section if links were restricted to only R&S links.

Considerations: Link descriptions are needed for this style. There is a space for content editors to enter short link descriptions within the CMS that appears to not be utilized. Alternatively, text could be pulled in and truncated from the meta description from those linked pages if those pages are located within the CMS.

Used elsewhere: Pay your VA copay bill, Coronavirus FAQs

VA benefits: Using the style, "Quick Links, for navigating to related topics located outside of a section". Link descriptions are not used within this style.

Need help?: Using the style, "Quick Links, for navigating to related topics located outside of a section". Update header from "Need more help?" to "Need help?"

Used elsewhere: Apply for burial benefits

Style guidance from VA.gov Pattern Library Sketch file

[shiragoodman]

@mgleo @nicole-leonard - next step would be to create a Design Intent ticket and schedule your review with our team.