A premium drag‑and‑drop page builder + CMS for Flarum 2. Design custom pages

from blocks, run structured content types ("databases") like an articles

section or knowledge base, and edit it all visually — in the admin **or live on

the front end**. No code required.

Table of contents

• Features

• Requirements

• Installation

• Quick start

• Pages & the block designer

• The live front‑end editor

• Block reference

• Hero banners

• Content types (the CMS)

• Comments on records

• Promote a discussion to an article

• SEO

• Setting a custom homepage

• Permissions

• For developers: the block & field APIs

• License

Features

• Visual page designer — build pages from a responsive 12‑column grid of

  rows → columns → blocks, with drag‑and‑drop reordering, in the admin.

• Live WYSIWYG editor on the front end — admins get an Edit layout button

  on any Page Builder page; drag blocks around and edit their settings while

  seeing the real, rendered result.

• 15 built‑in blocks — heroes, text/HTML/images/buttons, forum widgets

  (recent & featured discussions, online users, newest members, stats, tag

  grid), content lists, and media embeds.

• Customizable hero banners — full‑width or split layouts; gradient, solid,

  or uploaded/linked image backgrounds; custom text color; one or two buttons.

• Content types (CMS) — define your own kinds of content (articles,

  downloads, a directory, a knowledge base) with custom fields, categories, and

  per‑group permissions. Records get listing pages, detail pages, and comments.

• Promote a discussion to an article in one click.

• Built‑in SEO — server‑rendered titles, meta descriptions, and Open

  Graph / Twitter cards for every page and record.

• Open block & field APIs — other extensions can register their own blocks

  and field types.

Requirements

• Flarum ^2.0

• PHP 8.1+

• Optional: flarum/tags — required only for the **Tag

  Grid** block.

Installation

php flarum migrate
php flarum cache:clear```

Then enable **Page Builder** under *Admin → Extensions*.

This is a proprietary, paid extension — see License.

---

## Quick start

1. Open **Admin → Extensions → Page Builder**.
2. Click **New page**, give it a title, and you're dropped into the designer.
3. **Add row → Add block**, pick a **Hero banner**, and edit its heading,

   background, and buttons.
4. Click **Save changes**, then **Preview**.
5. (Optional) Use the **Forum homepage** card to make your page the site's front

   page — see Setting a custom homepage.

![Page Builder admin: homepage, pages, and content types](https://raw.githubusercontent.com/ernestdefoe/page-builder/main/docs/screenshots/admin-pages.png)

---

## Pages & the block designer

A **page** lives at `/p/{slug}` (or `/` when set as the homepage) and is built

from a layout tree:

```Page
└── Row            (full‑width / wide / narrow, padding, background)
    └── Column     (1–12 of a 12‑column grid)
        └── Block  (hero, text, widget, …)```

In the designer you can:

* **Add / delete / reorder rows**, set each row's width and padding, and give it

  a background color.
* **Add / delete / reorder columns** within a row and set each column's width

  (out of 12).
* **Add / delete / reorder blocks** within and across columns.
* **Edit every block's settings** inline (the form is generated from the block's

  schema).
* Set **per‑block visibility** — which device sizes (desktop / mobile) and which

  user groups can see it.

Everything reorders by **dragging the grip handle** (☰); drop zones appear

between items as you drag.

![The admin page designer](https://raw.githubusercontent.com/ernestdefoe/page-builder/main/docs/screenshots/designer.png)

---

## The live front‑end editor

Open any Page Builder page as an admin and click **Edit layout** (bottom‑right).

The page turns into a live editor where the **real blocks render as you work**:

* Drag rows, columns, and blocks to rearrange them.
* Click the **

⚙ settings** icon on a block to edit it — changes update the live preview instantly (true WYSIWYG). * **Add block** / delete blocks per column. * Click **Save layout** to publish, or **Cancel** to discard. ![Live front‑end WYSIWYG editor](https://raw.githubusercontent.com/ernestdefoe/page-builder/main/docs/screenshots/live-editor.png) --- ## Block reference | Block | Category | What it does | |-------|----------|--------------| | **Hero banner** | content | Full‑width or split banner; gradient/solid/image background, heading, subheading, up to two buttons. See Hero banners. | | **Heading** | content | A styled heading (h1–h4), alignment. | | **Text** | content | A rich text paragraph block, alignment. | | **HTML** | content | Raw HTML, **sanitized on save** (scripts & event handlers stripped). Authoring is admin‑only. Great for embeds and custom markup. | | **Image** | media | A single image (uploaded or by URL), optional rounded corners, alignment. | | **Button** | content | A call‑to‑action button (primary/secondary), link, alignment. | | **Divider** | layout | A horizontal rule with adjustable spacing. | | **Recent Discussions** | forum | The latest discussions, visibility‑filtered. | | **Featured Discussions** | forum | Hand‑picked discussions by ID, in your chosen order, with optional excerpts. | | **Online Users** | forum | Avatars of who's online now. | | **Newest Members** | forum | The most recently joined members, with join dates. | | **Forum Stats** | forum | Member / discussion / post / online counts. | | **Content list** | content | Embeds records from a content type (e.g. latest articles) as cards. | | **Tag Grid** | forum | Forum tags as clickable cards (requires `flarum/tags`). | | **Embed** | media | A responsive YouTube/Vimeo embed from a URL, with caption. | --- ## Hero banners The **Hero banner** block (and each content type's optional **listing hero**) is fully customizable: * **Layout** — *Full‑width background* (centered or left text) or *Split* (text panel beside an image panel). * **Background** — **Gradient** (start/end colors + angle), **Solid** color, or **Image** (upload or paste a URL, with an adjustable dark overlay). * **Text** — heading, subheading, and **text color**: light, dark, or a **custom color** to match your theme. * **Buttons** — a primary and an optional secondary button (e.g. "Browse articles" + "Browse forum"). * **Height** & **alignment**. --- ## Content types (the CMS) Page Builder includes a full content‑management layer. A **content type** is your own kind of content — *Articles*, *Downloads*, a *Knowledge base*, a *Directory* — each with its own fields, categories, permissions, and URLs. ![Editing a content type](https://raw.githubusercontent.com/ernestdefoe/page-builder/main/docs/screenshots/content-type.png) **Create one** under *Page Builder → Content types → New content type*, then configure: * **Fields** — text, textarea, rich text, **markdown** (the full Flarum composer with uploads/mentions/emoji), **image** (upload or URL), number, date, boolean, select, multiselect, URL, email, color, rating, and relationship. Mark one as the **title**, and choose which appear in the list view. * **Categories** — optional taxonomy with a filter bar and badges on the listing. * **Permissions** — which groups can **view**, **submit**, and **manage** records. * **Listing hero** — an optional hero banner on the type's `/c/{type}` page. Each type gives you: * A **listing** at `/c/{type}` (cards, category filter, pagination). * A **record page** at `/c/{type}/{slug}`. * A **composer** at `/c/{type}/new` and `/c/{type}/{slug}/edit`. ![A content type's listing page with a full‑width hero](https://raw.githubusercontent.com/ernestdefoe/page-builder/main/docs/screenshots/listing-hero.png) --- ## Comments on records When enabled for a type, each published record gets a **comment thread** backed by a real Flarum discussion — so comments get mentions, reactions, notifications, and moderation for free. The thread is created lazily on first view and hidden from the normal discussion list. --- ## Promote a discussion to an article Turn any forum discussion into an article from its **controls dropdown → Promote to article** (admin only). The discussion's title becomes the article title and its first post becomes the body; the original discussion is then attached to the new article as its **comment thread** (and drops out of the forum listing). --- ## SEO Page Builder renders SEO tags **server‑side** (so crawlers and social cards see them without running JavaScript) for `/home`, `/p/{slug}`, `/c/{type}`, and `/c/{type}/{slug}`: * `<title>` and `<meta name="description">` * **Open Graph** (`og:type`, `og:title`, `og:url`, `og:description`, `og:image`) * **Twitter** card tags * `article:published_time` for records, plus a canonical URL Record descriptions come from a summary/excerpt and `og:image` from the record's cover image. Pages use the **Meta description** field you set in the designer. The tags are authoritative and de‑duplicated, so they coexist cleanly with a dedicated SEO extension. --- ## Setting a custom homepage 1. In **Page Builder → Forum homepage**, choose the page to use as your front page. 2. Go to **Admin → Basics → Home Page** and select **“Home (Page Builder)”**. Your custom page now serves as the forum's landing route (`/`), Invision‑style. --- ## Permissions * **Pages & the designer** (admin) — building pages and editing HTML blocks is admin‑only. * **Content types** — set per‑type **view / submit / manage** group permissions in the content‑type editor. * **Block visibility** — limit individual blocks to specific groups (enforced server‑side) and device sizes. --- ## For developers: the block & field APIs Register a **block** from any extension: ```// extend.php (new Ernestdefoe\PageBuilder\Extend\PageBuilderBlock(MyBlock::class)),``` ```// forum JS app.pageBuilder.registerBlock('my-block', MyBlockComponent);``` `MyBlock` extends `Ernestdefoe\PageBuilder\Block\AbstractBlock`: declare `type()/name()/icon()/category()`, a `settingsSchema()` (the same schema language the editor renders), and a `resolve($settings, $actor)` returning data **scoped to the actor's visibility**. The matching JS component receives `{ settings, data }`. Register a custom **field type** for content types via `app.pageBuilderFields.register(type, InputComponent, DisplayComponent)`. --- ## License **Proprietary © Ernest Defoe.** A premium paid extension — see [LICENSE](https://github.com/ernestdefoe/page-builder/blob/main/LICENSE) for terms. For licensing inquiries: ernestdefoe@gmail.com

Automation for your forum. Connect gives Flarum 2 outgoing webhooks, a

scoped REST API, and an in-app if-this-then-that Rules engine. Wire your

community up to Zapier, Make, IFTTT, n8n — or automate things right on the

forum with no external service at all.

Free and MIT-licensed.

What it does

Connect covers both directions of automation:

• Out of your forum → anywhere. When a discussion is started, a reply is

  posted, or a user registers, Connect fires a signed webhook to whatever URL

  you (or a Zap) subscribed. Perfect for Zapier/Make/IFTTT/n8n triggers.

• Anywhere → into your forum. A scoped API key lets an external service

  create discussions and replies as a real user, through Flarum's own API — so

  every permission and validation rule still applies.

• Inside your forum. The built-in Rules engine runs trigger → conditions

  → actions entirely on your server. No third-party account, no per-task billing,

  no data leaving the box.

Set it all up without leaving your forum

Connect embeds Zapier's official experience right in your admin panel. Browse

6,000+ apps, pick a recipe — Share new discussions to a Facebook Page, *Post to

Slack, Add members to Mailchimp* — and build or manage Zaps in place. No tab

switching, no developer knowledge required.

Paste your Zapier integration's Client ID once (Admin → Connect) and the full

experience appears, themed to match your forum. Prefer Make, n8n, or IFTTT?

They all work off the same REST API and webhooks.

Automation rules (no external service needed)

Pick a trigger, add optional conditions, and choose one or more

actions. Rules run on a queue, off the request path, so they never slow down

the person who triggered them.

Triggers

| Event | Fires when |

| --- | --- |

| discussion.created | someone starts a new discussion |

| post.created | someone posts a reply |

| user.registered | a new member signs up |

Conditions — match all or any of a list. Each condition compares a

payload field (e.g. title, content, tagList) using one of:

is, is not, contains, does not contain, starts with, is greater than,

is less than, is empty, is not empty, matches (regex).

Actions

| Action | What it does |

| --- | --- |

| Post a reply | replies to the discussion the event is about |

| Add / remove a tag | requires flarum/tags |

| Add / remove from a group | changes the involved user's groups |

| Call a webhook | POSTs the event payload to a URL you choose |

Actions are isolated — if one fails, the rest of the rule still runs — and each

rule tracks how many times it has run.

Connecting Zapier / Make / IFTTT / n8n

1. In Admin → Connect, create an API key. Give it a label (e.g. Zapier) and

   the scopes it needs — Read for triggers, Write for actions.

2. Copy the token (ck_…) and secret (cs_…).

3. In your automation tool, add a webhook that authenticates with

   Authorization: Bearer ck_….

   • To receive forum events, subscribe your tool's catch-hook URL (Zapier

     does this automatically via REST Hooks — see the API below).

   • To act on the forum, POST to the action endpoints.

Every outgoing delivery is HMAC-signed so you can verify it really came from

your forum:

