FE Display of Non-Clinical Services on VAMC Top Task Pages should not be in a Card component

[davidmpickett]

User Story or Problem Statement

In the tugboat Integration branch, non-clinical services on VAMC Top Task Pages are presenting inside a bordered box for Service Locations. This does not match the current design ( or future design, later).

Description or Additional Context

• https://web-xptmfsnjoodldn85nzgkrgljqtfbz24b.ci.cms.va.gov/northeast-ohio-health-care/medical-records-office/#get-your-records-in-person
• https://web-xptmfsnjoodldn85nzgkrgljqtfbz24b.ci.cms.va.gov/northeast-ohio-health-care/billing-and-insurance/#pay-in-person
• https://web-xptmfsnjoodldn85nzgkrgljqtfbz24b.ci.cms.va.gov/northeast-ohio-health-care/register-for-care/#patient-registration-admission

SCREENSHOTS

Examples of 3 top task pages where the bordered box is visible, and needs to go away: 

Steps for Implementation

Acceptance Criteria

• Non-clinical service locations do not use the card component/border on these templates
  • Billing and Insurance
  • Medical Records
  • Register for Care
• Requires design review

[jilladams]

This is in PR.
The Tugboat FE needs to be built from the PR branch in order to QA for merge.
That is queued behind Christian's rebuild for the Unspecified = NULL migration fix.

[thejordanwood]

I reviewed the PR for this and have approved it.

Following up on spacing: @eselkin Thanks for bringing up in scrum that the space between the location header and the facility address is 48px instead of the 45px specified in the design mockup. In this case, I'm fine with the difference since the VADS ecosystem doesn't have the 45px spacing.

[laflannery]

I just want to note here for reference because it seems as though my direction on the PR looks to be in contrast to Jordan's comment above.

I am working off this Figma file in which the space between the Facility address and the "Location" header is 24px, which is just about the standard DS spacing (they actually state it should be 25.5px)

This is why I have recommended in my comment we remove the extra large spacing and custom spacing I was seeing and stick instead with the standard DS spacing.

[davidmpickett]

This ticket was not supposed to include altering any spacing. it was only supposed to be about removing the border. I apologize for linking to a speculative WIP design as reference. By default, these should match the current spacing on Prod (which is 25.5)

[davidmpickett]

Last step is verifying this on SL tugboat after the migration finished and Content Release runs

[davidmpickett]

Confirmed on Tugboat