-
Notifications
You must be signed in to change notification settings - Fork 70
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CLP Q&A accordion display #18322
Comments
@davidmpickett @aklausmeier This seems like something that would be nice to make consistent, although not a quarterly goal. Tossing it your way for opinions/possible UX love. cc @mmiddaugh |
I feel like @thejordanwood has put some previous thought behind this in previous ticket comments #14443 and possible not all of her work was implemented. Might be good for her to take a look. |
To better understand the specific question, it would be helpful to have an example of a page with the mixed use case. Do we know of one that exists? Some things that make this question gnarly:
Reusable Q&As
flowchart TD
paragraphq_a_group>"Reusable Q&A Group<br>paragraph"]
nodeq_a(("Reusable Q&A<br>node"))
paragraphq_a_group -->|"q_as"|nodeq_a
nodecampaign_landing_page(("Campaign Landing Page<br>node"))
nodecampaign_landing_page -->|"clp_reusable_q_a"|paragraphq_a_group
nodefaq_multiple_q_a(("FAQ page<br>node"))
nodefaq_multiple_q_a -->|"q_a_groups"|paragraphq_a_group
nodepage(("Benefits Detail Page<br>node"))
nodepage -->|"content_block"|paragraphq_a_group
nodesupport_resources_detail_page(("Resources and Support Detail Page<br>node"))
nodesupport_resources_detail_page -->|"content_block"|paragraphq_a_group
style nodeq_a fill:#ffaacc,stroke:#333,stroke-width:4px;
flowchart LR
subgraph "Legend"
node(("Node"))
paragraph>"Paragraph"]
end
Single page Q&As
flowchart TD
paragraphq_a>"Page-Specific Q&A<br>paragraph"]
nodecampaign_landing_page(("Campaign Landing Page<br>node"))
nodecampaign_landing_page -->|"clp_faq_paragraphs"|paragraphq_a
nodehealth_care_region_detail_page(("VAMC Detail Page<br>node"))
nodehealth_care_region_detail_page -->|"featured_content"|paragraphq_a
nodepage(("Benefits Detail Page<br>node"))
nodepage -->|"featured_content"|paragraphq_a
paragraphq_a_section>"Page-Specific Q&A Group<br>paragraph"]
paragraphq_a_section -->|"questions"|paragraphq_a
nodedocumentation_page(("CMS Knowledge Base Article<br>node"))
nodedocumentation_page -->|"content_block"|paragraphq_a_section
nodehealth_care_region_detail_page -->|"content_block"|paragraphq_a_section
nodepage -->|"content_block"|paragraphq_a_section
style paragraphq_a fill:#ffaacc,stroke:#333,stroke-width:4px;
flowchart LR
subgraph "Legend"
node(("Node"))
paragraph>"Paragraph"]
end
|
Most of my thinking has been done around the Drupal experience of reusable v page-specific Q&As (Figma design for context). At the time I was working on the Drupal designs, it was discussed that both Q&As would appear the same on the FE to keep everything consistent. Although, we never talked through every scenario. I also didn't change the page-specific Q&A design very much because, as Dave said, Q&As get complex within Drupal. Considerations:
|
Status
[2024-07-25] [Fran] Comment to Amanda K and Dave P asking if this needs some UX love, and possible prioritization later on, although it's not a quarterly goal. Awaiting feedback label applied.
Description
While working on a different Q&A ticket Randi pointed out that Page specific Q&As are always displayed in accordions and Reusable Q&As can be displayed either in accordions or not. When these are combined, this is a bit odd. It would probably make more sense to always display these consistently when combined.
Questions to answer
Acceptance Criteria
The text was updated successfully, but these errors were encountered: