search

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
282 stars 201 forks source link

Build, edit, and publish Eligibility for Veterans Pension page in Spanish #65723

Open RLHecht opened 1 year ago

RLHecht commented 1 year ago

Issue Description

As part of our ongoing effort to have more multilingual content on our site, we need to publish the core Pension pages in Spanish. This includes Eligibility for Veterans Pension.

We need to build the page in Drupal, review, and publish.

Content from translation team: LS-2022-0118394-G-SPA-FINAL_Pension content for Spanish translation Batch 1 (1).docx

Tasks

Prepublishing checklist ## For all VA.gov pages (including those in Resources and Support) ### Before you begin - [ ] Confirm that there are no updates in draft by other content authors that aren't ready to be published. Check the revision log and then confirm with the content author who made the previous edits that the page is ready to publish. ### Accessibility standards - [ ] If your link or button will take the user off VA.gov, confirm that the text for the link or button contains a purpose and a target. The user should be able to tell from the link or button text what the call to action is (the purpose) and where they will end up if they click on the link (the target). The following link is an example of this:
[Read more about making links accessible on AccessibilityOz](https://www.accessibilityoz.com/2014/02/links-and-accessibility/)
**Note:** When you direct the user to another VA.gov page, the link only needs to contain text indicating purpose (the call to action). - [ ] Confirm all phone numbers are in aria labels. [Learn how to code numbers with aria labels](https://design.va.gov/content-style-guide/dates-and-numbers#phone-numbers) - [ ] Confirm that the hierarchy of section and subsection titles is correct (H1 to H2 to H3—levels shouldn't be skipped). [Learn more about section titles](https://design.va.gov/content-style-guide/page-titles-and-section-titles) - [ ] Replace any sighted language ("view," "see," "look") with a word that's inclusive of our screen reader users ("check," "go to," "review"). - [ ] Avoid using other ability-focused language. ("hear back from") ### Link standards - [ ] Confirm that links work (aren't broken—no error message) and point to the intended page (you pasted in the correct URL or chose the correct node ID). - [ ] Confirm all link text is 100 characters or less. - [ ] Check that you've selected a node ID for all links pointing to VA.gov (internal) pages. Only paste in a URL if the page you're linking to doesn't live in our CMS (isn't one of our modernized pages). [Learn how to add node IDs in Drupal](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/teams/vsa/teams/sitewide-content/how-to-do-different-tasks/linking-with-node-ids.md) - [ ] Check that all anchor/jump links are pointing to a node followed by # and the header identifier (Example: /node/47278/#information-for-survivors). Double check all anchor/jump links post-publish. ### CMS standards - [ ] Make sure all apostrophes and quotation marks are curly not straight. (Once this is automatic in Drupal, we can remove this item.) - [ ] If there are alerts at the top of the Drupal Edit node for broken links, redirected links, or links to unpublished pages, correct the issues. If there's an alert for a broken link but the link is actually working, report the issue to the CMS help desk. [Read more about link alerts in the CMS knowledge base](https://prod.cms.va.gov/help/cms-basics/how-to-fix-broken-links-and-redirects) - [ ] If publishing a brand-new page, confirm the left nav and url are set up correclty. (If the page is a child page, the section needs to be the same as the parent page in order for the left nav to show.) [Learn how to set up a url and left nav in Drupal](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/teams/vsa/teams/sitewide-content/how-to-do-different-tasks/adding-left-nav-and-url.md) - [ ] Check if the page has a new or updated alert. If so, publish the alert separately. ### Additional checks for translated articles - [ ] If we don't have updated translated versions, add the alert that links to the corresponding English page and lets users know that the translated pages aren't up to date.

Acceptance Criteria

ABeltran77 commented 11 months ago

@RLHecht @strelichl @megzehn Eligibility page built. FYI -

Please note:

  1. Page is missing the translation for the Title & Title Intro. I translated it so as to have something in place for the meantime. Do we need to send to translators?
  2. Only the fist sentence in Meta fit in the box, otherwise it's over by 81 characters.
  3. I receive this message when trying to preview: "404 Page not found"
RLHecht commented 11 months ago

Thanks so much for building this page @ABeltran77 ! Preview should be working now if you do the fix I posted in slack (change https to http). It looks like you need to change the eligibility section to the featured content blue box content block. And it looks like there are a few other minor style things you'll need to tweak before passing to Megan. Thanks so much!

RLHecht commented 11 months ago

@ABeltran77 Can you translate this for the meta description and see if it fits?

If you're a wartime Veteran, you may qualify for monthly VA pension payments. Find out if you're eligible based on your age or a permanent and total non-service-connected disability, as well as your income and net worth.

ABeltran77 commented 11 months ago

@RLHecht Thanks for the info on the Preview issue. I'll fix and check the Meta shortly.

ABeltran77 commented 11 months ago

@RLHecht @strelichl The following have been completed:
1 - changed the eligibility section to the featured content blue box content block 2 - Translated and input the new Meta description (it did fit) FYI - I made several attempts to correct the spacing pertaining to the first link but was unsuccessful. Sorry, I feel I'm spending too much time on this and struggling to correct it....ughhhh. @megzehn you'll see what I'm referring to when you review. I know we encountered this issue before. Let me know what I'm doing wrong here.

megzehn commented 11 months ago

Noting that I reviewed this page, but holding on publishing since we're currently editing the English version.

Pasting the Drupal link in this ticket for when we come back to it: http://preview-prod.vfs.va.gov/preview?nodeId=62416

@ABeltran77, for future tickets when you're building a new page, could you drop the Drupal link in the ticket? This one took a little time to find, since the translators didn't include an H1!

ABeltran77 commented 11 months ago

@megzehn Yes! Sorry about that.

moviedosoco commented 1 month ago

@RLHecht I resumed work on this page where it was left off, comparing the English live page with the Spanish draft, and updating the content to ensure both pages matched. I also made some copy tweaks.

I'm tagging @megzehn and @saratorres2 to review and publish this page in Spanish: 'Elegibilidad para la pensión de veteranos' http://preview-prod.vfs.va.gov/preview?nodeId=62416

Please note that I did not change the Section; I left it as it was (sitewide content team). Thank you.

strelichl commented 1 month ago

Moving this into Ready until Sara can pick it up.