department-of-veterans-affairs / va.gov-team

Public resources for building on and in support of VA.gov. Visit complete Knowledge Hub:
https://depo-platform-documentation.scrollhelp.site/index.html
283 stars 205 forks source link

Content Support Request from VAOS #18500

Closed laurenernest closed 3 years ago

laurenernest commented 3 years ago

Background

The Help Desk notified the VAOS team that the VVC support hours are 24/7. We've made the respective change in the VAOS app footer and would like to align similar content.

Content request

Update existing copy for VA Video Connect support hours on the static landing page for VAOS.

From:

We’re here Monday through Saturday, 7:00 a.m. to 11:00 p.m. ET.

To:

We’re here 24/7.

Screen Shot 2021-01-13 at 8.13.52 AM.jpg

Desired/target implementation date

1/21/21

About your team


Public Websites internal use

Acceptance Criteria

Definition of Done

DanielleThierryUSDSVA commented 3 years ago

Hi @RLHecht. Could you work with Kelson to update this, since the content isn't in Drupal?

Adding sitewide content labels.

kelsonic commented 3 years ago

PR is up: https://github.com/department-of-veterans-affairs/vets-website/pull/16183

RLHecht commented 3 years ago

Thanks, @kelsonic ! @DanielleThierryUSDSVA This change should be live today or tomorrow.

kelsonic commented 3 years ago

PR merged, will go out with daily deploy tomorrow since I missed the cut off today 🙂

brianalloyd commented 3 years ago

@DanielleThierryUSDSVA @RLHecht this has been merged, wondering if we can close this ticket?

RLHecht commented 3 years ago

Yep, all good to close, @brianalloyd. Thanks!

laurenernest commented 3 years ago

@DanielleThierryUSDSVA How do we handle the "last updated" date since it's now no longer accurate?

Screen_Shot_2021-02-26_at_3_33_08_PM
DanielleThierryUSDSVA commented 3 years ago

Great question, @laurenernest! I think for the moment, we just go in an republish the Drupal page any time we make an update in the react file so the dates stay consistent.

But, this speaks to a larger need to shift back to having more of this content in Drupal. When the implementation of this came to the PW team, this approach of all content (except intro) in Drupal was a solution because of urgent timing and lots of complications. But the ideal would be for as little of the content as possible to be in the react widget and instead live within Drupal so the content team can manage it.

That's on our list of things we want to do in 2021. @RLHecht we can add to our next content mtg and set up an epic for the work (which would need to start w/ an audit of the pages to determine which content is dynamic outside of the sign-in modal). Thanks!

brianalloyd commented 3 years ago

Closing per Validation, thanks @RLHecht