Download the PHP package gedankenfolger/gedankenfolger-event without Composer

TYPO3 Extension Gedankenfolger Event
(gedankenfolger-event)

Compact event management extension using Content Blocks (Record Types + Content Elements), Site Set, Bootstrap CSS/SCSS, and vanilla JS. Requires TYPO3 14.

First of all many thanks to the hole TYPO3 community, all supporters of TYPO3. Especially to TYPO3-Team and Gedankenfolger GmbH.

TYPO3 13 support is maintained on the 13.x branch.

Contents of this file

1. Features
2. Install
3. Usage
4. Options
5. Template Overrides
6. Changelog
7. Acknowledgements
8. Notes
9. Notice on Logo / Trademark Use

Features:

1. Event record type with fields for title, dates (from/to), location, hall, stand, floor, image, teaser, rich text description, and an optional link
2. Three event categories: Fairs, Conferences, and Webinars with conditional fields (hall/stand/floor for fairs)
3. Event content element: select events from a storage folder with category filtering
4. Multiple layout options: List, Grid (2-column), Grid (3-column), and Grid (4-column)
5. Optional dynamic filter bar (month/day navigation, search, category filter) — disabled by default for a simple, static output
6. Optional ICS download ("Add to calendar") per event
7. Bootstrap CSS/SCSS integration with flexible loading options

Install

1. Require via Composer

Activate the extension in the TYPO3 backend (Extensions module) if not done automatically.

2. Include TypoScript via Site Set

Add the set to your site configuration:

3. (Optional) SCSS compilation

Only required when GedankenfolgerEvent.cssmode is set to scss_bootstrap, see Options below.

Usage

1. Create event records under the record type "Event" in a storage folder (sysfolder).
2. Fill in the event details:
   • Title: Name of the event
   • Date from/to: Event duration
   • Location: Where the event takes place
   • Category: Choose between Fairs, Conferences, or Webinar
   • Hall/Stand/Floor: Additional fields for fairs
   • Image: Event image (jpg, jpeg, png, webp)
   • Teaser: Short description
   • Description: Full rich text description
   • Link: Optional link, rendered as a "More information" button
3. Insert the "Event" content element on your page.
4. Select the storage folder containing your events via "Events folder".
5. Configure display options (layout, category filter, etc.).

Options

Content Element Options

• Events folder: Select the sysfolder containing your event records.
• Category filter: Show all events or filter by specific category (Fairs, Conferences, Webinar).
• Layout: Choose between List, Grid (2 columns), Grid (3 columns), or Grid (4 columns).
• Enable filters: When enabled, shows the month/day navigation, search field, and category filter bar above the events. Disabled by default — a simple static list/grid is shown without this bar.
• ICS download: When enabled, shows an "Add to calendar" link on each event card.

Site Set Settings

Configure in your site settings (config/sites/[yoursite]/settings.yaml):

• GedankenfolgerEvent.cssmode: Controls which CSS is loaded. Possible values:
  • none (default): No CSS is loaded by the extension. Use this when your sitepackage already loads Bootstrap.
  • css_bootstrap: Load pre-compiled Bootstrap + event CSS. No additional extensions required.
  • scss_bootstrap: Compile Bootstrap + event SCSS on the fly. Requires EXT:ws_scss.

Event Categories

• Fairs: Trade shows and exhibitions with additional fields for hall, stand, and floor.
• Conferences: Professional conferences and symposiums.
• Webinar: Online events and webinars.

Template Overrides

The template can be overridden from your site package without modifying the extension.

Template override

Set templateRootPaths.100 directly in your sitepackage TypoScript, pointing to a directory that contains your own frontend.html. Content Blocks resolves template root paths by descending index, so index 100 is checked before the extension's own index 20 — if your frontend.html exists there, it is used; otherwise the extension default applies.

Available template:

• frontend.html – main content element template

Note: file = EXT:... has no effect for Content Blocks v2 content elements — templateName and templateRootPaths are always set by Content Blocks itself, and FluidTemplateContentObject only evaluates file when neither is present.

Changelog

See git-cliff from Conventional Commits.

Acknowledgements

This extension builds on the following open source projects:

• TYPO3 Content Blocks
• Bootstrap Framework
• SASS Compiler for TYPO3

Notes

• Events are stored as custom records in the table tx_gedankenfolger_event.
• The extension uses Content Blocks for easy customization and extension.
• Date formatting and display can be customized via Fluid templates.
• Images support common web formats: jpg, jpeg, png, and webp.

Notice on Logo / Trademark Use

The logo used in this extension is protected by copyright and, where applicable, trademark law and remains the exclusive property of Gedankenfolger GmbH. Use of the logo is only permitted in the form provided here. Any changes, modifications, or adaptations of the logo, as well as its use in other projects, applications, or contexts, require the prior written consent of Gedankenfolger GmbH. In forks, derivatives, or further developments of this extension, the logo may only be used if explicit consent has been granted by Gedankenfolger GmbH. Otherwise, the logo must be removed or replaced with an own, non-protected logo. All other logos and icons bundled with this extension are either subject to the TYPO3 licensing terms (The MIT License (MIT), see https://typo3.org) or are in the public domain. For full license terms covering all graphic assets, see LICENSE-ICONS.