valid  ⇔  signature == 'sha256=' + hmac_sha256(rawRequestBody, keySecret)```

---

## REST API

All routes are under your forum's API root (`/api`). Authenticate with

`Authorization: Bearer ck_…`.

| Method | Endpoint | Purpose |

| --- | --- | --- |

| `GET` | `/connect/me` | Who this key acts as (auth test) |

| `POST` | `/connect/hooks` | Subscribe: `{ event, targetUrl }` → REST Hook, returns `{ id }` |

| `DELETE` | `/connect/hooks/{id}` | Unsubscribe |

| `GET` | `/connect/samples/{event}` | Recent real items shaped like the payload (Zap setup) |

| `POST` | `/connect/actions/discussions` | Create a discussion `{ title, content }` |

| `POST` | `/connect/actions/posts` | Reply to a discussion `{ discussionId, content }` |

A `410 Gone` from a subscribed target auto-prunes the subscription — so a Zap you

turn off cleans itself up.

### Example

```# What does this key act as?
curl https://your-forum.example/api/connect/me \
  -H "Authorization: Bearer ck_live_xxx"

# Create a discussion as the key's user
curl -X POST https://your-forum.example/api/connect/actions/discussions \
  -H "Authorization: Bearer ck_live_xxx" \
  -H "Content-Type: application/json" \
  -d '{"title":"Posted from Zapier","content":"Hello from an automation!"}'```

---

## Installation

```composer require ernestdefoe/connect```

Then enable **Connect** in **Admin → Extensions**. Make sure a queue worker is

running (`php flarum queue:work`) so webhooks and rule actions are delivered.

The tag actions light up automatically if [flarum/tags](https://github.com/flarum/tags) is installed; everything

else works on a stock forum.

## Minting a key from the CLI

```php flarum connect:key "My key" --scopes=read,write```

---

## Requirements

* Flarum `^2.0`
* PHP `^8.3`
* A running queue worker (recommended — webhooks and rule actions are queued)

## License

[MIT](https://github.com/ernestdefoe/connect/blob/main/LICENSE) © Ernest Defoe

Migrate an existing forum into Flarum 2 — from phpBB, vBulletin (3/4/5), XenForo, MyBB, SMF, Vanilla, NodeBB, Invision, Discourse, or Convoro. Everything is driven from the admin panel: pick a platform, connect to its database (or upload a dump), test it, then run the import in small batches with a live progress bar — so even a large forum won't time out.

Ported from the Convoro importer suite. Members keep their passwords where possible (bcrypt hashes are copied straight across; other formats are randomised so the member simply resets on first login). Post bodies are converted to Flarum's native rich-text format, so BBCode / HTML / Markdown comes across as real formatting — bold, italics, links, quotes, lists and code.

Runs on shared hosting

No queue worker and no SSH required. The import runs as a loop of small "step" requests straight from your browser, each processing one bounded batch and returning — so it can never hit a web timeout. Progress and the source→Flarum id-maps are persisted in the database, so if the tab is closed or the connection drops, reopen the page and it resumes exactly where it left off. If you do have a queue worker (e.g. fof/redis), the import is handed to it and runs fully in the background instead — either way it's safe.

The admin area

The whole tool lives on the extension's settings page.

1. The wizard

Pick a source platform, then either connect to a database (host, port, database name, username, password, and table prefix) or upload a database file (a mysqldump .sql/.sql.gz, or a SQLite file) for hosts that only hand you a dump. Nothing is written until you start.

2. Test the connection

Test connection validates the credentials, confirms it really is the platform you picked, then reports exactly what it found — here 21 Users, 4 Categories, 30 Topics, 371 Posts — so you know it will pull the right data before committing. Start import only lights up once the test passes.

3. Watch it run

Start import kicks off the batched run and shows a live progress bar with the current phase and running totals — categories, members, topics and posts — updating as it goes.

When it finishes you get a summary of everything imported, and can start another.

Supported sources

| Platform | Notes |

|----------|-------|

| phpBB 3.x | BBCode posts; bcrypt passwords copied across |

| vBulletin 3 / 4 · vBulletin 5 / 6 | one option covers both — vB5's node schema is auto-detected |

| XenForo 1.x / 2.x | BBCode posts; XF2 bcrypt passwords copied |

| MyBB 1.8 · SMF 2.0 / 2.1 | BBCode posts |

| Vanilla · NodeBB | Markdown / mixed formats; NodeBB reads its Redis store (needs the redis PHP extension) |

| Invision Community (IP.Board) | HTML posts, quotes & mentions cleaned up |

| Discourse | PostgreSQL source (needs pdo_pgsql) |

| Convoro | Convoro → Flarum; bcrypt passwords copied, so members keep their logins |

Categories are imported as tags (requires flarum/tags); if tags aren't installed, discussions and posts still import, just untagged.

How it works

• Timeout-proof — the run is a resumable state machine; each request processes one small batch and returns, so memory stays flat and nothing runs long enough to time out. Works with or without a queue worker.

• Resumable — progress, cursors and the source→Flarum id-maps live in the database, so a run survives a closed tab, a reload, or a dropped connection.

• Faithful content — post bodies go source → HTML/Markdown → Flarum's formatter, landing in Flarum's native stored format so they render as proper rich text.

• Relations preserved — members, tags, discussions, first/last-post pointers, comment counts and participant counts are all rebuilt.

Requirements & tips

• Import into a fresh Flarum for the cleanest result.

• A queue worker is optional — the import runs from the browser without one. If you have fof/redis + a worker, it runs in the background instead.

• There's also a CLI for very large migrations or scripting:

  --host=127.0.0.1 --database=my_old_forum --username=root --password=secret --prefix=phpbb_
# add --test to only check the connection and show counts```

## License

MIT © ernestdefoe

A free, drop-in Typesense search driver for Flarum 2 —

fast, typo-tolerant full-text search across discussions, users and posts that anyone

can set up in a few minutes.

Flarum 2 shipped a pluggable search architecture; this extension implements a Typesense

driver for it. Text searches are answered by Typesense; everything else (filtering,

browsing, permissions) stays exactly as Flarum does it. You choose per resource which

searches Typesense answers.

Why it's safe by design

Typesense is only ever asked for candidate discussion IDs and their ranking. Which

results a given user may actually see is decided entirely by Flarum's own

whereVisibleTo (including tag restrictions) — never by Typesense. The search server

holds no authorization logic, and the browser never talks to it. Your API key is stored

server-side and is never exposed to visitors.

Requirements

• Flarum ^2.0

• A running Typesense server (self-hosted is a single binary or Docker container, or use

  Typesense Cloud)

Install

composer require ernestdefoe/typesense

Run Typesense (self-hosted example)

  -v typesense-data:/data typesense/typesense:27.1 \
  --data-dir /data --api-key='CHANGE_ME' --enable-cors```

## Set up

1. **Admin → Typesense Search.** Enter the host, port, protocol and API key, then **Save**.
2. Click **Test connection** to confirm Flarum can reach the server.
3. Click **Rebuild index** (or run `php flarum typesense:index`) to populate the index

   from your existing discussions.
4. Turn on **Use Typesense for discussion search** and save.

That's it — searches for discussions are now served by Typesense.

Search tabs that Typesense answers show a small **Powered by Typesense** badge in the

search modal, so you can see at a glance which searches are using the driver. Only that

on/off fact is sent to the browser — connection details and the API key stay on the server.

### Console

```php flarum typesense:index          # build / refresh the index
php flarum typesense:index --flush  # delete the index```

## How indexing works

* Each discussion is one Typesense document: its title plus the concatenated text of its

  visible comment posts.
* Creating, editing or deleting a discussion or post re-indexes the affected discussion

  automatically through Flarum's queued indexing pipeline.
* **Configure a real queue driver** (`redis`, `database`, …) in production so indexing and

  rebuilds run in the background rather than inline on a web request.

Several forums can share one Typesense server safely — collections are namespaced by a

