[MGNLSTK-457] Drop teaser image selection from page dialog Created: 23/Sep/09  Updated: 23/Jan/13  Resolved: 08/Nov/09

Status: Closed
Project: Magnolia Standard Templating Kit (closed)
Component/s: None
Affects Version/s: None
Fix Version/s: 1.2

Type: Improvement Priority: Major
Reporter: Boris Kraft Assignee: Philipp Bärfuss
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
relation
is related to MGNLSTK-466 Page Intro + Image Closed
Template:
Acceptance criteria:
Empty
Date of First Response:

 Description   

As discussed a long time ago on the me-list:

I would like to remove the teaser image definition from the page info
dialog. Instead I propose to simply use the first image found in the
main section as the teaser image. I believe this would improve
usability and reduce complexity.

  • if you have images in an article / event / glossary item / news, the
    first image is probably the one that is most relevant to the article
    and hence useful as a teaser image
  • if you have no image (for a news maybe?) you probably don't want to
    tease using a contrived image that is only used for the teaser, so its
    ok to use no image at all.
  • if you don't like the image to be used in the teaser or really want
    one even though the teased page doesn't show one, you can still
    overwrite it from the teaser paragraph

From my own experience in building the new demo site I can say that
it is foremost confusing when the teaser image doesn't match the image
in the article, and it is additional and rather needless work.

Now, there may be cases where you really need a specific teaser image
which actually is used in more than one or two locations, in which
case it might actually make sense to have that teaser image assigned
to the article instead of selecting it manually from the DMS for each
teaser - but I reckon this is rare enough to either do it (manually)
or - in that specific case) - add the feature to a custom page info
dialog.

As a new and further idea, we could later allow to select a teaser image from any image found within the content f the teased page, much like Facebook allows you to scroll through images found from a "shared" web page. (that would be a nifty new control)



 Comments   
Comment by Christian Ringele [ 25/Sep/09 ]

There is only one case where i see a use of it:

Building upon the idea of auto generated teasers.
For example:
A 'special' section page which automatically generates a teaser pointing to all sub pages.
This use case we have in Scottish Widows. Of course the teasers can be added manually.
But it's just cumbersome to as a sub page to a section, and after that adding a page having to add into the section page a teaser pointing to the child.
I think the RTR has a very similar use case with the auto generates news pages form the external news system.
When creating a news page by automatism, the parent section must show it as a teaser.

So in these scenarios the only way to provide to a automatic generated teaser a image is over the target page itself.
The target page has to define in this case what image is shown if somebody points to me.
(Of course only if the page itself does not contain any image).

Comment by Boris Kraft [ 25/Sep/09 ]

Well, yes, but that's exactly what we have defined - we simply take the first image found in the target page's content. No problem creating "automatic" teaser sections or list of pages or whatever.

Comment by Christian Ringele [ 28/Sep/09 ]

All I wrote is regarding to the case:

  • The target page as no image in it's content/mainArea at all.
    For example: automatic generated short news (RTR), articles just containing no images (Guides in Scottish Widows).
  • On the parent section page, teasers pointing to its children pages are automatically generated.
    For example: Always for the last 8 shot news a teaser is generated. But there are over 200 short News. Each news need still to define it's image -> teaserOverwrite is no option for supplying the image.

In this scenario (and only in this), an image definition on 'page info' level would make sense.

Comment by Christian Ringele [ 30/Sep/09 ]

If you think these are corner cases, no problem.
I have just seen this need in two of three projects i was involved in.
So i thought these are probably not that seldom cases.

Generated at Mon Feb 12 07:27:13 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.