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
284 stars 206 forks source link

Updating Eligibility h3 question to be consistent across all hubs #10787

Closed RLHecht closed 3 years ago

RLHecht commented 4 years ago

User story

As a content team member I need to ensure our content is consistent across all hubs.

Issue Description

Currently we have different wordings for the H3 at the top of our eligibility section asking Veterans if they are eligible for specific benefits. We should be consistent with our language going forward as well as what is currently on the site. It should read as follows:

H3 Am I eligible for [X benefits]? You may be eligible for [X benefits] if you meet [all/both/at least one] of the requirements listed below.

See example here: Screen Shot 2020-06-30 at 2.46.55 PM.png

Tasks

Update published eligibility pages with the above wording (Selina).

Acceptance Criteria

MickinSahni commented 4 years ago

Spun off bug ticket #13480

lunascoop commented 4 years ago

I have updated the eligibility h3 question for the benefit hubs.

Careers and employment

Life insurance

Health care

Housing: For the first page listed, the eligibility language template may not work. "Eligible" is kind of used back to back so it may sound off. Perhaps we can change it to its acronym (COE). I'll leave it to you to decide. Included a screenshot below.

Screen Shot 2020-09-11 at 10 38 35 AM

Education: The first page listed below does not include an eligibility blue box (screenshot of current version below). I assume this is because the content required its own page, which is linked at the bottom of the section. I updated the blue eligibility box on the linked page (Post 9/11 GI Bill).

Screen Shot 2020-09-11 at 10 42 54 AM

Disability

Burials and memorials

Pension

bethpottsVADEPO commented 4 years ago

@DanielleThierryUSDSVA for awareness. This will tamp down our use of "get" (Can I get) and address the current inconsistencies.

DanielleThierryUSDSVA commented 4 years ago

Thanks! Randi and I have touched base about this.

@lunascoop @RLHecht Just a note that you don't have to worry about the Agent Orange pages since those are going away with the consolidation work in that section. Thanks!

RLHecht commented 4 years ago

These pages have all been reviewed and published except for a few, which I also slacked @bethpottsVADEPO about. For these, the new wording seemed awkward and I wasn't sure if we should keep as is or update in a different way. Beth was going to review. These are the pages:

http://preview-prod.vfs.va.gov/preview?nodeId=753 http://preview-prod.vfs.va.gov/preview?nodeId=760 http://preview-prod.vfs.va.gov/preview?nodeId=761 (No lead in sentence for our bulleted list) http://preview-prod.vfs.va.gov/preview?nodeId=925 http://preview-prod.vfs.va.gov/preview?nodeId=919 http://preview-prod.vfs.va.gov/preview?nodeId=920 http://preview-prod.vfs.va.gov/preview?nodeId=931 (I think this one should stay as it was)

FYSA @brianalloyd @MickinSahni http://preview-prod.vfs.va.gov/preview?nodeId=918 http://preview-prod.vfs.va.gov/preview?nodeId=952

DanielleThierryUSDSVA commented 4 years ago

Just noting that Beth and I will be reviewing these together on Thursday.

DanielleThierryUSDSVA commented 4 years ago

Hi @RLHecht. Beth and I reviewed some of these. Here's guidance on the ones we got through today:

Please revert back to the "Can I get" language for:

http://preview-prod.vfs.va.gov/preview?nodeId=753 (we did this one, please just check for errors) http://preview-prod.vfs.va.gov/preview?nodeId=760 http://preview-prod.vfs.va.gov/preview?nodeId=761

Let's use "Can I use my VA education benefits..." and "You may be able to use your education benefits for..." for:

http://preview-prod.vfs.va.gov/preview?nodeId=925 http://preview-prod.vfs.va.gov/preview?nodeId=919

Will update with others soon. Thanks!

RLHecht commented 4 years ago

Changes to the pages above have been made and published.

DanielleThierryUSDSVA commented 3 years ago

Beth/Danielle content planning meeting 11.4.21:

bethpottsVADEPO commented 3 years ago

@RLHecht Here are the remaining oddball headers that you'd identified above: http://preview-prod.vfs.va.gov/preview?nodeId=920 (please review my edit to "can I get...") http://preview-prod.vfs.va.gov/preview?nodeId=931 (Agree that this one should stay as it is)

Randi, these are the 2 you called out for Mickin and Brian (I don't remember what they would have been assessing). The first one (918) looks ok to me--do you know what the issue was? For the second one below, I edited in drupal. http://preview-prod.vfs.va.gov/preview?nodeId=918 (no change) http://preview-prod.vfs.va.gov/preview?nodeId=952 (please review my edit to the header and first line of text)

Here's the related work that you can either use this ticket for or create a new ticket for: 1/ Make all blue box headers H2s. Some are currently H3s. 2/ Fix the start of each bulleted item so each line of text can stand-alone (add a subject, and remove that subject from the bold lead-in line above the list.

LIKE THIS: At least one of these must be true:

NOT LIKE THIS: At least one of these must be true. You:

RLHecht commented 3 years ago

Work in this ticket is now complete. I opened a new ticket (#32659) to do the work of changing H3s to H2s and adjusting the language in bulleted lists so that the subject is in each item.