Ratna, could you give me a starting point for understanding how I would
build this into a template? Would it just be multiple ways to render the
template's content? Not unlike the Teaser which optionally may display
its various elements?
Yes, that is exactly what I want to do. (Just getting back to this.) I
have been looking at content fragments and experience fragments, too.I'm
surprised that this isn't an OOB capability. Look at everyone's web
sites, intranets anyway, for large corporations. L0 & L1 pages are
strictly links and teasers to the rich content at L2+. So, when I create
my content rich page, as an experience fragment (though I like the fact
that content fragments have models and can be saved as experience
Thank you for your answer, Peter, but Sensei isn't what I would be
looking for at all.I have pages. We are building out page components,
but we are still very page-centric as this is a "lift-and-shift"
migration of an olde Interwoven system that was very page centric -- and
very much custom page centric. The out-of-the-box (OOB) AEM teaser
component is linktitledescriptionimage (optional)We would extend that to
add PublishDate and BusinessDomain as optional display.Note that all of
the elements ...
How can I automate the creation of a Teaser component from a page (and
from other components)? I'm thinking this is actually a rendition of a
page. Is there such a concept? If not, how do I associate the Teaser
with the page?Thank you!