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
In Content Tree right now, we have a node called LayoutImage - described as :
LayoutImage is a workaround to handle pre-existing articles that were published using tags rather than images. The reason for this was that in the bodyXML, layout nodes were inside an tag, and that didn't support publishing .
I think in Spark, we do publish these as ImageSets with Images - however in the bodyxml we're publishing an <img> tag, like:
LayoutImage
In Content Tree right now, we have a node called
LayoutImage- described as :I think in Spark, we do publish these as ImageSets with Images - however in the bodyxml we're publishing an
<img>tag, like:<img alt=\"\" data-copyright=\"© AFP via Getty Images\" data-image-type=\"image\" longdesc=\"\" src=\"https://d1e00ek4ebabms.cloudfront.net/staging/14703d45-9403-445a-85cd-7c57799aac59.jpg\"/>This means that we won't be able to convert these into "proper" responsive images, and will have to keep these weird LayoutImage things.
Possible Solutions
LayoutImagein the schemaRawImage(Add RawImage support #102) using the cloudfront URLdata-imageset-idattribute so the can be migrated<ft-content>imagesets ( see "Layout" Nodes (again) #106 )