prefix (set one, or it's derived from your forum URL).

## What's indexed

Everything Flarum can full-text search, each in its own namespaced collection:

* **Discussions** — title + the concatenated text of visible comment posts.
* **Users** — username and display name.
* **Posts** — individual comment post text (post-scoped search).

Each is toggled independently in the admin, so you can send discussion search to

Typesense while leaving users or posts on the database, or run all three through it.

(Groups and access tokens have no full-text search in Flarum, so they always stay on the

database driver.)

## License

[MIT](./LICENSE.md) © Ernest Defoe

A fully customizable, animated hero banner for your Flarum 2 discussion list — designed live, per page and per tag.

Give your community a polished, modern welcome. Hero Builder adds a configurable banner to the top of your discussion list — a title, subtitle, any Font Awesome icon, an animated gradient or a cover image, and optional live community stats. Set a different hero for the home page and for every tag, all from a live in-admin editor. No core files are touched.

Features

• Title & subtitle — say hello, set the tone.

• Any Font Awesome icon — type the class (fas fa-meteor, fas fa-dragon, fab fa-discord …), not a fixed preset list.

• Animated two-colour gradient or a cover image — pick a palette or drop in a full-bleed background.

• Optional live stats — surface real community numbers in the banner.

• Per-context heroes — a distinct hero for the home page and for each tag, so every corner of your forum gets its own welcome.

• No core files touched — ships as a clean, self-contained extension.

Hero Studio — design it live

Everything is configured in Admin → Extensions → Hero Builder, in the Hero Studio: pick a context (the home page or any tag), edit the fields, and watch the banner update in a live preview as you type. No saving-and-refreshing to see how it looks.

Tabs across the top let you switch between the home hero and a per-tag hero; the "Show the hero here" toggle lets you enable it only where you want it.

Installation

php flarum cache:clear```

Then open **Admin → Extensions → Hero Builder** and start designing.

### Requirements

* Flarum **2.0+**
* PHP 8.1+

---

## Building from source

```cd js
npm install
npm run build```

---

## License

[MIT](https://github.com/ernestdefoe/hero-builder/blob/master/LICENSE) © Ernest Defoe. Free to use, fork and build on.

A Flarum 2.x extension that lets members pick a favorite

FBS (NCAA Division I-A) college-football team. The team's logo is displayed

under the member's avatar on posts and on their profile.

Features

• Team picker — a searchable grid of all 136 FBS teams (logo + name) in the

  member's account settings.

• Avatar badge — the chosen team's logo appears under the avatar on posts

  (in the post's side column) and on the profile / user card.

• Require at registration (optional) — an admin toggle that forces new

  members to pick a team before they can use the forum. It shows a

  non-dismissible picker on the next page load for any logged-in member who

  hasn't chosen yet (works with normal, social, and SSO sign-ups).

• No database migration — the choice is stored in the member's existing

  preferences, so it loads with the user row (no extra query when rendering the

  badge across a page of posts).

• Logos via the ESPN CDN — no images are bundled or hosted by the extension.

Installation

php flarum cache:clear```

Then enable **Favorite Team** in the admin panel under Extensions.

## Usage

### For members

Go to **Settings** → **Favorite Team** → **Choose your team**, search or scroll

the grid, pick a team, and save. The logo then shows under your avatar.

### For admins

Open the **Favorite Team** extension page in the admin panel and toggle

**Require members to pick a team** to force the choice at registration. It's off

by default.

## How it works

* The FBS team list is bundled as static reference data in

  `resources/teams.json` (id, name, abbreviation, color,

  and ESPN logo URL per team).
* The chosen team id is stored in the member's `preferences`

  (`ernestdefoe-favorite-team.team`).
* The core `UserResource` is extended with two fields:
  * `favoriteTeamId` — writable by the member themselves (or an admin), validated

    against the bundled team list.
  * `favoriteTeam` — a read-only resolved object (`id`, `name`, `logo`, …) used to

    render the badge; readable by everyone.
* `GET /api/fbs-teams` returns the full team list for the picker.

## API

| Method | Endpoint | Notes |

|---|---|---|

| `GET` | `/api/fbs-teams` | Full FBS team list (registered users). |

| `PATCH` | `/api/users/{id}` | Set `favoriteTeamId` (self or admin). |

## Configuration

| Admin setting | Default | Effect |

|---|---|---|

| Require members to pick a team | off | Blocks members without a team until they choose. |

## Notes

Team names and logos are the property of their respective institutions and are

served from ESPN's public logo CDN. This is an unofficial fan tool and is not

affiliated with or endorsed by the NCAA, ESPN, or any team.

## License

MIT

# Favorite Team

A [Flarum](https://flarum.org) 2.x extension that lets members pick a favorite

FBS (NCAA Division I-A) college-football team. The team's logo is displayed

under the member's avatar on posts and on their profile.

## Features

* **Team picker** — a searchable grid of all 136 FBS teams (logo + name) in the

  member's account settings.
* **Avatar badge** — the chosen team's logo appears under the avatar on posts

  (in the post's side column) and on the profile / user card.
* **Require at registration (optional)** — an admin toggle that forces new

  members to pick a team before they can use the forum. It shows a

  non-dismissible picker on the next page load for any logged-in member who

  hasn't chosen yet (works with normal, social, and SSO sign-ups).
* **No database migration** — the choice is stored in the member's existing

  preferences, so it loads with the user row (no extra query when rendering the

  badge across a page of posts).
* **Logos via the ESPN CDN** — no images are bundled or hosted by the extension.

## Installation

```composer require ernestdefoe/favorite-team
php flarum cache:clear```

Then enable **Favorite Team** in the admin panel under Extensions.

## Usage

### For members

Go to **Settings** → **Favorite Team** → **Choose your team**, search or scroll

the grid, pick a team, and save. The logo then shows under your avatar.

### For admins

Open the **Favorite Team** extension page in the admin panel and toggle

**Require members to pick a team** to force the choice at registration. It's off

by default.

## How it works

* The FBS team list is bundled as static reference data in

  `resources/teams.json` (id, name, abbreviation, color,

  and ESPN logo URL per team).
* The chosen team id is stored in the member's `preferences`

  (`ernestdefoe-favorite-team.team`).
* The core `UserResource` is extended with two fields:
  * `favoriteTeamId` — writable by the member themselves (or an admin), validated

    against the bundled team list.
  * `favoriteTeam` — a read-only resolved object (`id`, `name`, `logo`, …) used to

    render the badge; readable by everyone.
* `GET /api/fbs-teams` returns the full team list for the picker.

## API

| Method | Endpoint | Notes |

|---|---|---|

| `GET` | `/api/fbs-teams` | Full FBS team list (registered users). |

| `PATCH` | `/api/users/{id}` | Set `favoriteTeamId` (self or admin). |

## Configuration

| Admin setting | Default | Effect |

|---|---|---|

| Require members to pick a team | off | Blocks members without a team until they choose. |

## Notes

Team names and logos are the property of their respective institutions and are

served from ESPN's public logo CDN. This is an unofficial fan tool and is not

affiliated with or endorsed by the NCAA, ESPN, or any team.

## License

MIT

A full-featured social groups extension for Flarum 2. Members can create public or private groups, post to a Facebook-style feed, hold threaded discussions, share media, react to posts, run polls, and more — with optional real-time updates powered by flarum/realtime.

Features

Groups

• Public & private groups — public groups are open to all; private groups require a join request or direct invitation.

• Group image & banner upload — each group has its own avatar and cover banner image.

• Featured groups — administrators can pin groups to a featured row on the group directory.

• Primary group badge — members designate one group as their primary group; the badge is displayed on their Flarum profile.

• Group analytics dashboard — overview of member count, post activity, and growth over time (visible to group admins and moderators).

• RSS feed — each group exposes a per-group RSS 2.0 feed at /groups/{slug}/feed.rss.

Feed

• Facebook-style post cards with full Flarum BBCode/Markdown rendering.

• Emoji reactions — six reaction types: 👍 Like, ❤️ Love, 😂 Haha, 😮 Wow, 😢 Sad, 😡 Angry; one reaction per user, toggleable.

• Polls — create polls directly from the post composer; members vote inline with live percentage bars.

• Link previews — URLs are automatically expanded into rich Open Graph preview cards (title, description, thumbnail).

• Media attachments — attach images and files to posts via fof/upload (optional).

• Pin posts — group admins can pin discussions to the top of the feed.

• Post search — debounced search bar filters discussions by title or content in real time.

• Post sharing — share any discussion into another group you belong to, with an optional comment; shared posts render a quoted card.

Discussions

• Threaded discussion view at /groups/{slug}/d/{discussionId} with nested comment replies.

• Pin discussions to the top of the discussion list.

• Share discussions to the group feed.

Media Gallery

• Dedicated "Media" tab on each group page aggregating all images from posts and discussions into a responsive thumbnail grid with lightbox.

Member Management

• Join requests — group admins approve or reject membership requests; direct invitations bypass the queue.

• Promote / demote — elevate a member to group admin or step them back down.

• Kick — remove a member from the group.

• Member badges on profiles — group membership chips appear on Flarum user profile cards forum-wide.

Notifications

• Alert when a new post is created in a group the user participates in.

• Alert when someone replies directly to a user's post.

Real-time (optional — requires flarum/realtime)

See the flarum/realtime Integration section below.

Requirements

| Dependency | Version | Required |

|---|---|---|

| Flarum | 2.x | Yes |

| PHP | 8.3+ | Yes |

| flarum/realtime | any | No — graceful no-op if absent |

| fof/upload | ^2.0 | No — required for file/image attachments in posts |

Installation

php flarum migrate
php flarum cache:clear```

Then go to **Admin → Extensions** and enable **Social Groups**.

**After every update**, run the migrate and cache-clear commands to apply any new database migrations:

```php flarum migrate && php flarum cache:clear```

---

## Configuration

### Admin panel settings

Navigate to **Admin → Extensions → Social Groups**:

| Setting | Options | Default |

|---|---|---|

| **Who can create groups** | `member` — any registered user; `admin` — forum administrators only | `member` |

### Group privacy

Group creators choose privacy at creation time:

| Type | Behaviour |

|---|---|

| **Public** | Anyone can view the feed, discussions, and gallery. Joining is instant. |

| **Private** | Content is hidden from non-members. New members must submit a join request (approved by a group admin) or be invited directly. |

---

## flarum/realtime Integration

The real-time features are entirely **optional**. If `flarum/realtime` is not installed the extension works normally — the typing endpoint silently returns `204` and the post-broadcast listener exits immediately without any error or warning.

When `flarum/realtime` **is** installed and running:

* **Live post injection** — after a member submits a reply in a group discussion thread, all other members viewing that thread see the new post card appear instantly via the `sg-post-created` WebSocket event. No page refresh is needed.
* **Typing indicator** — while a member is composing a reply, an animated "Jane is typing…" indicator with bouncing dots is broadcast via the `sg-typing` event and displayed above the reply box for all other members viewing the same thread. The indicator disappears automatically when the member stops typing or submits their post.
* **Deduplication** — the client compares each incoming post's ID against already-rendered posts to prevent duplicates when both the HTTP response and the WebSocket push arrive for the same post.
* **No extra configuration** — the extension uses the existing public Pusher/Soketi channel that `flarum/realtime` sets up. Nothing additional needs to be configured.

---

## Updating

```composer update ernestdefoe/social-groups
php flarum migrate
php flarum cache:clear```

---

## License

Released under the [MIT License](https://github.com/ernestdefoe/social-groups/blob/main/LICENSE). © Ernestdefoe

<https://ernestdefoe.online/extension/ernestdefoe/social-groups>

Bring live video into your community. Members go live from YouTube or Twitch,

and a LIVE NOW badge follows their avatar everywhere it appears — posts, the

discussion list, mentions, the header, the sidebar.

Free / MIT. The optional premium add-on OnAir+

turns your forum into the whole platform — a built-in RTMP server (stream straight in

from OBS), in‑forum HLS playback, multistream, VOD, live chat, go‑live notifications and

scheduled streams. See the comparison below.

Features

• 🔴 LIVE badge on every avatar — one Avatar override lights a streamer up everywhere.

• ▶️ YouTube + Twitch embed viewer — paste a channel/video URL and go live.

• 📡 Presence with graceful fallback — uses flarum/realtime for instant badge

  updates when installed, transparently falls back to lightweight polling when it isn't.

• 🟥 Live Now widget + a /onair directory — see who's streaming at a glance.

• 🔐 Permissions + admin settings — who can go live, default provider, poll interval.

• ⏱️ Stale‑stream reaper — auto‑ends streams left running.

The Live directory

OnAir vs OnAir+

OnAir (this extension) is free and complete on its own for YouTube/Twitch streamers.

OnAir+ is a paid add‑on for communities that want to host streaming themselves.

| | OnAir (free) | OnAir+ |

|---|:---:|:---:|

| LIVE badge on avatar, everywhere | ✅ | ✅ |

| Live Now widget + /onair directory | ✅ | ✅ |

| YouTube embed viewer | ✅ | ✅ |

| Twitch embed viewer | ✅ | ✅ |

| Realtime presence + polling fallback | ✅ | ✅ |

| Permissions + admin settings | ✅ | ✅ |

| Auto‑end stale streams | ✅ | ✅ |

| Built‑in RTMP server → in‑forum HLS | — | ✅ |

| Stream keys + creator studio | — | ✅ |

| Multistream / restream to YouTube + Twitch | — | ✅ |

| VOD recordings | — | ✅ |

| Live chat overlay | — | ✅ |

| Go‑live notifications + follow a streamer | — | ✅ |

| Scheduled streams + reminders | — | ✅ |

| Concurrent viewer counts | — | ✅ |

OnAir+ — stream straight into the forum

Members broadcast from OBS to your own server; viewers watch an hls.js player inline,

with live chat beside it.

OnAir+ — creator studio

Each streamer gets an ingest URL, a secret stream key, multistream targets, and a one‑click

key reset.

Install

composer require ernestdefoe/onair

Then enable OnAir in the admin panel. Optionally install flarum/realtime for

instant (push) LIVE badges — OnAir detects it automatically. For self‑hosted streaming,

add OnAir+ (composer require ernestdefoe/onair-pro).

Development

npm install
npm run build      # or: npm run dev  (watch)```

A no‑backend concept render of the whole product lives in `preview/index.html`.

## Architecture notes

* **LIVE badge:** overrides the shared `Avatar` component (main‑bundle, safe to extend at

  init) and reads a serializer‑supplied `user.isLive()`.
* **Presence transport:** `app.onair.presence` picks `RealtimeTransport` when

  `flarum/realtime` is detected, else `PollingTransport`; both expose the same API.
* **Providers:** `app.onair.providers` (JS) + the `StreamProvider` interface (PHP) are the

  extension points **OnAir+** plugs its RTMP/HLS provider into.

## License

MIT © Ernestdefoe

A flexible user projects extension for Flarum 2 — a showcase page for creator communities. Members publish "projects" (books, games, apps, art, mods, anything) as cards on a dedicated page, with rich, admin-configurable metadata.

Inspired by this community request. Free and MIT-licensed.

Features

• Project cards with an optional cover image, author, categories, key parameters, a short description and link buttons — on a dedicated /projects page.

• Search & filters — full-text search, category filter and sort (recent / most-liked / A–Z), plus an Add project button.

• Admin-defined categories with an icon and accent colour. A project's main category becomes a badge shown next to the author's name across the forum.

• Custom parameters — define your own typed fields (text, paragraph, number, date, URL, select, yes/no) such as Genre, Age rating or Release date. Choose which show on the card.

• Flexible link/button system — define button slots, optionally restricted to specific domains (e.g. only YouTube links), with default or custom labels. Example for a book: Read Excerpt, Buy, Discuss on Forum.

• Optional moderation — projects can publish instantly or wait for approval, controlled per-group by the Publish without moderation permission.

• Detail page with forum-formatted content, all parameters and link buttons; link a forum discussion for comments.

• Built-in likes on every project.

• Profile integration — a Projects tab on each member's profile, plus a featured-project badge (their main category's icon, with the project name on hover) next to their username everywhere.

• FoF Badges integration (optional) — award a badge when a member's project is first published.

Screenshots

| Browse page | Project detail |

| --- | --- |

| | |

| Submission form | Admin configuration |

| --- | --- |

| | |

Permissions

| Permission | Default |

| --- | --- |

| Create projects | Members |

| Publish without moderation | — (admins/mods always can) |

| Moderate projects | Moderators |

Installation

php flarum migrate
php flarum cache:clear```

Then open **Admin → Projects** to add categories, custom parameters and button slots.

## License

[MIT](https://github.com/ernestdefoe/projects/blob/main/LICENSE)

A gaming theme for Flarum 2: chamfered surfaces, neon accents, mono typography, hex-clipped avatars, hero with blinking cursor, level/XP sidebar widget, and a stats footer.

Features

• Dark + Light mode — admin-configurable default, per-user toggle in the header (☾ / ☀)

• Branded hero — replaces the default IndexPage hero with a panel showing an eyebrow line, big mono headline ("Welcome to {forum}"), tagline, and an optional row of tag-shortcut chips

• Server-status footer — four chamfered stat cards (Posts · Discussions · Members · Online Now) rendered at the bottom of the index page, cached server-side at 60s

• Player Card — sidebar widget for the logged-in user with hex avatar, derived LVL N · {posts} POSTS, and a cyan→magenta XP bar

• Rarity Legend — sidebar panel mapping the four tag-color tiers (Legendary / Epic / Rare / Common) so newcomers learn the vocabulary

• Post styling — chamfered post cards, mono usernames in cyan, post-number pills, accent-bordered blockquotes, mono code blocks

• Composer + Scrubber — restyled to match the theme

The theme is a pure CSS/LESS skin layered on top of stock Flarum — no Mithril components replaced or routes added beyond the small components above. Anything that uses Flarum's CSS variables (--primary-color, --secondary-color, etc.) is remapped, so most extensions skin for free.

Requirements

• Flarum 2.x

• PHP 8.3+

Installation

php flarum cache:clear```

Then enable **Respawn** in **Admin → Extensions**.

---

## Configuration

All settings are in **Admin → Extensions → Respawn**.

| Setting | Description | Default |

|---|---|---|

| **Theme Mode** | Default colour mode for new visitors (`Dark` or `Light`). Users can toggle with the moon/sun button in the header. | `Dark` |

| **Hero Tagline** | Subtitle shown under the welcome headline. Leave blank to hide. | `Drop in, level up, and join the discussion.` |

| **Hero Eyebrow** | Small accent line above the headline. | `▸ Player Connected` |

| **Hero Tag Chips** | Comma-separated list of tag slugs to feature as quick-jump chips (e.g. `halo, elden-ring, deals`). Leave blank to hide. | *(blank)* |

The hero headline reads from Flarum's standard **Forum Title** setting (Admin → Basics).

---

## How the stats are computed

`ForumStatistics` queries the `posts`, `discussions`, `users`, and `users.last_seen_at` tables and caches each count for 60 seconds. The "Online Now" tile uses a 5-minute activity window matching Flarum's stock indicator. Any DB error renders the affected tile as `—` rather than a misleading `0`.

---

## Player Card level formula

Currently: `level = floor(posts / 100) + 1`, progress to next level = `posts % 100`.

It's a deliberately simple linear ramp. If you want a non-linear curve (exponential, custom thresholds, Bronze/Silver/Gold ranks instead of a number), open an issue.

---

## Customising

The theme exposes its tokens as CSS variables on `:root` (and `[data-respawn="light"]`), so an extension or custom CSS can override any of them without touching Respawn itself:

```:root {
  --r-accent:  #50ff8a;    /* lime instead of cyan */
  --r-magenta: #ff6b35;    /* orange instead of magenta */
}```

Every component reads through these variables.

---

## Support

Questions, bug reports, and feature requests:

* **Support forum:** https://ernestdefoe.online
* **Issues:** https://github.com/ernestdefoe/respawn/issues

---

## License

Respawn is released under the [MIT License](https://github.com/ernestdefoe/respawn/blob/main/LICENSE).

Copyright © ernestdefoe.

Design your whole forum on the live page — colours, fonts, layout, widgets, chrome — and publish when it's perfect. No code, no rebuilds, no guesswork.

Bespoke is a premium theme and an in-context visual theme builder for Flarum 2, in the spirit of Invision Community's Theme Designer. Open the overlay editor right on your forum, change anything, watch it repaint instantly, and hit Publish when you're happy. Visitors only ever see the published result.

Table of contents

• Why Bespoke

• Feature tour

  • The live editor

  • Palette & accessibility

  • Typography (any Google Font)

  • Shape & depth

  • Layout modes — Feed / Grid / Category

  • Hero

  • Effects — header, dark mode, glass, tag colouring

  • Site chrome — announcement bar & footer

  • Widgets

  • Inspector

  • Presets, import & export

• How it works

• Installation

• Using the editor

• Permissions

• Internationalisation

• Performance & security

• Requirements & compatibility

• FAQ

• Pricing

• Support

• License

Why Bespoke

Most Flarum theming means editing LESS, redeploying, and refreshing to see what you got. Bespoke replaces that loop with a live, in-context editor:

• Instant — colour, font, radius, spacing and effect changes repaint with zero server round-trips.

• Safe — everything you change is a private draft until you Publish; one click reverts.

• Deep — it's a complete theme in itself (three discussion-list layouts, hero, posts, avatars, header variants), not just a colour picker.

• No code — but power users still get a Custom CSS escape hatch.

Feature tour

The live editor

A floating ✦ Edit theme launcher appears for admins. It opens a docked overlay with tabs for every part of the theme; the forum stays fully interactive behind it so you always edit in real context. A light/dark preview switch, Save draft, and Publish sit in the footer.

Palette & accessibility

Set every colour role — brand, accent, background, surface, text, muted, border — with independent light and dark values. Don't want to hand-pick seven colours? Generate harmony from Brand derives a balanced palette from one hue.

A built-in WCAG contrast checker grades the key text/background pairings live (AA / AAA / fail) so your theme stays readable as you go.

Typography (any Google Font)

Pick any Google Font by name — not a short curated list, the whole library — for headings and body independently, plus base size, modular type scale, and line-height. System and already-loaded fonts work too. Font links are injected server-side so there's no flash of the wrong typeface.

Shape & depth

Corner radius, border width, elevation/shadow depth, button styles (solid / soft / outline / ghost), post styles (boxed / flat / bubble), and avatar shapes (circle / rounded / square / hexagon).

Layout modes — Feed / Grid / Category

The discussion list ships in three first-class layouts, switchable live:

| Mode | Look |

|---|---|

| Feed | Comfortable, separated cards — the refined default. |

| Grid | Magazine cards with a cover image (pulled from the first post), excerpt, tag pills, and a participant/reply footer. Configurable columns or auto-fit. |

| Category | A classic forum category index built from your tags, inspired by fof/categories — parent tags become sections, child tags become rows with icons, descriptions and counts. |

Hero

Full control of the welcome hero: height, contained vs. full-bleed width, a brand→accent gradient or a background image, custom text colours, and an admin-locked (non-dismissible) option so the hero always shows.

Effects — header, dark mode, glass, tag colouring

The Effects tab is where Bespoke earns its keep:

• Header style — solid, transparent, or gradient; optional centred logo; sticky on/off.

• Visitor dark-mode toggle — adds a sun/moon switch to the header so each visitor picks their own scheme (remembered locally, applied before paint — no flash).

• Glassmorphism — frosted, translucent surfaces; pairs beautifully with a site background image.

• Subtle animations — tasteful hover/entrance motion, toggleable.

• Colour UI by active tag — a built-in ramon/colored replacement: on a tag page the hero adopts that tag's colour (with automatically-contrasting text), and the brand accent follows too.

• Card tag accent — give each discussion card a left bar or full border in its own primary-tag colour, so a mixed list reads as a colour-coded index.

Site chrome — announcement bar & footer

• Announcement bar — a dismissible, optionally-linked banner across the top of every page.

• Custom footer — your own links, social icons (X, Discord, GitHub, YouTube, Facebook, Instagram), and copyright/text — no second extension required.

Widgets

Drag widgets from the tray into any zone — above the list, sidebar, below the list, header, hero, or footer — then reorder them by their handle. Click a placed widget to edit its settings in the inspector.

| Widget | What it shows |

|---|---|

| Hero banner | Heading, subheading, CTA, background image. |

| Community stats | Discussions / posts / members / online counts. |

| Online users | Avatars of who's online now. |

| Top Contributors | Ranked by posts, likes received, or discussions, over week / month / all-time. |

| Newest Members | Most-recent sign-ups, as a list with join dates or an avatar grid. |

| Trending threads | Most-active discussions over 24h / 48h / 7d. |

| Call to action | Heading, body, button + link. |

| Markdown / HTML | Free-form content block. |

| Tag cloud | Popular tags. |

| Articles | From Page Builder, shown automatically when that extension is installed. |

All data-driven widgets share one cached request per page, so a widget-heavy sidebar stays cheap.

Inspector

Toggle Inspect (⊹) and hover any element on the page — Bespoke highlights it and labels it; click to jump straight to the controls that style it.

Presets, import & export

Start from curated themes (Aurora, Carbon, Sunrise, Newsprint, Terminal, Grape), then export your finished theme as a portable .bespoke.json and import it on another Bespoke site — perfect for moving a look between staging and production, or shipping a house style across forums.

How it works

Bespoke splits styling into two layers so editing feels instant but still reaches deep into Flarum:

| Layer | Carries | Mechanism | When |

|---|---|---|---|

| Instant | colours, fonts, radius, spacing, shadows, effects, layout switches | CSS custom properties in <style id="bespoke-vars"> + data-bespoke-* attributes on <html> | every page load; mutated client-side in the editor for zero-latency preview |

| Structural | the premium base theme, layout modes, component styling | compiled LESS (less/forum.less) | at build/compile time |

The theme is stored as a single JSON document (tokens + layout + zones + custom CSS + chrome). The editor edits an in-memory copy and applies it live; Save draft persists it for admins only; Publish promotes it to what every visitor sees. Because the instant layer is server-injected, the forum is themed before JavaScript runs — there's no flash of an unstyled or default theme.

Installation

composer require ernestdefoe/bespoke

Then enable Bespoke in Admin → Extensions, open your forum, and click ✦ Edit theme (bottom-right).

To update:

php flarum cache:clear```

---

## Using the editor

1. Click **✦ Edit theme**. The overlay docks to the side; your forum stays live behind it.
2. Work through the tabs — **Palette, Type, Shape, Layout, Hero, Discussion, Effects, Site, Widgets, Presets**. Every change previews instantly.
3. Use the footer **◑** switch to preview light vs. dark.
4. **Save draft** to keep working privately, or **Publish** to go live for everyone.
5. Use **Inspect (⊹)** any time to jump from an on-page element to its controls.

---

## Permissions

The editor and the theme save/publish API are gated on the `bespoke.edit` ability, which is granted to **administrators**. Visitors and regular members never load the editor and cannot write theme data or custom CSS.

---

## Internationalisation

Every user-facing string is translatable via standard Flarum locale files (`resources/locale/en.yml`) — tab names, control labels, widget names, hints, and messages. Translations are welcome.

---

## Performance & security

* **One request for widgets** — all data widgets share a single, 60-second-cached `widget-data` call per page.
* **No render flash** — colours/fonts are injected server-side before JS.
* **Visibility-aware** — the Trending widget is scoped to guest-visible discussions, so its shared cache can never leak titles of private or tag-gated threads.
* **Admin-only writes** — theme save/publish (including Custom CSS) require `bespoke.edit`; injected custom CSS is additionally sanitised against tag-breakout as defence-in-depth.

---

## Requirements & compatibility

* **Flarum** `^2.0`
* **PHP** `8.3+` (Flarum 2's minimum)
* Optional: [Flarum Tags](https://github.com/flarum/tags) (Category layout, tag colouring, tag accents) and Page Builder (Articles widget) light up automatically when present.

---

## FAQ

**Will my visitors see my experiments?**

No. Everything is a private draft until you **Publish**. One click reverts.

**Can I use a font that isn't in the suggestions?**

Yes — type *any* Google Font name; the whole library is available.

**Does it replace ramon/colored or fof/categories?**

It includes native equivalents — tag-driven colouring and a tag-based category index — so you don't need to run both.

**Can I move a theme between forums?**

Export `.bespoke.json` on one and import it on another.

**Is there a flash of the default theme on load?**

No — the instant layer is server-rendered.

---

## Pricing

Bespoke is a premium extension sold on [Floxum](https://floxum.com/extension/ernestdefoe/bespoke):

| Plan | Price |

|---|---|

| **Annual** | **$20.00 / year** |

| **Lifetime** | **$100.00 one-time** |

Both plans include all features and updates. Buy at [floxum.com/extension/ernestdefoe/bespoke](https://floxum.com/extension/ernestdefoe/bespoke).

---

## Support

Found a bug or have a request?

* **Support site:** [ernestdefoe.online](https://ernestdefoe.online)
* **Issues:** [github.com/ernestdefoe/bespoke/issues](https://github.com/ernestdefoe/bespoke/issues)

---

## License

Proprietary — commercial license. © 2026 ernestdefoe. See `LICENSE.md`.

A Flarum extension that sends beautifully formatted digest emails to your forum members on a schedule they choose. Each email summarises what happened on your forum since the last digest — new discussions, active conversations, new members, leaderboard standings, badges earned, pick'em results, awards, and more — all in a clean, branded email that works in every major email client.

What It Does

Instead of sending a notification every time something happens, Digest Mail sends one well-organised summary email per period. Members choose how often they want it — daily, weekly, or monthly — and can unsubscribe at any time with a single click. Admins control what goes in the email, when it sends, and how hard it works on the server.

Email Content

Every digest email is made up of sections. Some are always included, others only appear when the relevant extension is installed and enabled by the admin.

Always included

Featured Discussion

An admin-pinned discussion displayed prominently at the top of every digest with a highlighted card, author avatar, and a button linking directly to the discussion. Set this to your most important current thread — announcements, pinned rules, ongoing events. Leave it blank to disable it.

New Discussions

Discussions that were started during the digest period, showing the title, author, and reply count.

Active Discussions

The most engaged discussions during the period, ranked by a configurable activity score that balances reply count and recency. The admin can tune how much weight each factor carries.

Unread Discussions

Personalised to each recipient — shows discussions they have not read yet, based on their own read history. This is the only section that differs between subscribers.

New Members

Members who joined during the period, shown with avatars and join date.

Community Stats

A four-number summary bar showing total posts, discussions, new members, and active users during the period. This always appears near the top of every email regardless of section order.

Favorite Discussions

The most liked or reacted-to discussions during the period. If fof/reactions is enabled, shows a per-emoji reaction breakdown. If only flarum/likes is installed, shows like counts. Requires at least one of those extensions to be active.

Optional — require additional extensions

Leaderboard (requires huseyinfiliz/leaderboard)

Shows the top point-earners for the period with a podium display for the top three, a full ranked table for positions four and beyond, movement indicators showing who moved up or down, and a "biggest mover" spotlight for whoever gained the most points during the period.

Badges (requires fof/badges)

Shows badges earned during the period — recent earners with their badges, the most-awarded badge of the period, and the rarest badge awarded.

Pick'em (requires huseyinfiliz/pickem)

Shows upcoming pick'em matches members can still vote on, recent match results, and the current pick'em leaderboard standings.

Gamepedia (requires huseyinfiliz/gamepedia)

Shows the most-discussed game pages from the period and newly added games.

Awards (requires huseyinfiliz/awards)

Shows active and upcoming awards — including name, description, voting deadline countdown, category list, vote totals, and current front-runners when live vote display is enabled on the award.

Section Order

Every section listed above can be reordered from the Digest Order tab in the admin panel. Use the arrows to set the sequence sections appear in each email. Only enabled sections appear in the list. The three core sections (Discussions, New Members, and Stats) are always shown regardless of order position.

Scheduling

How timing works

You set the time you want digests to go out — for example 8 a.m. — and the extension fires at that time in whichever timezone you select. You choose your own timezone, not the server's. A forum run by an admin in Chicago should be set to Central Time and set to 8 a.m., even if the server itself is physically located somewhere else entirely.

Single hour vs send window

Single hour: The extension dispatches one chunk of subscribers per scheduler run at the configured hour. For most small forums this means all subscribers are processed in one or two runs within the same minute.

Send window: You set a start time and an end time — for example 2 a.m. to 5 a.m. — and the extension dispatches one chunk of subscribers per minute throughout that window. Each minute the scheduler fires, the next batch is processed and queued. Workers drain each batch in parallel as it arrives. This keeps server load low and steady instead of hitting everything at once. Recommended for forums with more than a few thousand subscribers.

When the send window is active, the extension tracks its own progress automatically. Once all subscribers for a given frequency have been processed, it stops on its own — it does not keep running until the window closes.

User frequency choices

Each user picks their own digest frequency from their account settings page:

• Daily — one email every day at the configured time

• Weekly — one email on the configured day of the week

• Monthly — one email on the configured day of the month

• Off — no digest emails

Admins can restrict which frequencies are available. A low-traffic forum might choose to offer only weekly and monthly and hide the daily option entirely. The unsubscribe preference page shown to users automatically reflects whichever options the admin has enabled.

Design and Themes

Every email uses a table-based HTML layout that works reliably in all major email clients including Gmail, Outlook, Apple Mail, and mobile clients.

The email uses your forum's configured brand colours throughout — headings, buttons, and accent elements all pull from your forum's primary and secondary colour settings automatically.

Light and dark mode: If fof/nightmode is installed, each subscriber's email theme automatically matches their night mode preference — members who use dark mode receive a dark-themed email. Members who have not set a preference receive the light version. If night mode is not installed, all emails use the light theme.

Unsubscribe

Every email includes a secure unsubscribe link in the footer. Clicking it takes the subscriber to a preference page where they can choose a different frequency or opt out entirely.

The link is unique to each subscriber and valid for 90 days. Unlike some implementations, the link remains valid across multiple digest sends — it is only replaced when it expires or the subscriber uses it to change their preference. This means a user who receives a digest on Monday and clicks the link on Friday will always get a working page.

Admin Panel

The admin panel is organised into four tabs.

Settings

Content Limits — set the maximum number of items shown in each section: new discussions, active discussions, unread discussions, new members, leaderboard entries, badges, pick'em entries, and gamepedia entries. Also includes the featured discussion ID and the weighting controls for the hot score algorithm.

Schedule — set your timezone, send time (start hour), optional send window end hour, weekly send day, and monthly send day. A live summary below the time dropdowns shows you exactly what mode you are in and when emails will go out.

User Frequency Options — choose which frequency options are available to users on their account settings page.

Extension Integrations — enable or disable each optional section individually. A toggle is only activatable when the required extension is installed and enabled in Flarum. Sections that are disabled here are removed from the digest entirely and do not appear in the Digest Order tab.

Token Checker — paste any unsubscribe token to verify it is valid, see which user it belongs to, and confirm its expiry date. Useful for diagnosing unsubscribe link issues without sending an email.

Digest Order

Arrow-based ordering for all active sections. Changes save immediately and apply to all future digests. Sections that are not currently enabled are not shown here — enable them in the Settings tab first.

Statistics

Live statistics pulled from your forum's database:

• Subscription Overview — total members, total digest subscribers, and the overall subscription rate as a percentage

• Subscribers by Frequency — how many subscribers are on each frequency, with a visual bar and a View button that slides open a paginated list of all subscribers for that frequency showing username, avatar, and last sent date

• Last Sent — the date and time each frequency was last sent

• Send History — one entry per frequency per day showing the total sent and skipped count. History is retained automatically: 30 daily entries, 52 weekly entries, and 24 monthly entries

Server Settings

Everything related to how the extension uses your server, in one place. The page auto-detects your forum's installation path and generates ready-to-copy cron lines and config blocks using your actual server path.

• Queue Settings — queue name, chunk size (subscribers dispatched per scheduler run), job delay, and maximum retry attempts

• Cron Setup — tailored setup instructions for your chosen queue backend: Sync, Database Queue, or Redis/Valkey. Each tab shows only what is relevant to that setup, including retry and backoff behaviour, send window guidance, and optional two-phase pre-population for very large forums

• Recommended Settings by Forum Size — a reference table covering 100 members through 100,000+ with suggested chunk size, worker count, and send mode for each tier

Test Send

From the Settings tab, any admin can send a live digest email to any address immediately — without affecting any subscriber records or timestamps. Choose a frequency and an optional theme (light or dark), enter any email address, and click Send. Use this to check your email layout, branding, and content before your first scheduled send goes out.

Requirements

Core requirements

• PHP 8.1 or higher

• Flarum 2.0 or higher

• A working outbound mail configuration in your Flarum admin panel (SMTP, Mailgun, Postmark, etc.)

• A server cron job running schedule:run every minute — this is the standard Flarum scheduler requirement shared by many other extensions

Queue driver

By default Flarum uses the sync queue driver, which processes jobs during the web request rather than in the background. This is fine for very small forums but causes problems as your subscriber list grows:

| Subscribers | What happens on sync |

|---|---|

| Under \~50 | Fine — most servers handle it without issue |

| 50–200 | Slow page responses, occasional timeouts |

| 200+ | Regular timeouts, memory exhaustion on typical VPS hosting |

| 500+ | Effectively broken — posts fail or appear to hang |

Flarum 2.x has a database queue driver built into core — no extension install required. To enable it, add this to your config.php:

    'driver' => 'database',
],```

For larger forums, Redis or Valkey with Laravel Horizon and Supervisor is the most scalable option. See the **Server Settings** page in the admin panel for full setup instructions tailored to your chosen approach.

### Optional integrations

| Extension | What it enables |

|---|---|

| `huseyinfiliz/leaderboard` | Leaderboard section |

| `fof/badges` | Badges section |

| `huseyinfiliz/pickem` | Pick'em section |

| `huseyinfiliz/gamepedia` | Gamepedia section |

| `huseyinfiliz/awards` | Awards section |

| `flarum/likes` | Favorite Discussions section |

| `fof/reactions` | Per-emoji reaction breakdown in Favorite Discussions |

| `fof/nightmode` | Per-user dark mode email theme |

---

## Installation

```composer require ernestdefoe/digest-mail
php flarum migrate```

Then enable the extension in your Flarum admin panel.

---

## Cron Setup

The only cron line required for all setups is the Flarum scheduler. Add it to your server's crontab by running `sudo crontab -u YOUR_WEB_USER -e`, replacing `YOUR_WEB_USER` with the user that owns your Flarum files. If you are unsure which user that is, run `ls -la /path/to/flarum` and check the owner column. Common values are:

* **Ubuntu/Debian** with Nginx or Apache → `www-data`
* **CentOS/RHEL** with Apache → `apache`
* **CentOS/RHEL** with Nginx → `nginx`
* **Shared hosting** → your hosting account username

```* * * * * cd /path/to/flarum && php flarum schedule:run >> /dev/null 2>&1```

**If you are using the sync driver**, that is the only line you need.

**If you are using the database queue driver**, add a second line for the queue worker:

```* * * * * cd /path/to/flarum && php flarum queue:work --queue=digest,default --max-time=55 --tries=3 --backoff=30 >> /dev/null 2>&1```

`--queue=digest,default` processes digest jobs first, then other Flarum notifications. `--max-time=55` stops the worker cleanly before the next cron fires. Add one additional worker line per parallel worker for larger forums.

**If you are using Redis or Valkey with Horizon and Supervisor**, the scheduler cron line is the only line you need. Do not add a `queue:work` cron line — Horizon is your persistent worker and runs continuously under Supervisor. Adding a `queue:work` cron on top would create competing workers.

Adjust `user` to match the user that owns your Flarum files (`www-data`, `apache`, `nginx`, or your hosting account username depending on your setup).

The **Server Settings** page in the admin panel generates ready-to-copy cron lines and config blocks using your actual server path and current Queue Settings values.

### Two-phase pre-population (50,000+ subscribers only)

For very large forums, you can pre-populate the queue with jobs before the send window opens so workers have no construction overhead when they start. Add this cron line 10 minutes before your configured send window start. For example, if your window starts at 2 a.m., run this at 1:50 a.m.:

```50 1 * * * cd /path/to/flarum && php flarum digest:enqueue --frequency=daily --delay=600 >> /dev/null 2>&1```

The first number is the minute (50 = :50) and the second is the hour in 24-hour format (1 = 1 a.m.). Adjust both to match your setup.

---

## Console Commands

### `digest:send`

The main send command. Runs automatically via the scheduler every minute. Outside the configured send window it exits immediately. Inside the window it dispatches one chunk of subscribers and exits, leaving the rest for the next minute.

```# Normal run — respects time gate and window
php flarum digest:send

# Force a specific frequency, bypassing the time gate (useful for testing)
php flarum digest:send --frequency=daily

# Preview mode — shows eligible recipients and content without sending anything
php flarum digest:send --frequency=weekly --dry-run

# Test a single user by ID
php flarum digest:send --frequency=daily --user=1

# Override the queue name
php flarum digest:send --queue=high-priority

# Override the job delay in seconds
php flarum digest:send --delay=300```

### `digest:enqueue`

Pre-populates the queue with jobs but does not send them. Intended for very large forums that want to build all jobs ahead of time so workers have no construction overhead when the send window opens.

```# Pre-build all daily digest jobs with a 10-minute delay before they become available
php flarum digest:enqueue --frequency=daily --delay=600

# Preview how many users would be enqueued without actually doing it
php flarum digest:enqueue --frequency=weekly --dry-run```

---

## Performance and Scaling

The extension is built for efficiency at any subscriber count.

**Shared data caching:** Almost everything in a digest email is identical for every subscriber in the same frequency group — new discussions, hot discussions, new members, leaderboard, awards, badges, and all other sections are built once per send run and stored in cache for 2 hours. The only per-subscriber query is unread discussions. For a forum with 10,000 daily subscribers this means roughly 10,013 total database queries per send instead of 100,000+.

**Lightweight job storage:** Each background job stores only a user ID, frequency, and a reference to the cached shared data — typically under 500 bytes per job. The jobs table stays small and workers stay fast.

**Persistent unsubscribe tokens:** Each subscriber's unsubscribe token is generated once and reused across sends. It is only replaced when it expires (90 days) or the subscriber uses it. This ensures unsubscribe links in emails always work, regardless of how many sends have occurred since the email was received.

**Send window pacing:** With a send window configured, the extension dispatches one chunk of subscribers per minute throughout the window. Workers drain each chunk in parallel as it arrives. Server load stays low and steady across the entire window period.

**Recommended settings by forum size:**

| Forum Size | Chunk Size | Workers | Send Mode |

|---|---|---|---|

| 100–500 members | 200 | 1 | Single hour |

| 500–2,000 | 500 | 1 | Single hour |

| 2,000–5,000 | 1,000 | 2 | 1–2 hour window |

| 5,000–15,000 | 2,000 | 3 | 2–3 hour window |

| 15,000–50,000 | 5,000 | 5 | 2–4 hour window |

| 50,000–100,000 | 7,500 | 8 | 3–4 hour window |

| 100,000+ | 10,000 | 10+ | 4+ hour window |

For 50,000+ member forums, consider switching from the database queue driver to Redis or Valkey with Horizon and Supervisor for significantly higher throughput and real-time queue monitoring. The Server Settings page in the admin panel includes full step-by-step setup instructions for this configuration.

---

## Credits

Originally created by [Resofire](https://github.com/resofire). Rebranded and

maintained by [ernestdefoe](https://github.com/ernestdefoe), with full credit and

thanks to the original author.

## License

MIT — Copyright (c) 2026 Resofire

A Flarum 2 extension. A Discourse-style topic map under the first post of busy discussions: views, likes, outbound links, top participants and estimated read time at a glance — plus a Top Replies panel that jumps you straight to the most-liked answers.

Features

• Stats bar on the first post once a discussion passes a reply threshold (admin setting): views · likes · links · participants (with avatars) · minutes-to-read.

• Top Replies — the most-liked replies with author + excerpt; click one to jump to that post. Works with flarum/likes or fof/reactions (the stat relabels itself "reactions"); hides when neither is installed.

• Links panel — the discussion's outbound links grouped by URL, tap the links stat to expand.

• View counting built in (guests count, one per browser session, visibility-checked). On forums running ernestdefoe/bespoke, Bespoke's view counter is used instead — one source of truth, never double-counted.

• Everything is computed server-side and cached; a 400-post scan cap keeps huge topics cheap.

• Fully translatable.

Installation

php flarum migrate
php flarum cache:clear```

## Updating

```composer update ernestdefoe/topic-map
php flarum migrate
php flarum cache:clear```

## Links

* [Packagist](https://packagist.org/packages/ernestdefoe/topic-map)
* [GitHub](https://github.com/ernestdefoe/topic-map)

Paste a GitHub repo URL into the Flarum composer and the URL is auto-replaced with the rendered README markdown.

How it works

1. User pastes https://github.com/owner/repo into any composer (new discussion, reply, edit, private message).

2. The frontend recognizes it as a GitHub repo root URL and intercepts the paste.

3. It calls POST /api/gh-readme/fetch on the Flarum backend.

4. The backend fetches https://api.github.com/repos/{owner}/{repo}/readme, decodes the base64 payload, rewrites relative image / link / anchor URLs against the repo's HEAD branch on raw.githubusercontent.com, and returns the processed markdown.

5. The frontend replaces the URL in the composer with the README markdown. The user can edit freely from there.

Subsequent pastes of the same repo are served from a 10-minute server-side cache so a popular forum doesn't burn GitHub's rate limit.

Works with both composer types

| Composer | Behavior |

| --- | --- |

| Default Flarum (textarea + flarum/markdown) | URL replaced inline by the markdown source. The post renders as formatted markdown at display time. A visible italic "Loading…" marker shows in the textarea during the fetch. |

| fof/rich-text (Tiptap WYSIWYG) | URL replaced by rich nodes — headings, paragraphs, lists, code blocks, blockquotes, images all appear formatted in the composer immediately. A toast notification shows during the fetch (no inline marker — finding a specific text node inside a ProseMirror document is brittle). |

Detection is automatic via the presence of editor.editor on the active driver. No setting needed.

Install

php flarum cache:clear```

Then enable in **Admin → Extensions → GitHub README Paste**.

`flarum/markdown` is a `suggest` dep — without it the inserted markdown ends up in the post but renders as plain text rather than formatted headings/lists/code blocks.

## Configure

**Admin → Extensions → GitHub README Paste:**

* **GitHub Personal Access Token** *(optional)* — raises GitHub's API rate limit from 60/hour-per-IP (unauth) to 5000/hour. No scopes required for public repos.
* **Cache duration (minutes)** — how long the server caches each README before refetching. Default 10. Clamped 1–60.

## URL shapes accepted

| URL | Behavior |

| --- | --- |

| `https://github.com/owner/repo` | 

✅ expanded | | `https://github.com/owner/repo/` | ✅ expanded | | `https://github.com/owner/repo.git` | ✅ expanded (strips `.git`) | | `https://www.github.com/owner/repo` | ✅ expanded | | `https://github.com/owner/repo/tree/main` | ❌ left as-is (use the root URL) | | `https://github.com/owner/repo/blob/main/file.md` | ❌ left as-is (file links, not repos) | | `http://github.com/owner/repo` | ❌ rejected (must be https) | | `https://gitlab.com/owner/repo` | ❌ not GitHub | ## Security notes * Strict URL allowlist (`github.com` host only). * Owner/repo regex-allowlisted to GitHub's own charset. * The backend never fetches the user-supplied URL directly — it constructs the API call from validated owner/repo segments. SSRF surface is the GitHub API host only. * Response body capped at 2 MB. * 10s connect + 15s total request timeout. * TLS verification on. * Endpoint requires an authenticated Flarum actor; throttled by Flarum's standard per-actor API throttler. ## License MIT — see [LICENSE](LICENSE).

A World of Warcraft armory for Flarum 2. Members sign in

with Battle.net, and the extension pulls their characters straight from the

Blizzard API — gear with hover tooltips, stats, talents, Mythic+/raid progress,

professions, PvP ratings, reputations and collections — on a tabbed, theme-aware

character page that looks at home in light or dark mode.

Free and open source (MIT). The companion Convoro build

shares the same data engine.

Features

• Battle.net OAuth — one click to connect; characters sync automatically.

• Full character page at /armory with tabs:

  • Gear — every slot with a big 3D character render and Wowhead-style item tooltips (item level, stats, sockets, set bonuses, sell price).

  • Stats — primary + secondary stats, defenses and resources.

  • Talents — active spec, talents, and the in-game loadout import string.

  • PvE — Mythic+ rating and best weekly runs, plus raid progress.

  • Professions — primary and secondary, with tier skill.

  • PvP — honor level and rated 2v2 / 3v3 / RBG ratings.

  • Reputations and Achievements / Collections (points, mounts, pets).

• Roster sidebar to switch between your characters; pick a main, hide alts.

• Role-Play tie-in — if ernestdefoe/roleplay is installed, an Add to Role-Play button imports a WoW character as a playable Role-Play character: a combat sheet (HP + might/agility/wits/heart scaled from item level and primary stats) plus a deck of signature class ability cards whose damage dice scale with item level. Re-run after a gear upgrade to rescale.

• Theme-aware — colors follow your forum's light/dark scheme.

• Caching — character data is cached so the page stays fast and stays well

  under Blizzard's rate limits.

Setup

1. Install:

   
   php flarum migrate
   php flarum cache:clear   ```

2. Create a Battle.net API client at

   develop.battle.net/access/clients.

   Set the Redirect URL to https://YOUR-FORUM/auth/battlenet/callback.

3. In Admin → Armory, paste the Client ID and Client Secret, and

   choose your default region (Americas / Europe / Korea / Taiwan).

4. Members open Armory from the navigation and click Connect Battle.net.

How it works

Public character data (gear, stats, raids, …) is fetched with an app-level

client-credentials token, so refreshes never require the member to sign in

again. The member's wow.profile token is used only once — to discover which

characters belong to them.

License

MIT © ernestdefoe

Automated, rules-based discussion housekeeping for Flarum 2.

Define rules that periodically look inside chosen tags for discussions matching

conditions (age, tags, reply count) and then hide, lock, retag / move,

or delete them — so a busy section keeps itself tidy without manual moderator

work.

Inspired by the "auto-archive old/prefixed threads" plugins from other forum

software, rebuilt the Flarum way (tags instead of forum IDs).

Features

• Rules — each rule has a scope (one or more tags, or all), conditions,

  an action, and its own run frequency.

• Conditions — inactive/created for N days, also has / doesn't have certain

  tags, minimum / maximum replies.

• Actions — hide, lock, unlock, add tag, remove tag, move (retag), or

  permanently delete.

• Scheduler — due rules run automatically; you can also Run or

  Preview any rule on demand from the admin page.

• Global dry-run — preview everything: rules log what they would do and

  change nothing. Flip it off when you're confident.

• Audit-log friendly — every live action dispatches the matching Flarum

  domain event (Hidden, Deleted, tag/lock events), so audit-log /

  action-log extensions record Janitor's actions automatically, attributed to an

  admin. (Dry-run previews never emit them.)

• Safety — stickied and locked discussions are protected by default, every

  run is capped (default 100 actions), permanent delete is opt-in per rule, and

  every (would-be) action is written to an action log. A rule can opt in to

  include locked (e.g. archiving closed-and-locked sale threads) or

  include stickied discussions when that's exactly what it's for; the

  Unlock action always includes locked discussions.

• Every condition is optional — a rule can match on tags alone (no

  inactivity needed), on inactivity alone, or any combination.

Install

php flarum migrate
php flarum cache:clear```

Then enable **Janitor** in the admin panel and open its settings to add rules.

## Requirements: the scheduler

Janitor's automatic runs rely on Flarum's task scheduler, so your server must run

this cron entry (once a minute):

```* * * * * cd /path/to/forum && php flarum schedule:run >> /dev/null 2>&1```

Without it, rules won't run on their own — but the **Run** / **Preview** buttons

on the settings page work regardless, and are the safest way to try a rule first.

## Tips

* Start with **Global dry-run** on and use **Preview** to see exactly which

  discussions a rule would hit (check the action log) before letting it act.
* Prefer **Hide** or **Move** over **Delete** — hidden discussions can be

  restored; deletion can't.
* "Inactive for N days" measures last activity by default — ideal for archiving

  stale threads in a busy tag.

## License

[MIT](https://github.com/ernestdefoe/janitor/blob/main/LICENSE.md) © ernestdefoe

A Flarum 2 extension. Adds Run Migrations and Publish Assets to the admin dashboard's tools menu — right beside Clear Cache, System Info and Toggle Advanced Page — so you can finish an extension install or update without ever opening a terminal.

Features

• Run Migrations — the in-process equivalent of php flarum migrate: runs outstanding core and extension migrations, then reloads the admin so everything picks up the changes.

• Publish Assets — the equivalent of php flarum assets:publish: republishes core fonts and every enabled extension's assets.

• Admin-only (both endpoints reject non-admins), and each run reports exactly what it did.

• Perfect companion to the Extension Manager on shared hosting.

• Fully translatable.

Installation

php flarum cache:clear```

## Updating

```composer update ernestdefoe/maintenance
php flarum cache:clear```

## Links

* [Packagist](https://packagist.org/packages/ernestdefoe/maintenance)
* [GitHub](https://github.com/ernestdefoe/maintenance)

A full-featured, free calendar & events extension for Flarum 2. Month and

list views, RSVPs, colour-coded categories, recurring events, cover images, a

proper iCal feed, one-click Google Calendar export, and a drop-anywhere

Upcoming Events widget that looks right on the default theme — and integrates

natively with Bespoke and

Page Builder.

Built to feel premium. Priced at free.

Features

• 🗓️ Month, Week, Day & list views with quick prev / today / next navigation.

  Week/Day are true time grids with hour lines, a live "now" indicator, side-by-side

  overlapping events, and double-click-to-create at the clicked time slot.

• 📍 Location on every event, rendered as a one-tap Google Maps link.

• 🔁 Recurring events (daily / weekly / monthly / yearly) via standard RRULE,

  expanded on the fly so each occurrence shows on the right day.

• ✅ RSVP — members mark themselves Going or Interested, with live counts.

• 🎨 Categories with colours — filter the calendar and give each event a

  coloured accent. Managed from a dedicated admin panel with a colour picker.

• 🖼️ Cover image per event — paste a URL, or upload a file directly when

  FoF Upload is installed (auto-detected;

  falls back to a URL field otherwise).

• 📅 iCal export — a subscribable feed.ics for the whole calendar plus a

  per-event .ics download (RFC 5545, proper escaping & folding).

• 🟦 Google Calendar — "Add to Google Calendar" deep-links with title, time,

  description and location pre-filled.

• 💬 Optional discussion thread per event (hybrid model) so members can

  comment using Flarum's native discussion UI.

• 🧩 Upcoming Events widget — works standalone on the default theme, and

  registers as a first-class widget/block in Bespoke and Page Builder.

• 🌓 Theme-aware — every colour resolves through Flarum's own CSS variables,

  so it looks correct in light & dark and on custom themes out of the box.

• 🔐 Permissions — separate "create events" and "manage all events" controls.

Installation

php flarum migrate
php flarum cache:clear```

Then open **Admin → Calendar** to configure it.

## Updating

```composer update ernestdefoe/calendar
php flarum migrate
php flarum cache:clear```

## Configuration

**Admin → Calendar** gives you:

| Setting | What it does |

| --- | --- |

| **Default view** | Month grid or upcoming list when the calendar opens. |

| **Week starts on** | Sunday or Monday. |

| **Index widget** | Show an "Upcoming events" widget on the forum index. |

| **Widget count** | How many upcoming events the widget lists. |

| **Link discussion** | Auto-create a discussion thread for each new event (for comments). |

| **Categories** | Add / rename / recolour / delete colour-coded categories. |

Two permissions are added under **Admin → Permissions**:

* **Create calendar events** — who can add events.
* **Manage all calendar events** — who can edit/delete events they don't own.

## The Upcoming Events widget

The widget is a self-contained component, so it shows up automatically wherever

your theme supports it:

* **Default theme** — appears in the index sidebar (toggle in admin).
* **Bespoke** — available in the widget tray as **Upcoming events**.
* **Page Builder** — available as an **Events** block.

## Calendar subscription (iCal)

Every calendar exposes a subscribable feed at:

```https://your-forum.example/calendar/feed.ics```

Paste that URL into Google Calendar (*Other calendars → From URL*), Apple

Calendar (*File → New Calendar Subscription*), or Outlook to keep events in sync.

Each event also has its own `.ics` download and an "Add to Google Calendar" link.

## How events are modelled

Events are their own records (title, time, location, recurrence, etc.). When

**Link discussion** is enabled, creating an event also spins up a normal Flarum

discussion linked to it, so comments, mentions, likes and notifications all work

exactly as members expect — no parallel comment system to learn.

## Compatibility

* Flarum `^2.0`
* PHP `^8.3`
* No required third-party extensions. Plays nicely with Bespoke & Page Builder

  when present, and degrades gracefully when they aren't.
* **Optional:** [FoF Upload](https://github.com/FriendsOfFlarum/upload) — enables

  drag-free file uploads for event cover images.

## Contributing

Issues and PRs welcome. To build the front-end locally:

```cd js
npm install
npm run dev      # watch
npm run build    # production```

## License

[MIT](https://github.com/ernestdefoe/calendar/blob/main/LICENSE) © ernestdefoe

Bring live video into your community. Members go live from YouTube or Twitch,

and a LIVE NOW badge follows their avatar everywhere it appears — posts, the

discussion list, mentions, the header, the sidebar.

Free / MIT. The optional premium add-on OnAir+

turns your forum into the whole platform — a built-in RTMP server (stream straight in

from OBS), in‑forum HLS playback, multistream, VOD, live chat, go‑live notifications and

scheduled streams. See the comparison below.

Features

• 🔴 LIVE badge on every avatar — one Avatar override lights a streamer up everywhere.

• ▶️ YouTube + Twitch embed viewer — paste a channel/video URL and go live.

• 📡 Presence with graceful fallback — uses flarum/realtime for instant badge

  updates when installed, transparently falls back to lightweight polling when it isn't.

• 🟥 Live Now widget + a /onair directory — see who's streaming at a glance.

• 🔐 Permissions + admin settings — who can go live, default provider, poll interval.

• ⏱️ Stale‑stream reaper — auto‑ends streams left running.

The Live directory

OnAir vs OnAir+

OnAir (this extension) is free and complete on its own for YouTube/Twitch streamers.

OnAir+ is a paid add‑on for communities that want to host streaming themselves.

| | OnAir (free) | OnAir+ |

|---|:---:|:---:|

| LIVE badge on avatar, everywhere | ✅ | ✅ |

| Live Now widget + /onair directory | ✅ | ✅ |

| YouTube embed viewer | ✅ | ✅ |

| Twitch embed viewer | ✅ | ✅ |

| Realtime presence + polling fallback | ✅ | ✅ |

| Permissions + admin settings | ✅ | ✅ |

| Auto‑end stale streams | ✅ | ✅ |

| Built‑in RTMP server → in‑forum HLS | — | ✅ |

| Stream keys + creator studio | — | ✅ |

| Multistream / restream to YouTube + Twitch | — | ✅ |

| VOD recordings | — | ✅ |

| Live chat overlay | — | ✅ |

| Go‑live notifications + follow a streamer | — | ✅ |

| Scheduled streams + reminders | — | ✅ |

| Concurrent viewer counts | — | ✅ |

OnAir+ — stream straight into the forum

Members broadcast from OBS to your own server; viewers watch an hls.js player inline,

with live chat beside it.

OnAir+ — creator studio

Each streamer gets an ingest URL, a secret stream key, multistream targets, and a one‑click

key reset.

Install

composer require ernestdefoe/onair

Then enable OnAir in the admin panel. Optionally install flarum/realtime for

instant (push) LIVE badges — OnAir detects it automatically. For self‑hosted streaming,

add OnAir+ (composer require ernestdefoe/onair-pro).

Development

npm install
npm run build      # or: npm run dev  (watch)```

A no‑backend concept render of the whole product lives in `preview/index.html`.

## Architecture notes

* **LIVE badge:** overrides the shared `Avatar` component (main‑bundle, safe to extend at

  init) and reads a serializer‑supplied `user.isLive()`.
* **Presence transport:** `app.onair.presence` picks `RealtimeTransport` when

  `flarum/realtime` is detected, else `PollingTransport`; both expose the same API.
* **Providers:** `app.onair.providers` (JS) + the `StreamProvider` interface (PHP) are the

  extension points **OnAir+** plugs its RTMP/HLS provider into.

## License

MIT © Ernestdefoe

Play a character, post in-character, and run a card-based tactical game — right inside your Flarum discussions.

Role-Play turns an ordinary Flarum forum into a home for tabletop-style play. Members create characters, write posts as those characters, and storytellers can run full turn-based combat encounters — with dice, cards, initiative and live HP bars — without anyone leaving the thread.

It touches no core tables (everything lives in its own rp_* tables) and is free and MIT-licensed.

Three features, one extension

🎭 Characters

Members manage their cast at /characters ("My Characters" in the account menu): a name, an accent colour, an optional avatar and bio. Characters are yours; archive them any time and their old posts keep their identity.

💬 Post in-character

When replying, pick "Post as …" in the composer and your reply is authored as that character — its coloured badge and name replace your own, with a quiet "Played by you" underneath so nothing is hidden. Perfect for narrative threads where several people each speak as their characters.

⚔️ A tactical card game

This is where Role-Play goes further than any other Flarum RP add-on. Build a deck of cards, then run encounters — turn-based fights that play out live in the discussion sidebar.

The deck builder

At /deck ("My Deck" in the account menu) each member crafts cards — abilities, items, spells and enemies — each with dice formulas the game engine actually rolls:

• Attack roll (e.g. 1d20+5) — checked against the target's defense

• Damage roll (e.g. 3d6) — applied on a hit, doubled on a natural-max crit

• Optional defense, HP, cost, a Font Awesome icon, and a description

• Mark a card public to share it into everyone's deck

Dice expressions are validated server-side — a malformed formula is rejected, never silently ignored.

Running an encounter

Any member can start an encounter inside a discussion and becomes its storyteller (GM). From the tracker in the sidebar you:

1. Build the field — add party members and foes by hand, spawn a foe straight from an enemy card (its HP and defense seed automatically), and let players join with one of their own characters.

2. Roll initiative & start — every combatant rolls 1d20 + agility; the tracker sorts them into turn order.

3. Play it out — on each turn the active combatant plays a card at a target. The engine rolls to-hit vs. defense, rolls damage on a hit (×2 on a crit), and updates HP. A rolling action log narrates every play — hits, misses and crits.

4. Advance until one side is down — a Victory / Defeat banner appears, and the GM ends the encounter.

The tracker shows the initiative order, colour-coded HP bars (green party / red foes), the active turn, and adapts its controls to who's looking — the GM drives the fight; a player only acts on their own character's turn.

Live for the whole table

When flarum/realtime is installed, every play, turn and HP change is broadcast over WebSocket — the whole table sees the fight update instantly, no refresh. Without realtime, the tracker falls back to a lightweight poll, so it still stays in sync.

Installation

php flarum cache:clear```

That's it — the six `rp_*` tables are created automatically on enable. Then:

* Members find **My Characters** and **My Deck** in their account menu.
* Anyone can start an encounter from a discussion's sidebar.
* For instant multi-viewer combat, install and configure **flarum/realtime** (optional).

### Requirements

* Flarum **2.0+**
* PHP 8.1+
* *(Optional)* flarum/realtime for live updates

---

## How the dice work

The engine (`src/Game.php`) is a small, pure core:

| Step | Rule |

|------|------|

| **Dice** | Any `XdY+Z` expression, e.g. `2d6+1`, `1d20`, `3d8-2` |

| **Initiative** | `1d20 + agility`, highest goes first |

| **To-hit** | Attack total ≥ target defense (defense `0` = always hits) |

| **Crit** | A natural maximum on any attack die → **double damage** |

| **Down** | A combatant at `0` HP is out; turns skip them |

---

## Building from source

The PHP runs as-is; the front-end compiles with the Flarum webpack toolchain:

```cd js
npm install
npm run build```

---

## License

[MIT](https://github.com/ernestdefoe/roleplay/blob/master/LICENSE) © Ernest Defoe. Free to use, fork and build on.

A GDPR / ePrivacy-style cookie consent extension for Flarum 2. Free and MIT-licensed.

Shows a clean cookie notice with Accept / Reject / Customize, and a granular Privacy Settings dialog with consent categories and a per-service transparency view — and, crucially, it can gate third-party scripts so they only load after consent.

Features

• Cookie notice banner (bottom bar, corner box, or centered) with Accept, Reject and Customize, plus your Privacy Notice link.

• Granular Privacy Settings modal — per-category toggles (Necessary is always on) with expandable detail, plus a Services tab listing the third-party services and cookies in each category.

• Script gating — two ways to ensure tags only run after consent:

  • Paste scripts per category in the admin panel; they load when that category is accepted.

  • Mark any script on the page as <script type="text/plain" data-cc-category="marketing">…</script> and it activates on consent.

• Admin-defined categories (rename, add, remove, mark required) — defaults: Necessary, Performance, Functional, Marketing.

• Consent versioning — bump the version to re-prompt everyone when your policy changes.

• Do Not Track / Global Privacy Control — optionally auto-reject non-essential categories when the browser sends an opt-out signal.

• Fully stylable — layout (bottom bar / corner box / centered), light / dark / auto theme, custom accent colour, box width and corner radius, so it fits any site and screen size.

• Reopen anytime — a "Cookie settings" link, plus a JS API so a theme can place its own trigger.

• Fully translatable; consent is stored locally (no personal data leaves the browser).

Screenshots

| Cookie notice | Privacy settings |

| --- | --- |

| | |

Fully stylable so it fits any forum — choose the layout (bottom bar / corner box / centered), a light/dark/auto theme, your own accent colour, box width and corner radius:

JavaScript API

window.cookieConsent.accepted('marketing'); // boolean
window.cookieConsent.onChange((c) => { /* … */ });
window.cookieConsent.acceptAll();
window.cookieConsent.rejectAll();```

## Installation

```composer require ernestdefoe/advanced-cookie-consent
php flarum cache:clear```

Then open **Admin → Advanced Cookie Consent** to set your text, categories and scripts.

## License

[MIT](https://github.com/ernestdefoe/advanced-cookie-consent/blob/main/LICENSE)

Use any Google Font on your Flarum 2 forum. Pick a body font and a heading

font from the full Google Fonts library — applied site-wide, with a live preview

right in the admin panel.

Features

• 🔎 Searchable picker for a curated list of popular Google Fonts, in the

  admin settings — and you can type/paste any Google Font family name, even

  ones not in the list.

• ✍️ Separate body and heading fonts, so you can pair (e.g.) Inter body

  text with Playfair Display headings.

• 👀 Live preview of each font directly in the admin panel.

• ⚡ Server-side injection of the Google Fonts stylesheet into the page

  <head> — no flash of unstyled text, no client round-trip.

• 🪶 No configuration files, no API key required.

Installation

composer require ernestdefoe/google-fonts

Then enable Google Fonts in your admin panel.

Usage

1. Go to Admin → Google Fonts.

2. Set a Body font and (optionally) a Heading font.

3. Start typing to search, or paste an exact family name from

   fonts.google.com.

4. Click Save. The fonts apply to your forum immediately.

Leave a field blank to fall back to your theme's default font.

Updating

php flarum cache:clear```

## License

[MIT](https://github.com/ernestdefoe/google-fonts/blob/main/LICENSE)

A live FBS college football scores ticker for Flarum 2 forums, powered by the free public ESPN API. Scores scroll automatically across a sticky banner at the top (or bottom) of your forum, updating on a configurable interval.

Features

• 🏈 FBS-only — filters ESPN's API to Group 80 (NCAA Division I FBS)

• 📡 Live scores with a pulsing green dot for in-progress games

• 🏆 AP/Coaches rankings — shows #N next to ranked teams (Top 25)

• 🖼️ Team logos pulled directly from ESPN's CDN

• ⚙️ Admin settings — toggle on/off, top/bottom position, refresh interval, scroll speed

• 📱 Responsive — logos hidden on narrow screens to keep ticker readable

• 🔁 Seamless loop — CSS-only marquee with no layout jank

• ♻️ Auto-refresh — polls ESPN API on a configurable interval (default 60s)

Requirements

• Flarum ^2.0

• PHP ^8.3

• No external PHP dependencies

Installation

composer require ernestdefoe/espn-cfb-ticker

Then enable the extension in your Flarum admin panel under Extensions.

Building JavaScript

If you're contributing or modifying the extension:

npm install
npm run build   # production build
npm run dev     # watch mode```

---

## Admin Settings

| Setting | Default | Description |

|---|---|---|

| Enable Ticker | `true` | Show/hide the ticker sitewide |

| Position | `top` | Sticky top or fixed bottom |

| Refresh Interval | `60` seconds | How often to poll ESPN API (min 15s) |

| Scroll Speed | `40` | Per-game animation multiplier (lower = faster) |

---

## How It Works

1. On page load the extension mounts a Mithril component outside Flarum's main app node.
2. The component `fetch()`es `https://site.api.espn.com/apis/site/v2/sports/football/college-football/scoreboard?groups=80&limit=50` — the public ESPN API, no key required.
3. Games are rendered in a CSS `@keyframes` scroll animation. The track is duplicated so the loop is seamless.
4. A `setInterval` re-fetches on the configured interval, causing a Mithril redraw.

---

## ESPN API Notes

The ESPN public scoreboard API (`site.api.espn.com`) is unofficial and undocumented but has been widely used by developers for years. It requires no API key and returns JSON. The `groups=80` parameter restricts results to FBS schools.

---

## License

[MIT](https://github.com/ernestdefoe/espn-cfb-ticker/blob/main/LICENSE) © 2026 ernestdefoe

<https://ernestdefoe.online/extension/ernestdefoe/espn-cfb-ticker>

A small, theme-agnostic day/night/system picker for the Flarum 2 header. Drops into any Flarum 2 theme that respects the native <html data-theme="…"> signal (every theme that ships with or extends Flarum 2 does, including the default).

Screenshots

Desktop — header button

A compact icon button next to Search / Sign Up / Log In. The icon reflects the active choice (☾ dark, ☀ light, ◐ system).

Desktop — dropdown open

Five choices, each with a matching icon. The active choice is marked with a checkmark.

Mobile — slide-out drawer

On phone-width viewports Flarum re-renders HeaderSecondary inside .App-drawer. The button switches to a labeled, full-width menu row so it lines up with Search / Sign Up / Log In.

Features

• Five choices. Dark, Dark (high contrast), Light, Light (high contrast), System.

• Native Flarum 2 signal. The extension only flips <html data-theme="…"> and localStorage — no theme-specific CSS, so it composes with any well-behaved Flarum 2 theme (default, Aurora, or any third-party theme).

• System mode honours OS preferences. When System is active, the theme follows prefers-color-scheme for light/dark and prefers-contrast: more for the -hc variants — so an accessibility user with macOS / Windows "Increase contrast" turned on automatically gets the right palette.

• Live OS updates. Changes to the OS theme or contrast preference are picked up immediately while the tab is open, with no reload.

• Persists per visitor. Your choice is stored in localStorage under ernestdefoe-theme-toggle.choice and re-applied on every page load before paint, so there's no FOUC.

• Respects the admin default. Until a visitor explicitly picks a choice, Flarum's Admin → Appearance → Color Scheme setting is left untouched.

• Mobile-aware UI. Renders as a compact icon button in the desktop header and as a labeled "◐ Theme" row inside the mobile slide-out drawer (where icon-only buttons would float disconnected from the surrounding Sign Up / Log In rows).

• Localized. All visible strings come from locale/en.yml and can be overridden in your forum's locale files.

• TypeScript end-to-end. Sources are authored in TypeScript and type-checked against Flarum core's bundled .d.ts files. npm run check-typings runs tsc --noEmit.

Compatibility

• Flarum core ^2.0

• PHP ^8.3

• Pairs with any theme. Tested with the default theme and the Aurora theme.

Install

php flarum cache:clear```

Then enable **Theme Toggle** from the admin panel's Extensions page.

## Development

```cd js
npm install
npm run build           # production bundle (writes js/dist/forum.js)
npm run dev             # watch mode for development
npm run check-typings   # tsc --noEmit, requires `composer install` at repo root first```

The TypeScript path mapping in `js/tsconfig.json` points at `../vendor/flarum/core/js/dist-typings/`, so `composer install` at the repo root must run before `check-typings` can resolve `flarum/*` imports.

### Project layout

```extend.php                                Flarum extension bootstrap
composer.json                             Package manifest
locale/en.yml                             User-facing strings
less/forum.less                           Header + drawer styling
js/
  forum.ts                                Webpack entry point
  tsconfig.json                           Extends flarum-tsconfig
  src/forum/
    index.ts                              Initializer + HeaderSecondary hook
    theme.ts                              Choice/storage helpers + media listener
    components/ThemeToggle.tsx            The Dropdown component
  dist/forum.js                           Compiled bundle (committed)
screenshots/                              Images in this README```

## How it works

Flarum 2 ships four `data-theme` values: `light`, `light-hc`, `dark`, and `dark-hc`. Themes are expected to define their dark tokens as the default and their light tokens under `[data-theme^='light']`, with a high-contrast layer under `[data-theme^='light-hc']` / `[data-theme^='dark-hc']`. Because those selectors use `^=` (prefix match), setting `data-theme="light-hc"` activates *both* the regular light palette and its HC overrides via the cascade.

This extension just sets that attribute client-side:

* On boot, `theme.ts` reads the saved choice from `localStorage` and writes the corresponding string to `<html data-theme="…">` **before** the initializer runs, so the page never paints in the wrong palette.
* The `ThemeToggle` component reads the same choice for its icon and dropdown state.
* When the user picks a new option, the choice is written to `localStorage`, `<html>` is updated, and Mithril redraws the button.
* In System mode, a `matchMedia` listener for `prefers-color-scheme` and `prefers-contrast: more` re-applies the choice live.

No theme-specific CSS, no setting payload, no server round-trip.

## Translations

Override any string by adding the matching key under `ernestdefoe-theme-toggle.forum.toggle.*` in your forum's locale file:

| Key                       | Default                  |

| ------------------------- | ------------------------ |

| `label`                   | `Theme`                  |

| `option_dark`             | `Dark`                   |

| `option_dark_hc`          | `Dark (high contrast)`   |

| `option_light`            | `Light`                  |

| `option_light_hc`         | `Light (high contrast)`  |

| `option_system`           | `System`                 |

## License

[MIT](https://github.com/ernestdefoe/theme-toggle/blob/main/LICENSE) © Ernest Defoe

An aurora-inspired theme for Flarum featuring animated

gradient backdrops, glassmorphic panels, glowing accents, and a dark night-sky

palette.

Flarum 1.x users: this branch targets Flarum 2.0. For Flarum 1.8.x see the

1.x branch.

Screenshots

Forum index

Animated aurora backdrop, glassmorphic discussion cards, gradient text on unread titles,

a glowing pill for unread counts, stat widgets inside the welcome hero, and the

user-facing palette picker popover (shown open).

Discussion view

Glassy posts with gradient usernames, accent-bordered blockquotes, themed inline code

and code blocks, and gradient-glow avatars.

Admin settings

Live color swatches, a gradient preview, and toggles for glassmorphism, glow, and

background animation.

Highlights

• Animated aurora backdrop — drifting radial gradients in violet, cyan,

  teal, pink, and magenta on a deep night-sky base.

• User palette picker — a circular gradient button in the header opens a

  popover with six presets (Aurora, Sunset, Ocean, Forest, Nebula, Ember).

  Choice persists per-visitor via localStorage and applies instantly.

• Hero widgets — Members, Discussions, Posts, and Online-now stat tiles

  embedded inside the welcome hero, with live trend lines.

• Glassmorphic surfaces — frosted header, sidebar, discussion cards,

  composer, modals, and dropdowns.

• Gradient buttons & badges — primary buttons shimmer; unread counts pulse

  with a cool glow.

• Glowing avatars & focus rings — soft cyan/pink halos on hover and focus.

• Gradient scrollbar & text — gradient-clipped headings, usernames, and

  scrollbar thumb.

• Configurable — admin settings for gradient colors, accent color, and

  toggles for glassmorphism, glow, and background animation.

• Accessible — honors prefers-reduced-motion, visible focus rings.

Palette presets

| Preset | Gradient |

| ------- | -------------------------------------------------------- |

| Aurora | #7c3aed → #4f46e5 → #22d3ee → #14b8a6 (default) |

| Sunset | #f97316 → #f43f5e → #d946ef → #7c3aed |

| Ocean | #1e40af → #3b82f6 → #06b6d4 → #22d3ee |

| Forest | #15803d → #10b981 → #22d3ee → #0ea5e9 |

| Nebula | #a855f7 → #d946ef → #6366f1 → #3b82f6 |

| Ember | #b91c1c → #ea580c → #f59e0b → #fbbf24 |

Add or override a preset by extending PALETTES in js/src/forum/palettes.js.

Installation

composer require ernestdefoe/aurora

Then enable Aurora Theme under Admin → Extensions.

Configuration

Open Admin → Extensions → Aurora Theme to customize:

| Setting | Default | Description |

| --- | --- | --- |

| Primary gradient — start | #7c3aed | First color of the primary gradient. |

| Primary gradient — end | #22d3ee | Last color of the primary gradient. |

| Accent color | #f472b6 | Warm accent used for hover halos. |

| Enable glassmorphism | on | Frosted-glass panels with backdrop blur. |

| Enable glow effects | on | Soft glows on hover, focus, and unread items. |

| Animate aurora background | on | Drifting gradient blobs in the backdrop. |

Development

cd aurora/js
npm install
npm run build      # production bundle
npm run dev        # watch mode```

### Project layout

```extend.php              Flarum extension bootstrap
composer.json           Package manifest
less/
  forum.less            Forum-facing styles
  admin.less            Admin-facing styles
  variables.less        Color palette, radii, easings
  mixins.less           .aurora-glass, .aurora-text-gradient, ...
  animations.less       drift, shimmer, pulse, float, fade-up
js/
  forum.js, admin.js          Webpack entry points
  src/forum/index.js          Frontend bootstrap: settings, scroll header, ripple
  src/forum/palettes.js       Palette presets + apply/load/store helpers
  src/forum/palette-picker.js Header button + popover injection
  src/forum/hero-widgets.js   Welcome-hero stat tiles
  src/admin/index.js          Admin entrypoint (re-exports extend)
  src/admin/extend.js         Flarum 2 Admin extender — settings registry
  dist/                       Compiled bundles (committed)
resources/locale/
  en.yml                English admin strings```

## Compatibility

* Flarum core `^2.0.0-beta` (built against `2.0.0-rc.1`)
* PHP `^8.3`
* Modern browsers with `backdrop-filter` support. Older browsers gracefully

  degrade to solid dark surfaces.

Need Flarum 1.x? Switch to the `1.x`

branch — it targets `flarum/core ^1.8.0` and uses the legacy `app.extensionData`

settings API.

## License

[MIT](https://github.com/ernestdefoe/aurora/blob/main/LICENSE) © Ernest Defoe