Tags Laravel Package

Product Decisions This Supports

• Community platform selection (build vs. buy). This package is the tagging module of Flarum, a PHP/Laravel-component-based forum. Adopting it is not a library decision — it is a decision to run Flarum as your community platform. Frame it that way in any roadmap discussion.
• Information architecture and content taxonomy. Tags are Flarum's primary mechanism for organizing discussions (tags, secondary tags, tag-scoped feeds/pages). This directly informs how you model categories, navigation, and discovery in a community product.
• Permissions and moderation model. The tags extension is the basis for tag-scoped visibility and moderation (restricting who can see or post in a tag). This supports decisions about gated communities, partner/private forums, and delegated moderation without building a custom ACL layer.
• Feature scoping for a community MVP. If your roadmap includes "categorize discussions," "segment audiences," or "delegate moderation," this is a built-in capability rather than a build item — it removes work from the backlog and shifts effort to configuration and migration.
• Ecosystem and exit-risk assessment. Because this is a read-only subtree split of the Flarum monorepo, it signals that the canonical code, issues, and contribution path live upstream. That is a dependency-governance input, not just an engineering detail.

When to Consider This Package

Consider it when:

• You are already running, or evaluating, Flarum and need discussion categorization — in that context this is the first-party, expected choice, not a third-party gamble.
• You need tag-based permissions or moderation delegation and want it without custom development.
• You want MIT-licensed, zero-licensing-cost functionality from the platform's own maintainers.
• You are doing a platform bake-off and need to know whether Flarum covers taxonomy/permissions out of the box (it does).

Look elsewhere — or stop — when:

• You are building a Laravel application, not a Flarum forum. Despite the Laravel/PHP framing, this is a Flarum extension using Flarum's extension APIs. It is not a general-purpose Laravel tagging package (compare: spatie/laravel-tags) and cannot be dropped into an arbitrary Laravel app.
• You need a standalone, independently maintained dependency. A read-only subtree split is a distribution artifact; issues, PRs, and versioning are governed upstream. Do not plan to fork or patch it locally without accepting ongoing merge burden.
• Your taxonomy needs exceed simple tags — deep hierarchies, multi-tenant scoping, or complex relational content models are better served by a bespoke or headless approach.
• You need an API-first/headless content model where Flarum's forum-shaped API is a constraint rather than an asset.

Two data-quality caveats for the record: the 38 stars materially understate real adoption (they reflect the split repo, not the upstream project), and the 2026-10-18 release date should be verified before it is cited in any planning artifact.

How to Pitch It (Stakeholders)

For executives: This is not a product we buy — it is a feature of a product we would adopt. Flarum's tagging extension gives us discussion categorization, tag-scoped permissions, and delegated moderation with no licensing cost (MIT) and no custom build. The real decision on the table is whether Flarum is our community platform; if it is, tagging is included, not procured.

For engineering: Treat this as a first-party Flarum module, not a Laravel dependency. It is a read-only subtree split of the upstream monorepo — pin the upstream package, route issues and patches upstream, and don't plan local forks. Integration effort is configuration and data migration, not code.

Bottom line / recommendation: Low direct cost, low integration risk if Flarum is the platform. If the requirement is tagging inside a bespoke Laravel app, this is the wrong tool — evaluate a dedicated Laravel tagging library instead. Recommend deciding the platform question first, then treating tags as a configuration task rather than a build-or-buy line item.