Page Builder Page Builder for Flarum 2 Table of contentsFeatures The section builder Section reference Pricing 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 FeaturesSection builder — assemble a page from 12 pre‑designed sections that drop in already styled to your forum. Pick, reorder, click any text to edit it in place, and nudge a few friendly knobs (background, accent colour, alignment, spacing). You can't make it ugly, and you don't need to know how the look is achieved. Live forum sections — Latest discussions, Newest members, and Articles pull real data straight from your forum and keep themselves current. Nothing to maintain. Follows your theme automatically — sections and the editor read Flarum's own colour variables, so everything tracks light / light‑hc / dark / dark‑hc and uses your forum's primary colour. Zero styling work. Articles, written or promoted — write an article from scratch, or promote any forum discussion into one, and list them anywhere with the Articles section. 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. The section builderThe fastest way to build a page. Go to Pages → New page and you land in a full‑screen editor: your sections on the left, a live preview in the middle, and the settings for whatever you've selected on the right. Add a section and pick from the gallery. Every section arrives already wearing your forum's colours, fonts and corner rounding — there is no separate theme to configure. Edit by clicking. Headlines, body copy, buttons, feature cards, pricing plans, FAQ rows — click the text on the page itself and type. Items can be added and removed from the right‑hand panel. Tweak with guardrails. Each section exposes a small, safe set of controls: background (Surface, Subtle, Brand tint, Dark, Image), accent colour, alignment, and spacing. Deselect everything and the panel becomes the page's theme. Publish when you're ready with the Draft / Published switch, then hit View page to see it live at /p/your-slug. The public page is rendered by the exact same code as the preview, so what you design is what visitors get. Section referenceSection What it does Hero Headline, sub‑copy and up to two buttons. Optional full‑bleed background photo with an automatic scrim so text stays readable. Feature grid Three cards with an icon, title and description. Icons are any Font Awesome class. Articles Live. Lists your latest articles — both ones you wrote and discussions you promoted — with cover image, excerpt, author and date. Image + text A split section with an uploaded image on either side. Stats band Big numbers with labels. Latest discussions Live. Recent threads from your forum with reply counts, updating on their own. Newest members Live. Recent sign‑ups with avatars. Testimonial A pull quote with an attributed author. Pricing Three plan cards; mark one as the popular plan. Call to action A closing banner with a button. Logo strip A muted "trusted by" row. FAQ A list of questions and answers. Sections marked Live read from your forum and refresh themselves — you place them once and never edit them again. Writing articlesArticles are content‑type records, so they get their own page, comments and SEO. There are two ways to create one, and both end up in the Articles section: Write one — the ✦ Articles button in the editor (or the Write an article button on the Articles section itself) opens a blank article. Promote a discussion — pick any thread from the same dialog and it becomes an article that links back to the original discussion. PricingPage Builder is a premium extension, distributed through Floxum. Access requires an active subscription. Plan Price Covers For all use $10.00 / year Not‑for‑profit and for‑profit sites RequirementsFlarum ^2.0 PHP 8.3+ (matches Flarum 2's minimum) Optional: flarum/tags — required only for the Tag Grid block. Optional: fof/upload — required for image uploads in the page builder and content editors. Without it you can still paste image URLs; the upload button shows a notice telling you to install it. Installationcomposer require ernestdefoe/page-builder php flarum migrate php flarum cache:clearThen enable Page Builder under Admin → Extensions. Quick startOpen Admin → Extensions → Page Builder. Click New page, give it a title, and you're dropped into the designer. Add row → Add block, pick a Hero banner, and edit its heading, background, and buttons. Click Save changes, then Preview. (Optional) Use the Forum homepage card to make your page the site's front page — see Setting a custom homepage. Pages & the block designerA 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 live front‑end editorOpen 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. Block referenceBlock 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 bannersThe 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. 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. Comments on recordsWhen 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 articleTurn any forum discussion into an article from its controls dropdown → Promote to article (admin only). The discussion's title becomes the article title, its first post becomes the body, and the first image in the post becomes the cover. The original discussion is then attached to the new article as its comment thread (and drops out of the forum listing) — and anyone who opens the old discussion is redirected to the article (admins aren't, so they can still manage it). To reverse it, use Demote to discussion on the same dropdown: the article is deleted and the discussion returns to a normal forum discussion (its replies are kept). SEOPage 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 homepageIn Page Builder → Forum homepage, choose the page to use as your front page. Go to Admin → Basics → Home Page and select “Home (Page Builder)”. Your custom page now serves as the forum's landing route (/), Invision‑style. PermissionsPages & 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 APIsRegister a block from any extension: // extend.php (new Ernestdefoe\PageBuilder\Extend\PageBuilderBlock(MyBlock::class)),// forum JSapp.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). LicenseProprietary © Ernest Defoe. A premium paid extension — subscribe on Floxum ($10/year). See LICENSE for terms. For licensing inquiries: ernestdefoe@gmail.com File Information Submitter Ernest Defoe Submitted 07/25/26 Category Flarum View File

Connect for Flarum 2 Connect for Flarum 2 What it doesConnect 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 forumConnect 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. Connecting takes one API key — there's nothing to register with Zapier and no developer account needed. Connect ships its own Zapier integration that every forum shares; because it authenticates per-site (your forum URL + your key), one integration serves everyone. Admin → Connect has an Open Connect on Zapier button that takes you straight there. The in-page Zap builder shown above switches itself on once that integration is listed publicly in Zapier's directory — until then you build Zaps in Zapier itself, with everything else working exactly the same. Prefer Make, n8n, or IFTTT? They all work off the same REST API and webhooks — no Zapier account involved. 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 Connecting Zapier / Make / IFTTT / n8nIn Admin → Connect, create an API key. Give it a label (e.g. Zapier) and the scopes it needs — Read for triggers, Write for actions. Copy the token (ck_…) and secret (cs_…). 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: X-Connect-Signature: sha256=<hex> valid ⇔ signature == 'sha256=' + hmac_sha256(rawRequestBody, keySecret) REST APIAll 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!"}'Installationcomposer require ernestdefoe/connectThen 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 is installed; everything else works on a stock forum. Minting a key from the CLIphp flarum connect:key "My key" --scopes=read,writeRequirementsFlarum ^2.0 PHP ^8.3 A running queue worker (recommended — webhooks and rule actions are queued) LicenseMIT © Ernest Defoe File Information Submitter Ernest Defoe Submitted 07/25/26 Category Flarum View File

Workflows Workflows — when this happens, do thatEvery community has jobs that get done by hand over and over. Tag the posts that mention billing. Message new members after their first post. Add buyers to a group. Push reports into the chat channel your team actually watches. Workflows does them for you. You pick a trigger, add conditions if you need them, and choose what should happen. 27 things to trigger onContent Posted · edited · deleted · hidden, locked or pinned · moved · merged · split · reported Members Registers · validates · logs in · updates their profile · flagged as a spammer · reacts · follows · joins or leaves a club · RSVPs · completes a course Commerce Purchase paid · about to expire · expired · renewed · cancelled Other Poll voted · file downloaded · club created Every one of those is wired to a real Invision Community event and tested on an install with the first-party applications present. The trigger list only ever offers events that genuinely fire — you cannot save a rule that quietly never runs. Conditions, so rules stay preciseForum or category, author's group, post count, account age, content contains text, content matches a pattern, tagged with, title contains, is the first post in a topic. For example: when content is posted, and the author has fewer than 5 posts, and the content matches a URL pattern — hide it and send yourself a webhook. ActionsLock, unlock, pin, unpin, hide, approve, add tags, add or remove a secondary group, award points, award a badge, send a private message, and send a webhook. The webhook action is the important oneAnything your community does can be pushed to Zapier, Make, n8n, or your own code, as JSON. That means Workflows isn't limited to what this application can do — it's the bridge to everything else you already use. Set a signing secret and each request is signed, so the receiving end can tell a genuine call from anyone who guessed the URL. A run log that answers the real questionRules engines fail when you can't tell why a rule didn't fire. Workflows records every evaluation, with the reason: "Forum 'Introductions' is not in the selected list." "Bob has 3 posts; condition was at least 10." "Content does not contain \"refund\"." Filter by matched, skipped or errors, and by rule. Turn skipped logging on while you build a rule and off once it works. Built not to get in the wayNothing blocks posting. Conditions are evaluated inline because they're cheap; actions run on the background queue. A rule pointing at a slow webhook can never make a member wait, and an outage can't stop people posting. Loops are impossible. "When a post is created, post a reply" would take a site down. The engine refuses to re-enter an event it's already handling — that's built into its structure, not a setting you can get wrong. Only sensible options are offered. The builder hides conditions and actions the chosen trigger can't supply, so you're never offered "lock the topic" on a member-registered rule — there isn't one. Actions report what they actually did, not what they attempted — including when Invision Community declines something, and why. Rules run in order, and any rule can stop the ones after it. No core files are edited. Upgrading Invision Community won't break it. RequirementsInvision Community 5.0 or newer (self-hosted), with the Forums application Nothing else. No external service and no API key — unless you use the webhook action, which needs somewhere to send to. Commerce triggers require the Commerce application; club and course triggers require theirs. Everything else works on a stock install. File Information Submitter Ernest Defoe Submitted 07/25/26 Category Members, Security & Admin apps for Invision Community 5 View File

Guardian Guardian — moderation that keeps your team away from the worst of itInvision Community gives you the tools to remove bad content once somebody finds it. Guardian finds it first, ranks it by how bad it is, and puts it in one queue your moderators can actually work through. And for the category of material nobody should have to look at, it does something different: it never shows it to them at all. What it checksPost text — spam, scams and phishing, harassment, hate, threats, and breaches of your rules. Paste your rules in and they are used when judging a post, so "against the rules" means yours rather than a generic idea of them. Attached images — adult content, graphic violence, hate symbols, and images posted purely to advertise. Known illegal material — attachments are matched against a vetted hash service you have arranged access to. Everything is scored from 0 to 100. You choose the score at which something enters the queue, and the score at which it is hidden before a human sees it. One queue, worst firstFlagged content arrives in a single triage screen ordered by severity, with the reason each check gave, the labels it applied, and the post excerpt. Two buttons: Looks fine puts it straight back, Keep hidden leaves it down. Cleared and removed items keep their own tabs so you have a record. Guardian never deletes anything. Content is hidden using Invision Community's own moderation tools, so a wrong call is always reversible — and genuinely illegal material is preserved rather than destroyed, which matters if you later have to account for it. The part that is handled differentlyWhen an attachment matches a known-illegal hash set, Guardian does not treat it as a moderation decision, because it isn't one. The post is hidden immediately and the file is preserved. The queue entry shows no image, no post text, and no link to the content. There is no "view" button. Nobody on your team has to look at it in order to deal with it. The identifying details — account, email, IP at the time of posting, timestamps, file hashes — are captured at the moment of detection, because by the time a report is filed the account may be gone and the IP record rotated away. Clearing it is not offered. A moderator clicking "looks fine to me" is not the right way to overturn a hash match. Reporting, wherever you areReporting duties are national, and the mechanisms differ. Guardian supports both shapes. Destination Region How NCMEC CyberTipline United States Filed directly from your server Internet Watch Foundation United Kingdom Hotline form + reference recorded Cybertip.ca Canada Hotline form + reference recorded eSafety Commissioner Australia Hotline form + reference recorded INHOPE network International Routes you to your national hotline Your own endpoint Any Evidence package posted as JSON Where an API exists, the file goes straight from your server to the destination — never downloaded, never emailed, never handed to a staff member to upload by hand. Guardian submits under your credentials; it never reports under its own identity. Where one doesn't, Guardian links you to the right hotline for your jurisdiction and records the reference number you are given. The evidence is preserved and the audit trail comes out identical either way. Costs you can actually controlA monthly spend limit. When it is reached the paid checks pause — but hash matching keeps running, because that is the one you least want switched off. Separate models for text and images. Image checks are the expensive half; point them at a cheaper model without giving up text checking. Skip established members. Set a post count above which members aren't scanned. New and guest accounts are always checked. This is the single biggest saving on a busy site. Per-forum scope and trusted groups. Staff are always skipped. The settings screen shows exactly what is running, how much you have spent this month, and how many images have been examined. If you already run AI AssistantGuardian works entirely on its own. But if AI Assistant is installed, one switch lets it use that application's provider, key and spend ledger — so you manage one key and one budget instead of two, and spend from both counts against the same limit. It is a convenience, never a dependency. Built to stay out of the wayNothing blocks posting. All checking happens on the background queue. An API outage means posts are unchecked, never that members can't post. Silence is never read as safe. If a check cannot reach its service or the model refuses to assess something, that is recorded as needing a human — not quietly scored as clean. No core files are edited. Upgrading Invision Community will not break it. A full audit trail. Every decision, who made it, and when. RequirementsInvision Community 5.0 or newer (self-hosted), with the Forums application An API key from Anthropic or any OpenAI-compatible provider, for the text and image checks For known-material matching and direct reporting: access to those services in your own name. Providers register with the relevant organisation themselves. File Information Submitter Ernest Defoe Submitted 07/25/26 Category AI & Content apps for Invision Community 5 View File

Tag Colors Tag Colours — your tags, finally telling them apartInvision Community already has tags. What it does not have is any way to make them look like anything. Every tag on your site is the same shape and the same grey, so a topic tagged Solved is visually identical to one tagged Urgent, and members read every label one at a time. Tag Colours fixes that in about a minute. Solved Bug Report Feature Request Announcement Off Topic It builds on the tags you already haveThis is not a replacement tag system. There is nothing to migrate, no second set of labels to maintain, and no new way for your members to tag things. It reads the tags already on your community and lets you pick a colour for each one. Because it works with the built-in system, the colours turn up everywhere tags already appear — topic view, topic lists, search results, tag pages, and the Blogs, Calendar and Pages applications too. Setting it upThe admin screen lists every tag actually in use on your community, most-used first, with a note of how many items carry it. Click a tag, pick a colour, done. Or click Colour them for me and every uncoloured tag is given a distinct colour from a readable palette — a sensible starting point you can then adjust. It never overwrites a colour you chose yourself, and it will not hand two tags the same colour. Three stylesSolid — the tag is filled with your colour Soft — a tinted background with coloured text, for a lighter touch Outline — a coloured border and text on a transparent background Pick one and it applies to every coloured tag, so your tags stay consistent with each other whatever your theme looks like. Readable by defaultChoose a tag colour and the text colour is worked out for you, using the same contrast maths the accessibility guidelines use — dark text on light colours, light text on dark ones. You never end up with a yellow tag nobody can read. If you want to override it on a particular tag, you can. Built to stay out of the wayNo core files are edited and no templates are overridden, so upgrading Invision Community will not break it and will not undo your work. One small stylesheet is added to the page, cached permanently by the browser and only re-fetched when you actually change a colour. There is no JavaScript and no per-page work. Turning it off restores your theme's own tag styling immediately — and keeps your colour choices, so turning it back on picks up where you left off. Uninstalling leaves no trace. Your tags are Invision Community's tags; only the colours belong to this application. RequirementsInvision Community 5.0 or newer (self-hosted) Nothing else — no external service, no API key, no background jobs File Information Submitter Ernest Defoe Submitted 07/25/26 Category Free apps for Invision Community 5 View File