Q&A: Add report in CMS for all page-specific Q&As for Content team

[wesrowe]

Description

User story

AS A Content Editor
I WANT to be able to see all the page-specific (non-reusable) Q&As in the CMS
SO THAT I can get organized to reduce dupes, confusion, etc.

Engineering notes / background

Form page could appear somewhere like: admin/content/qa and be Titled: "Page-specific Q&As".

Acceptance criteria

• Gathered column desires from Danielle/CAIA
• Made report available in CMS, with columns:
  • Page-specific Q&A Question (not the group)
  • page title of the node where Page-specific Q&A appears (as a link?)
  • link to node where the Q&A appears if possible
  • Section of the node (in order to see its Benefit hub )
• Request CAIA feedback in #sitewide-content-accessibility-ia channel using prod CMS link - migrated to Edit Q&A report workflow filter #15891

[wesrowe]

@DanielleThierryUSDSVA – @davidconlon proposed in refinement today that CAIA would find it helpful to have a report in the CMS that pulls up all the page-specific (non-reusable) Q&As in the system into a single audit view. Assuming that sounds useful to you...

• What columns/fields would need to be present to make the report useful?
• Is there an example of another report that meets similar needs?

[DanielleThierryUSDSVA]

Hi @wesrowe. Great questions. I think this would likely be useful, yes. I can't think of an example of a similar report. I think we'd want to have the benefit hub and page title or node to help categorize them and locate them on the pages.

[chri5tia]

Update 10/19/23

The implementation of non-reusable Q&A is a bit complex and inconsistent between nodes. I may end up needing to create different views for the different nodes that use this. I made a breakthrough in understanding the shape of the data that I should be able to use to finish building the view.

[chri5tia]

Update 10/24/23

This view is ready to go but only contains content on Campaign Landing Pages. I am trying to find other places where Page-specific Q&A is used.

I am still exploring the different ways that non-reusable FAQs may have been added to the site such as no via the Page-specific Q&A paragraph type, but via accordions and rich text alone.

[chri5tia]

Ride-along engineering notes that you can ignore

The only two content types that have the page-specific q&a enabled in config for the main content block are:

• page (Benefit Detail Page)
• health-care-region-detail-page

Other places, not via the main content block:

• Campaign landing pages: added to view-based report

[chri5tia]

10/25/23 Status and Points of Clarification

CAIA confirmed that a bulk of non-reusable Q&A content is in R&S. Rich text and other non-templated paragraph types were used for q&a and other content. R&S, as of 3 years ago or more, has not had the page-specific q&a enabled, only reusable.
There is not a way to generate a report for Resource & Support Q&A content because there is not a way to distinguish that type of content.

Adding page/benefit detail page content to the report.

[jilladams]

Note from sprint planning:
Because Main Content > Rich text and Main Content > Accordion group are so generic, the eng lift to find a way to report specifically on ones that were used on R&S for Q&A.

There are 81 published R&S articles: https://prod.cms.va.gov/admin/content?title=&type=support_resources_detail_page&moderation_state=All&owner=All. The baseline assumption here should likely be that CAIA needs to review all 81 for any use of paragraphs that were made into Q&As, and migrate that content into reusable Q&As. (Or: they may have a cause to make page-specific Q&As, which would be a new requirement and need to be exposed on R&S.)

[jilladams]

The outreach to CAIA should basically say:

• Here's the view
• Here's what it includes
• Here's what it doesn't include and why
• Here are the options for handling the things it doesn't include (audit of the 81 R&S)
• CC Fran and Jill

[chri5tia]

And here is the view: https://cms-80d0prfrxp0pohhtro3rzzrlo2bjdxih.ci.cms.va.gov/admin/content/qa

[jilladams]

@chri5tia I don't see any Benefit Detail Pages coming up in that view. Did you end up adding them? If so, does that just mean there are no existing Page specific Q&As on them right now?

[chri5tia]

@jilladams Hmm, I definitely thought I was seeing them during local testing. I don't see my test content coming up in the view on the tugboat so I'll see what got missed. Thanks for pointing this out!

[chri5tia]

@jilladams I pushed a fix and the environment is rebuilding. Can you evaluate the report before I reach out to CAIA? Thank you again!
#15833

[jilladams]

PR question about the UX here, with the full content blocks included: #15833 (comment)

[chri5tia]

@jilladams @thejordanwood
There are two views to look at to make a determination for which one you want to use.

https://cms-80d0prfrxp0pohhtro3rzzrlo2bjdxih.ci.cms.va.gov/admin/content/qa
Pro: Shows each individual question, looks clean and compact.
Con: The same node will be listed for each question.

https://cms-80d0prfrxp0pohhtro3rzzrlo2bjdxih.ci.cms.va.gov/admin/content/qa_group
Pro and Con: Shows the whole group of questions for each node
Con: The field rows are huge.