Skip to content
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

Design: FE for story page using more than one image #16890

Open
mmiddaugh opened this issue Jan 17, 2024 · 0 comments
Open

Design: FE for story page using more than one image #16890

mmiddaugh opened this issue Jan 17, 2024 · 0 comments
Labels
CY24-Q2 Calendar year Q2 2024 priority Design CMS team practice area Events product maintained by Public Websites team Facilities Facilities products (VAMC, Vet Center, etc) sitewide Story CMS managed product owned by Facilities team UX VAMC CMS managed product owned by Facilities team

Comments

@mmiddaugh
Copy link
Contributor

mmiddaugh commented Jan 17, 2024

Issue Description

VAMC editors can add a single image to stories. Images are not required but are displayed in the Story list if included. The Secretary has emphasized storytelling, supported by photos and videos and VAMC editors frequently request the ability to add more than one image to stories.

Problem(s) to solve

  • How might we enable use of more than one image for VAMC stories while ensuring an accessible and equitable experience for all Veterans?
    • Note: The editorial experience for embedding photos into stories is not ideal and likely needs a comprehensive review and improvement. Does it need to be done before we can enable additional photo use? Related: Enhance editorial experience for embedding photos into stories IRIS Q&As: Batch 4, Family member benefits va.gov-team#13906
    • Amanda and Danielle (see comment on #15718) recommend a special pilot experiment to test capability for support of one main image and one small supporting image on VAMC Events and Stories only. This pilot would be monitored closely for issues/feedback and could be turned off if problems are discovered. This issue covers the design piece only - separate issues will handle editor guidance, investigation of Drupal for options to address file size compression and support for alt text

Tasks

  • Review selection of VAMC story pages on front end to understand common uses and implications of cropping

  • Consider impact/change and update design (as necessary) for (1) individual VAMC stories, (2) story lists, and (3) featured stories considering the following
    • Stories will be limited to one main image and one small supporting image
    • Images are optional
    • Images have a caption
    • Editors may choose to use one or more than one image for a given story page
    • What is the experience on the story page if if more than one image has been specified? How does the experience compare to a story which specifies only one image?
    • What is the experience on the story listing page if more than one image has been specified for a given story?
    • What is the experience for a featured story if more than one image has been specified?

Note: we'll also need to view and design the editorial experience - this likely needs a separate issue

@mmiddaugh mmiddaugh added Events product maintained by Public Websites team Facilities Facilities products (VAMC, Vet Center, etc) Story CMS managed product owned by Facilities team UX VAMC CMS managed product owned by Facilities team labels Jan 17, 2024
@xiongjaneg xiongjaneg changed the title Design: FE for story and event page using more than one image Design: FE for story page using more than one image Feb 15, 2024
@davidmpickett davidmpickett added the Design CMS team practice area label Apr 4, 2024
@davidmpickett davidmpickett added the CY24-Q2 Calendar year Q2 2024 priority label Apr 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
CY24-Q2 Calendar year Q2 2024 priority Design CMS team practice area Events product maintained by Public Websites team Facilities Facilities products (VAMC, Vet Center, etc) sitewide Story CMS managed product owned by Facilities team UX VAMC CMS managed product owned by Facilities team
Projects
None yet
Development

No branches or pull requests

3 participants