VAMC front end templates use a very small thumbnail (2_1_medium_thumbnail) which should probably be 2_1_large.
This feedback provided by Ryan Stubblebein at Pittsburgh.
The imagery associated with stories featured on VAMc pages is as important to Veteran readers as the content itself.
Content editors can apply cropping ratios (2:1, 3:2, 7:2, Freeform, Original, and Square) and select the portion of the image to be included in the crop. However, regardless of the ratio and location selected, the system auto-applies the 2:1 ratio from the center of the image. Staff photographers and public affairs specialists have a difficult time trying to capture images in the ratios provided and pictures are often submitted from employees without training or experience to gain quality shots. This is occurring with more frequency due to the pandemic and telework.
In addition to the cropping issues, the imagery on the final output to the web is severely degraded compared to the originals. This causes the images to appear as though they are slightly “zoomed in on,” and causes them to be blurry and unattractive. I am including a link to the most recent story we put into review, as it showcases the limitations of the cropping (vertical picture CANNOT be used) as well as the image quality issues.
Tasks
[ ] What work is necessary for this story to be completed?
Acceptance Criteria
[ ] What will be created or happen as a result of this story?
How to configure this issue
[ ] Attached to a Milestone (when will this be completed?)
[ ] Attached to an Epic (what body of work is this a part of?)
[ ] Labeled with Team (product support, analytics-insights, operations, service-design, tools-be, tools-fe)
[ ] Labeled with Practice Area (backend, frontend, devops, design, research, product, ia, qa, analytics, contact center, research, accessibility, content)
[ ] Labeled with Type (bug, request, discovery, documentation, etc.)
Issue Description
VAMC front end templates use a very small thumbnail (2_1_medium_thumbnail) which should probably be 2_1_large.
This feedback provided by Ryan Stubblebein at Pittsburgh.
The imagery associated with stories featured on VAMc pages is as important to Veteran readers as the content itself.
Content editors can apply cropping ratios (2:1, 3:2, 7:2, Freeform, Original, and Square) and select the portion of the image to be included in the crop. However, regardless of the ratio and location selected, the system auto-applies the 2:1 ratio from the center of the image. Staff photographers and public affairs specialists have a difficult time trying to capture images in the ratios provided and pictures are often submitted from employees without training or experience to gain quality shots. This is occurring with more frequency due to the pandemic and telework.
In addition to the cropping issues, the imagery on the final output to the web is severely degraded compared to the originals. This causes the images to appear as though they are slightly “zoomed in on,” and causes them to be blurry and unattractive. I am including a link to the most recent story we put into review, as it showcases the limitations of the cropping (vertical picture CANNOT be used) as well as the image quality issues.
Tasks
Acceptance Criteria
[ ] What will be created or happen as a result of this story?
How to configure this issue
product support
,analytics-insights
,operations
,service-design
,tools-be
,tools-fe
)backend
,frontend
,devops
,design
,research
,product
,ia
,qa
,analytics
,contact center
,research
,accessibility
,content
)bug
,request
,discovery
,documentation
, etc.)