---
title: "Item and list partials"
manual: "Academic Profiles"
version: "main"
source: "Templates/Partials/Index.rst"
rendered: "2026-09-22T22:46:49+00:00"
---
# Item and list partials {#templates-item-and-list-partials}
The profile item and the profile list are built from small partials. An
integrator changes one aspect of them by putting one file of a few lines into
the configured partial root path, instead of copying a whole template and
maintaining it against every later correction.
The entry points stay `Profile/Item.html`,
`Profile/List/ItemList.html`, `Profile/List/Pagination.html` and
`Profile/List/AlphabetPagination.html`. The first two delegate to the
partials below, with unchanged arguments. The page navigation is a leaf that
only gained a class, and a project copy of it loses nothing. The letter
navigation gained an argument as well, `alphabetFilterLetters`; a project copy
of it keeps working and renders every letter as a link, as before - see
[the letter navigation](#templates-letter-navigation) below.
An existing copy of the item or the list body keeps working - and stops
profiting from the partials below, because a copy does not render them.
## The item {#templates-item-partials}
`Partials/Profile/Item.html` is rendered by the list, list-and-detail,
card, selected-profiles and selected-contracts elements, and by the contacts
element of `EXT:academic_contacts4pages`. It renders:
| Partial | Renders | Class |
| --- | --- | --- |
| `Profile/Item/DetailLink.html` | The address of the detail view, as text | none, it renders no element |
| `Profile/Item/Name.html` | The academic title and the names, as text | `academic-persons-item__name`, on the heading |
| `Profile/Item/Contracts.html` | The contract block, through `Profile/Contract/Item.html` | none, the list element belongs to that partial |
| `Profile/Item/Image.html` | The image, through the shared partial of `EXT:academic_base` | `academic-persons-item__image` |
### Two of them render text, not markup {#templates-item-partials-text}
`Profile/Item/Name.html` and `Profile/Item/DetailLink.html` produce
a **value**. The item hands it to `Profile/Header.html` or
`Profile/SectionHeader.html`, which put it inside their heading element -
and escape it there, once, on the way out.
An override of either therefore renders the profile values raw:
**EXT:my_sitepackage/Resources/Private/Partials/Profile/Item/Name.html**
```html
{profile.lastName}, {profile.firstName}
```
Without `` the value is escaped twice, and a name such as
`O'Neill` reaches the browser as the markup `O'Neill`, which a visitor
reads as `O'Neill`. Markup written in one of these two partials arrives as
literal text for the same reason - the heading element is what the header
partials own.
> [!WARNING]
> These two partials render unescaped text, so they are only safe where
> something else escapes them: as an argument of a partial that writes them
> into an element, which is what `Profile/Item.html` does. Never render
> one of them in an output position of a template - `{f:render(partial:
> 'Profile/Item/Name', ...)}` written into markup would emit the stored profile
> values unescaped.
Every other partial on this page renders markup and is written as any Fluid
partial is.
### Passing the detail page {#templates-item-partials-detail-page}
`Profile/Item/DetailLink.html` builds the address from
`plugin.tx_academicpersons.detailPid`, or stays on the current page for the
list-and-detail element, which shows the detail view itself.
A template that renders an item without those plugin settings passes the page
instead. A passed page wins over both branches, the list-and-detail one
included:
```html
```
## The list {#templates-list-partials}
`Partials/Profile/List/ItemList.html` renders:
| Partial | Renders | Class |
| --- | --- | --- |
| `Profile/List/ResultCount.html` | Nothing | none, it renders no element |
| `Profile/List/GroupHeader.html` | The heading above one group of a grouped list | `academic-persons-list__group-header`, on the heading |
| `Profile/List/Items.html` | The grid of items | `academic-persons-grid`, `academic-persons-grid__item` |
| `Profile/List/Pagination.html` | The page navigation | `academic-persons-list__pagination` |
| `Profile/List/EmptyState.html` | The text shown when nothing was found | `academic-persons-empty-state` |
`Profile/List/AlphabetPagination.html` is the sixth, and the one
`ItemList.html` does not render: the list template
`Templates/Profile/List.html` renders it above the list body, when
`settings.alphabetPaginationEnabled` is switched on and no profiles are
selected by hand - a manual selection ignores the letter filter. It carries
`academic-persons-list__alphabet-pagination` next to the
`alphabetical-pagination` it had.
The list template passes it `alphabetFilterLetters` next to `demand`: every
letter from `a` to `z`, mapped to whether the list holds a profile under it
(see [Which letters lead somewhere](../../Developers/Index.html#developers-letter-availability)). The partial renders
- a letter with profiles as a link, in a plain `li.page-item`;
- a letter without profiles as `li.page-item.disabled` holding a
`span.page-link` \- no link - with a `visually-hidden` "no profiles" for
assistive technology;
- the selected letter as `li.page-item.active` with
`aria-current="page"`, and as a link back to the list without a letter
\- with a `visually-hidden` "show all profiles" - only when
[the reset setting](../../Configuration/Index.html#configuration-letter-navigation) is on;
- **A-Z** as `li.page-item.active` with `aria-current="page"`
while no letter is selected.
The `