fgtclb/academic-partners-partnerships-teaser, which the aggregate set
fgtclb/academic-partners includes, see What the sets contain
The Partner Logo Teaser shows the same partners as
Partners Linked: the partnerships of the
page it is stored on, grouped by role, in the order the editor arranged them, and
the partners without a role after the groups. It is meant for a strip of partner
logos on the page of a project or a faculty, for example in a sidebar or above
the footer, while the full list of the partnerships is shown elsewhere. There
is no selection in the content element.
What it renders
The output is the one of Partners Linked, card for card: the name
of the partner linked to its page, its categories and the first image of the
partner page. Only the outermost element differs, it carries the class
academic-partnerships-teaser instead of academic-partnerships-list. That
the teaser shows logos, and only logos, is up to the stylesheet of the site,
which for example hides the name and the categories inside
academic-partnerships-teaser. See The partnerships list and teaser and
The outermost elements.
A site that wants different markup for the teaser, only the image of each
partner for example, overrides the partial of the teaser,
Partials/Partnerships/Teaser/Item.html. It renders one card of the
teaser and nothing else, so Partners Linked, which renders
Partials/Partnerships/List/Item.html, stays as it is.
The Partner Logo Teaser as it renders without a stylesheet of its own: the
same cards as Partners Linked.
Everything said about the partnerships on the page of
Partners Linked applies here as well: where
the partnerships come from, the grouping by role, and the partners without a
role, or with a hidden or deleted role, after the role groups.
Settings
The content element has no options of its own: it has no FlexForm and no
Configuration tab. What it shows is decided by the partnerships of
its page.
Reference to the headline
Copy and freely share the link
This link target has no permanent anchor assigned. You can make a pull request on GitHub to suggest an anchor.
The link below can be used, but is prone to change if the page gets moved.
