---
title: "General configuration"
manual: "Academic Bite Jobs"
version: "2.4"
permalink: "https://docs.typo3.org/permalink/fgtclb/academic-bite-jobs:configuration-general@2.4"
source: "Configuration/General/Index.rst"
rendered: "2026-10-26T16:43:50+00:00"
---

# General configuration {#configuration-general}

## The view of the job list {#configuration-general-view}

The plugin settings of a **Job list** content element select one of
three views: **List**, **Card** or **Table**. The stored
values are `List`, `Card` and `Table`.

Content elements saved with version 2.0 store `ListView`, `CardView` or
`TableView`. They render the corresponding view, and a content element with an
empty or unknown value renders the list view. Templates always receive the
normalised value in `{settings.jobs.view}`.

The upgrade wizard `academicBiteJobs_listViewFlexFormUpgradeWizard` rewrites the
stored values of existing content elements, so their backend form shows the view
the frontend renders.

## Grouping the jobs {#configuration-general-group-by}

The job list renders the jobs ungrouped. To group them, name a field of the job
postings in TypoScript:

**TypoScript setup**

```typoscript
plugin.tx_academicbitejobs.settings.jobs.groupBy = department
```

The list then renders one group per value of that field, headed by the value,
and every job title one heading level below the group heading. The field has to
be part of the job postings, either as the B-ITE API answers them for the job
listing key of the content element, or written into them by an event listener,
see [Example: a custom field filter and a grouping](https://docs.typo3.org/permalink/fgtclb/academic-bite-jobs:developers-example@2.4). It is not offered in the plugin settings. An
empty value, or `none`, switches the grouping off again.

A content element saved before version 2.1 may still store a grouping setting of
its own, which wins over the TypoScript. The upgrade wizard
`academicBiteJobs_listViewFlexFormUpgradeWizard` removes it.

## The header of the content element {#configuration-general-content-element-header}

The header and the subheader an editor enters on a **Job list**
content element are rendered by the content element layout of the site, as for
any other content element. The layouts of **EXT:fluid_styled_content**
and of the bootstrap package do that, and the plugin renders no header of its
own.

A site whose content element layout renders no header, because its element
templates render it instead, lets the plugin render it:

**TypoScript constants**

```typoscript
plugin.tx_academicbitejobs.renderContentElementHeader = 1
```

The template then renders the header partial of
**EXT:fluid_styled_content** above the jobs, so the switch needs that
extension installed; this extension does not require it. Do not switch it on
where the layout renders the header: the header then appears twice.

For the header layout **Default**, the partial takes the heading level
from `plugin.tx_academicbitejobs.settings.defaultHeaderType`, which
is mapped from the constant `styles.content.defaultHeaderType` of
**EXT:fluid_styled_content**. A site that does not include the
TypoScript of **EXT:fluid_styled_content** sets the setting itself;
without it, such a header renders as an empty `<header>` element.