VACMS-15142: Page-specific Q&A Report

[chri5tia]

Description

Relates to #15142

This is a content report at /admin/content/qa to show all Page-specific Q&A content that uses that template.
Note: There is Q&A-related text in other places (using other types of main content blocks like rich text and accordions) that did not use the paragraph template for page-specific Q&As, such as on the Resources and Support content types. This PR and report does not cover those instances.

Testing done

Local functional

QA steps

Log in as a user with the access that CAIA content team has.
Navigate to /admin/content/qa.
Content is populated for the following node types, with approximately 1836 total, give or take, will be a little different because of varying test data.

• 737 Benefit Detail Questions
• 31 CMS KB Article Questions
• 85 CLP Questions
• 12 Centralized Content Questions
• 970 VAMC Detail Questions

Ensure that you are able to:

• click on a node to view the listed content
• there are columns for section, node title and link, and node type

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

Is this PR blocked by another PR?

• DO NOT MERGE

Does this PR need review from a Product Owner

• Needs PO review

CMS user-facing announcement

Is an announcement needed to let editors know of this change?

• Yes, and it's written in issue ____ and queued for publication.
  • Merge and ping the UX writer so they are ready to publish after deployment
• Yes, but it hasn't yet been written
  • Don't merge yet -- ping the UX writer to write and queue content
• No announcement is needed for this code change.
  • Merge & carry on unburdened by announcements

[github-actions]

GitHub Workflows (.github/workflows/*.yml)

Have you...

• pinned all affected GitHub Actions at a specific commit by SHA?
• reviewed the source code of the action at the commit you are pinning?
• confirmed that no GitHub security measures are being bypassed?
• checked for any injection of user content into protected contexts?
• reviewed Security hardening for GitHub Actions?
• reviewed GitHub Workflows?

[jilladams]

@chri5tia still not seeing Benefit Detail Pages show up in the Tugboat instance here. Can you confirm what's happening with that before merging?

[chri5tia]

@jilladams Can you check again? I didn't push the changes that fixed it until after your comment.

[jilladams]

@chri5tia does this look how you expect it to? https://pr15833-80d0prfrxp0pohhtro3rzzrlo2bjdxih.ci.cms.va.gov/admin/content/qa

I'm seeing:

• Benefit Detail pages -- 176, https://pr15833-80d0prfrxp0pohhtro3rzzrlo2bjdxih.ci.cms.va.gov/admin/content/qa?title=&type=page&moderation_state=All. Nice fix.
• KBs - 46 - https://pr15833-80d0prfrxp0pohhtro3rzzrlo2bjdxih.ci.cms.va.gov/admin/content/qa?title=&type=documentation_page&moderation_state=All. Not all of these show the content block, not sure why.
• CLPs - 12 - https://pr15833-80d0prfrxp0pohhtro3rzzrlo2bjdxih.ci.cms.va.gov/admin/content/qa?title=&type=campaign_landing_page&moderation_state=All
• Centralized Content - 20 - that's legit, Page Specific Q&As are available on that content type. The content blocks do not all display: https://pr15833-80d0prfrxp0pohhtro3rzzrlo2bjdxih.ci.cms.va.gov/admin/content/qa?title=&type=centralized_content&moderation_state=All
• Landing page - 1 - https://pr15833-80d0prfrxp0pohhtro3rzzrlo2bjdxih.ci.cms.va.gov/admin/content/qa?title=&type=basic_landing_page&moderation_state=All. Doesn't show the content block.
• R&S page - 3 - https://pr15833-80d0prfrxp0pohhtro3rzzrlo2bjdxih.ci.cms.va.gov/admin/content/qa?title=&type=support_resources_detail_page&moderation_state=All
• VAMC Detail pages - 903 (!!) - https://pr15833-80d0prfrxp0pohhtro3rzzrlo2bjdxih.ci.cms.va.gov/admin/content/qa?title=&type=health_care_region_detail_page&moderation_state=All. Content blocks display, real big / makes the report a wonky.

@thejordanwood should probably weigh in, but I feel like we need to modify a style here to make this usable if we're going to include every single page-specific Q&A in the results. The way it works now, you could have a single table row taking up most of the page / scroll, and the identifying info about the row is middle-aligned, so you have to scroll a long way to see it. If we updated this table to make table cells top-aligned, the UX to navigate the report would be better. That could be a style plugged in somewhere in custom modules that we already have that style tables, I think. You'd need to scope it to apply to just this report, though. I don't know if this violates CMS style rules. Thinking something like:

.view-display-id-page_qa  td {
  vertical-align: top; 
}

The alternative would be to not print every single Q&A, which keeps rows shorter. Is it a big lift to display a count instead? Like: how many page-specific Q&As exist on that node?

[chri5tia]

@jilladams @thejordanwood @dsasser Can you both take a look, this is truly ready for a review now, as far as I can tell.

• blank entries have been removed
• duplicate entries have been removed
• other translations are now included

As we discussed in Slack, this is a view of questions so that the list can be paired as individual questions are moved/migrated to the Reusable Q&A template. In this way, page specific content can be addressed by the content team in their own way as well.

Please let me know if I missed anything and if it looks good, I will reach out to CAIA to take a look. Thanks for all your help and work on this.

[jilladams]

I feel ok with shipping this and iterating as needed once CAIA has a chance to take a look.

• 🟢 Benefit Detail pages -- 742Qs across 176 BDs, spot-check and all have Qs (didn't look at every page) - https://pr15833-80d0prfrxp0pohhtro3rzzrlo2bjdxih.ci.cms.va.gov/admin/content/qa?title=&type=page&moderation_state=All
• 🟢 KBs - 31Qs (used to show 46), all have Qs - https://pr15833-80d0prfrxp0pohhtro3rzzrlo2bjdxih.ci.cms.va.gov/admin/content/qa?title=&type=documentation_page&moderation_state=All. Not all of these show the content block, not sure why.
• 🟢 CLPs - 86 Qs across 12 CLPs - all look legit: https://pr15833-80d0prfrxp0pohhtro3rzzrlo2bjdxih.ci.cms.va.gov/admin/content/qa?title=&type=campaign_landing_page&moderation_state=All
• ❓ Centralized Content - 11 (used to be 20) - all show questions. I think the lower number here is due to removing the CCs that didn't have any page-specific Q&As?: https://pr15833-80d0prfrxp0pohhtro3rzzrlo2bjdxih.ci.cms.va.gov/admin/content/qa?title=&type=centralized_content&moderation_state=All
• 🟢 Landing page - shows none, used to show 1 with no questions - https://pr15833-80d0prfrxp0pohhtro3rzzrlo2bjdxih.ci.cms.va.gov/admin/content/qa?title=&type=basic_landing_page&moderation_state=All. Doesn't show the content block.
• 🟢 R&S page - 0 (used to show 3, but with no questions) - https://pr15833-80d0prfrxp0pohhtro3rzzrlo2bjdxih.ci.cms.va.gov/admin/content/qa?title=&type=support_resources_detail_page&moderation_state=All
• 🟢 VAMC Detail pages - 988 Qs (used to show 903) - https://pr15833-80d0prfrxp0pohhtro3rzzrlo2bjdxih.ci.cms.va.gov/admin/content/qa?title=&type=health_care_region_detail_page&moderation_state=All

[jilladams]

@chri5tia once you get approvals we can go ahead and merge, and share the Production link to the report with CAIA for feedback (that's implied in the AC re: sending Prod link). No need to get feedback in the Tugboat.

[dsasser]

Looks great, nice work!