You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Making it possible to publish data insights with only one file, and updating the designs to assume this as the default going forward
Motivation
Having to create 2 static visualizations per DI significantly increases the overhead in giving feedback and making revisions. We want to halve this by making it so that DIs only use one square image going forward.
Update the way images are rendered in data insights
Ensure og:image is still set correctly, and the Atom feed image.
Technical notes
I think something like a preferSmall option for the Image component will be a nice way to migrate all previous DIs that have 2 images specified, while also allowing authors to only specify filename in archie going forward (filename is mandatory whereas smallFilename is optional - the other potential solution would be to change this so that validation ensures that either one or both are defined and then handle that in the Image component, but that seems more likely to leak into other parts of the site)
The text was updated successfully, but these errors were encountered:
Making it possible to publish data insights with only one file, and updating the designs to assume this as the default going forward
Motivation
Having to create 2 static visualizations per DI significantly increases the overhead in giving feedback and making revisions. We want to halve this by making it so that DIs only use one square image going forward.
Proposed scope
Figma
Must do
og:image
is still set correctly, and the Atom feed image.Technical notes
I think something like a
preferSmall
option for theImage
component will be a nice way to migrate all previous DIs that have 2 images specified, while also allowing authors to only specifyfilename
in archie going forward (filename
is mandatory whereassmallFilename
is optional - the other potential solution would be to change this so that validation ensures that either one or both are defined and then handle that in theImage
component, but that seems more likely to leak into other parts of the site)The text was updated successfully, but these errors were encountered: