Display gleaning teasers in the same format as other content types

joshua_davis commented

2019-10-01 14:20:41 +00:00

(Migrated from gitlab.com)

Background

The cards for gleanings are showing images on the bottom and title on the top, rather than vice versa like all the other ones.

Work Required

Configure the Gleaning teaser to match the Article teaser (ie: image on top, title below)

## Background The cards for gleanings are showing images on the bottom and title on the top, rather than vice versa like all the other ones. ## Work Required * [x] Configure the Gleaning teaser to match the Article teaser (ie: image on top, title below)

cedewey commented

2019-10-01 14:38:47 +00:00

(Migrated from gitlab.com)

changed title from {-Gleaning cards on landing page are wonky-} to {+Display gleaning teasers in the same format as other content types+}

changed title from **{-Gleaning cards on landing page are wonky-}** to **{+Display gleaning teasers in the same format as other content types+}**

cedewey commented

2019-10-01 14:38:47 +00:00

(Migrated from gitlab.com)

changed the description

cedewey commented

2019-10-01 14:38:49 +00:00

(Migrated from gitlab.com)

assigned to @cedewey

cedewey commented

2019-10-01 15:10:12 +00:00

(Migrated from gitlab.com)

assigned to @mlncn and unassigned @cedewey

mlncn commented

2019-10-01 22:28:56 +00:00

(Migrated from gitlab.com)

marked the checklist item Configure the Gleaning teaser to match the Article teaser (ie: image on top, title below) as completed

marked the checklist item **Configure the Gleaning teaser to match the Article teaser (ie: image on top, title below)** as completed

mlncn commented

2019-10-01 22:53:29 +00:00

(Migrated from gitlab.com)

@cedewey I think this is as good as it can get, with the current differences in what data the sites actually have.

It's using the inserted image for gleanings and it should be tested to ensure that it can pick this up for new gleanings (there's no separate image field for gleanings as for other content types).

Or i guess the issue is more that the field is called Insert an image into the text but we built zero functionality to actually do that. And it would be a different user experience from any other content type if we built it. The rationale though if i can recall is that it be optional to display this image in the text, and that it not have a huge header image like other content. But maybe we should just make it huge header image? Anyway that speculation is i guess for another issue; Gleaning display as Card display is now consistent with other Cards.

@cedewey I think this is as good as it can get, with the current differences in what data the sites actually have. It's using the inserted image for gleanings and it should be tested to ensure that it can pick this up for new gleanings (there's no separate image field for gleanings as for other content types). Or i guess the issue is more that the field is *called* **Insert an image into the text** but we built zero functionality to actually do that. And it would be a different user experience from any other content type if we built it. The rationale though if i can recall is that it be optional to display this image in the text, and that it not have a huge header image like other content. But maybe we should just make it huge header image? Anyway that speculation is i guess for another issue; Gleaning display as Card display is now consistent with other Cards.

mlncn commented

2019-10-02 16:18:12 +00:00

(Migrated from gitlab.com)

assigned to @cedewey

mlncn commented

2019-10-03 08:08:32 +00:00

(Migrated from gitlab.com)

mentioned in issue #77