Open TroyA6 opened 1 year ago
Existing article here: https://prod.cms.va.gov/help/how-to-upload-images
Feedback from Dave C:
I don't think this article is sufficient. The way to do images in Drupal is different specifically because we want folks to understand that one image can have different aspect ratios and that you should upload high-res images and specify the aspect ratios/focuses by doing that as part of the upload process. Like: Before you begin: Will your image be mostly used horizontal or vertical? Is your image high-resolution? Does your image have no text in it? Steps: Upload image Edit the aspect ratio for 1:1 Edit aspect ratio for 2:1 (or whatever) Edit the aspect ratio for 4:3 (or whatever) etc because they should edit every single one of these because they can be reused!
Oooh, we should also start with "Have you checked to see if this image isn't already part of the library?" Arguably, we may want to consider breaking apart the image workflow away from the inline editor to get folks to think about re-usable assets. So that we encourage folks to "upload your images" separated from "build your page". Then, when we talk about "choose your image" in other areas of the CMS, we can tell them "the image you choose will use X aspect ratio.
Then, when building a page "Before you begin" -> Have you added all of the images you will use to the CMS on this page?
The issue we face, is that Editors only begin to understand the decisions necessary to make (above) after seeing an image they have produced.... show elsewhere on the site. After it "breaks".
What I mean by this is common when an Editor is using content type Story. When they add an image they are prompted to make ratio-decisions. This is a good thing. However they really have no idea what to do about that step.
So they choose something familiar, like 4:3 and move on, save, etc.
Later, when viewing their Facility(s) home page, they see the Story Teaser with image, and there, it is cropped off (typically the left and right edges are trimmed off.
It is here that they become frustrated and ask the CMS Help Desk to "fix" the issue.
Preview during the process of uploading the image, is insufficient (to the Editor) if it only displays one eventual implementation example.
Cross-linking a Discussion thread is DSVA Slack @TroyA6 https://dsva.slack.com/archives/CT4GZBM8F/p1706125756100029
Background context
What is the request for?
Create a Knowledge Base Article for training/reference: how and where to use photos within the CMS.
This KBA should describe
Person and team of requester:
Priority or deadline for request
Choose either Deadline or a priority:
Is the article associated with an ongoing product or feature update?
If requesting a new article:
Audience: Who is this intended for? Who would need this information? (i.e. All editors, only editors for a particular product, Internal use only, etc.)
Related KB articles, if applicable:
Any other relevant documentation, if applicable:
Process
Acceptance Criteria