Records List Examples: six ready-made backend views for TYPO3 v14

Records List Types lets you extend the TYPO3 v14 Records module with custom view types, entirely without PHP. The obvious question is what such a view type actually looks like in practice. Records List Examples answers exactly that.

This companion extension ships six ready-to-use views that work as both template and tool: install and use them as they are, or take them as a blueprint for your own custom types.

Table of Contents  

Overview  

Records List Examples is the direct complement to Records List Types: the base extension provides the mechanism for custom view types, while the examples deliver ready-made views to go with it. Once installed, they appear in the view switcher of the TYPO3 v14 Records module.

What stands out is how little it takes to achieve this. Four of the six views reuse the built-in templates (Grid, Compact, Teaser) with different configurations; only Timeline and Catalog bring their own Fluid templates and CSS, complete with a dark mode. This illustrates the core idea: many view types need nothing more than TSconfig and a few optional assets.

Features in detail  

The six views cover typical editorial scenarios, from chronological displays to image-heavy catalogues.

This matters for maintainability: the two custom templates (Timeline, Catalog) follow the base extension's template conventions closely – shared partials, the same sanitise logic for TYPO3 backend fragments, the native <typo3-backend-contextual-record-edit-trigger> element, and permission-aware rendering of actions. As a result, they keep working as Records List Types evolves.

That is also why the extension ships no custom JavaScript: interactive behaviour – actions, visibility toggles, pagination, multiple selection – comes from the base extension and the TYPO3 core. The templates rely on the documented data-gridview-action attributes and Fluid ViewHelpers. All labels are translatable via XLIFF 2.0 (English and German).

Installation  

Because Composer does not inherit repository definitions from dependencies, you need to add both VCS repositories to the project's composer.json. The base extension is then installed automatically.

composer config repositories.records-list-types vcs https://github.com/dirnbauer/typo3-records-list-types.git
composer config repositories.records-list-examples vcs https://github.com/dirnbauer/typo3-records-list-examples.git
composer require webconsulting/records-list-examples:^1.0

After setup, the six new view types appear in the switcher under Content → Records.

Customisation  

By default, all six views are available everywhere. With Page TSconfig you can restrict them per page tree – for example, allowing only the Timeline on the events page.

# Only Timeline on the events page
[page["uid"] == 42]
  mod.web_list.viewMode.allowed = list,timeline
  mod.web_list.viewMode.default = timeline
[end]

# Only Catalog in the shop page tree
[page["uid"] == 100 || page["pid"] == 100]
  mod.web_list.viewMode.allowed = list,catalog
  mod.web_list.viewMode.default = catalog
[end]

Frequently Asked Questions  

Conclusion  

Records List Examples is two things at once: a practical toolkit of six ready-to-use views, and a clear demonstration of how little effort a custom view type in the Records module really takes. If you already use Records List Types, this is the quickest way in – and a clean template to adapt to your own requirements.

We cover the technical foundations – the Records module, custom view types and zero-PHP extensibility – in detail in the article on Records List Types.