VACMS-20435: Updates description meta tag for va forms to use field_v…

[dsasser]

Description

Updates description meta tag for va forms to use field_va_form_name

Relates to #20435

Testing done

Manual but we need a full TB instance to check end-to-end that the meta tag is making its way to the FE. confirmed.

Screenshots

QA steps

Steps to view meta description in Chrome developer tools

• Open developer tools
• Click Elements tab
• Using search feature in Developer tools, search for Description and look at <meta name="description" content="">

Example of meta description tag:

Forms:

Form Name	Drupal Link	Frontend Link	Note
Nonsupervised Lender's Nomination and Recommendation of Credit Underwriter	/find-forms/about-form-26-8736a	/find-forms/about-form-26-8736a	Spot check
Clinical Trial Inclusion/Enrollment Report	/find-forms/about-form-10-0455a	/find-forms/about-form-10-0455a	Spot check
CHAMPVA Benefits Election Affirmation	/find-forms/about-form-10-493b	/find-forms/about-form-10-493b	Spot check
CHAMPVA—Other Health Insurance (OHI) Certification	/find-forms/about-form-10-7959c	/find-forms/about-form-10-7959c	Form with 'When to use' data
VA Advance Directive: Durable Power of Attorney for Health Care and Living Will	/find-forms/about-form-10-0137	/find-forms/about-form-10-0137	Form with 'When to use' data

As content admin

1. For each of the above Forms
   • Visit the Drupal link and confirm the Form Name matches the provided Form Name in the table
   • Visit the Frontend link and confirm the meta description tag content matches the provided Form Name
   • If the Form has 'When to use' note, confirm that the meta description no longer matches the 'When to use' value in Drupal.

Definition of Done

• Documentation has been updated, if applicable.
• Tests have been added if necessary.
• Automated tests have passed.
• Code Quality Tests have passed.
• Acceptance Criteria in related issue are met.
• Manual Code Review Approved.
• If there are field changes, front end output has been thoroughly checked.

Select Team for PR review

• CMS Team
• Public websites
• Facilities
• User support
• Accelerated Publishing

[github-actions]

Checking composer.lock changes...

[github-actions]

Checking composer.lock changes...

[omahane]

The first 3 in the QA steps works as described and as expected. Plus, they differed from Prod, which is what I'd expect.

VA Form 10-7959C, however, differed from the preceding, matched prod and has data whose origin I can't find.

[dsasser]

The first 3 in the QA steps works as described and as expected. Plus, they differed from Prod, which is what I'd expect.

VA Form 10-7959C, however, differed from the preceding, matched prod and has data whose origin I can't find.

Found the root cause:
The description data is coming from a "hidden" (via entity form display) field, field_meta_tags. Will determine next steps with team.

I also found where we hid the meta tags field from editors: #3310

[github-actions]

Checking composer.lock changes...

[github-actions]

Checking composer.lock changes...

[omahane]

Works as designed. Good investigation.

[github-actions]

Checking composer.lock changes...

[va-cms-bot]

Tugboat has finished building the preview for this pull request!

Links:

• https://pr20709-wvr5ocsbdk55xykhbj1smyaftnh73q24.ci.cms.va.gov
• https://cms-wvr5ocsbdk55xykhbj1smyaftnh73q24.ci.cms.va.gov
• https://web-wvr5ocsbdk55xykhbj1smyaftnh73q24.ci.cms.va.gov
• https://storybook-wvr5ocsbdk55xykhbj1smyaftnh73q24.ci.cms.va.gov
• https://next-wvr5ocsbdk55xykhbj1smyaftnh73q24.ci.cms.va.gov

Dashboard:

• https://tugboat.vfs.va.gov/67bf4e30d00f033beb4e7268