PHPackages                             rkw/rkw-newsletter - PHPackages - PHPackages  [Skip to content](#main-content)[PHPackages](/)[Directory](/)[Categories](/categories)[Trending](/trending)[Leaderboard](/leaderboard)[Changelog](/changelog)[Analyze](/analyze)[Collections](/collections)[Log in](/login)[Sign up](/register)

1. [Directory](/)
2. /
3. [Utility &amp; Helpers](/categories/utility)
4. /
5. rkw/rkw-newsletter

ActiveTypo3-cms-extension[Utility &amp; Helpers](/categories/utility)

rkw/rkw-newsletter
==================

Extension for editing and sending newsletters

v10.4.10-stable(1mo ago)04081GPL-2.0+PHPPHP &gt;=7.4

Since Nov 28Pushed 1mo ago1 watchersCompare

[ Source](https://github.com/RKWKomZe/RkwNewsletter)[ Packagist](https://packagist.org/packages/rkw/rkw-newsletter)[ Docs](https://www.rkw-kompetenzzentrum.de)[ RSS](/packages/rkw-rkw-newsletter/feed)WikiDiscussions master Synced yesterday

READMEChangelogDependencies (10)Versions (124)Used By (0)

rkw\_newsletter
===============

[](#rkw_newsletter)

Features
--------

[](#features)

Extension for sending newsletters. Each newsletter can contain several topics, which can be freely selected by the subscribers. In the dispatch process, each subscriber then receives only the topics that he or she has chosen.

Special issues can be created.

Structure and process
---------------------

[](#structure-and-process)

Editors can mark content in the backend as relevant for the newsletter. It is then automatically collected and copied into the editorial template a few days before the send date, reducing the editor's workload for the newsletter.

A folder ("issue-folder") must be created for each newsletter topic. Here the extention creates a new page a few days before the dispatch date and collects the marked contents there. Using appropriate roles and approval processes, each topic can be prepared accordingly.

Each newsletter can have a general editorial that is sent to those who have subscribed to more than one topic. In addition, each topic can have an editorial that is used only when a person subscribes to that topic only.

The extension includes a multi-step approval process. A timed release can be set on the lower release levels.

In the dispatch process, each subscribing person then receives only the topics that he or she has selected. In the process, the topics are zipped together while maintaining the order selected by the editor.

Setup
-----

[](#setup)

- Create a newsletter record with corresponding topics.
- A folder has to be created in the backend for each topic. The issues per topic will be generated into this.
- There is a backend layout for editing the newsletter articles, which can be set via page configuration of the issue-folders.
- A cronjob must be created for the time-controlled creation of the issues, the approval process and the dispatch process.

Status of editing: 2022-05-10

###  Health Score

52

—

FairBetter than 96% of packages

Maintenance90

Actively maintained with recent releases

Popularity14

Limited adoption so far

Community13

Small or concentrated contributor base

Maturity78

Established project with proven stability

 Bus Factor1

Top contributor holds 73.2% of commits — single point of failure

How is this calculated?**Maintenance (25%)** — Last commit recency, latest release date, and issue-to-star ratio. Uses a 2-year decay window.

**Popularity (30%)** — Total and monthly downloads, GitHub stars, and forks. Logarithmic scaling prevents top-heavy scores.

**Community (15%)** — Contributors, dependents, forks, watchers, and maintainers. Measures real ecosystem engagement.

**Maturity (30%)** — Project age, version count, PHP version support, and release stability.

###  Release Activity

Cadence

Every ~22 days

Recently: every ~87 days

Total

118

Last Release

47d ago

Major Versions

v7.6.35-beta → v8.7.0-beta2019-11-12

v8.7.70-beta → v9.5.0-beta2022-04-25

v8.5.7-beta → v9.5.8-beta2022-05-02

v8.7.73-beta → v9.5.24-stable2023-03-24

v9.5.1001-stable → v10.4.0-stable2024-04-19

PHP version history (2 changes)v7.6.3-betaPHP &gt;=5.6

v9.5.20-stablePHP &gt;=7.4

### Community

Maintainers

![](https://www.gravatar.com/avatar/ca11ace9490b8fe0b145e7d32464fba5c8eddaa88d700b95d32241a226623e76?d=identicon)[SteffenKroggel](/maintainers/SteffenKroggel)

---

Top Contributors

[![skroggel](https://avatars.githubusercontent.com/u/8121847?v=4)](https://github.com/skroggel "skroggel (270 commits)")[![addorange](https://avatars.githubusercontent.com/u/1980618?v=4)](https://github.com/addorange "addorange (72 commits)")[![MaxFaessler](https://avatars.githubusercontent.com/u/45080955?v=4)](https://github.com/MaxFaessler "MaxFaessler (25 commits)")[![Melanie2508](https://avatars.githubusercontent.com/u/78857863?v=4)](https://github.com/Melanie2508 "Melanie2508 (2 commits)")

---

Tags

TYPO3 CMSnewsletterRKW

### Embed Badge

![Health badge](/badges/rkw-rkw-newsletter/health.svg)

```
[![Health](https://phpackages.com/badges/rkw-rkw-newsletter/health.svg)](https://phpackages.com/packages/rkw-rkw-newsletter)
```

###  Alternatives

[derhansen/sf_event_mgt

Configurable event management and registration extension based on ExtBase and Fluid

64313.9k6](/packages/derhansen-sf-event-mgt)[brotkrueml/schema

Embedding schema.org vocabulary - API and view helpers for schema.org markup

33584.6k13](/packages/brotkrueml-schema)[causal/extractor

This extension detects and extracts metadata (EXIF / IPTC / XMP / ...) from potentially thousand different file types (such as MS Word/Powerpoint/Excel documents, PDF and images) and bring them automatically and natively to TYPO3 when uploading assets. Works with built-in PHP functions but takes advantage of Apache Tika and other external tools for enhanced metadata extraction.

16244.5k](/packages/causal-extractor)[jweiland/events2

Events 2 - Create single and recurring events

2062.4k2](/packages/jweiland-events2)[mfd/ai-filemetadata

Automatically generates FAL metadata for files by means of public LLMs

1142.1k](/packages/mfd-ai-filemetadata)

PHPackages © 2026

[Directory](/)[Categories](/categories)[Trending](/trending)[Changelog](/changelog)[Analyze](/analyze)
