Tags Laravel Package

Product Decisions This Supports

• Content discoverability and taxonomy (roadmap accelerator): Enables tagging of domain entities (e.g., courses, lessons, quiz questions, articles in an EscolaLMS-style product) so catalog browsing, filtering, related-content modules, and search facets can ship without a bespoke taxonomy service.
• Build vs. buy/borrow: Leans toward borrow/reuse — a small, focused Laravel package for polymorphic tagging is cheaper to adopt than designing and maintaining a tagging subsystem in-house, provided the data model and query patterns fit.
• Feature scoping: Supports near-term features such as topic/skill/audience tags on learning content, tag-based catalog filters, “more like this” recommendations, and admin curation workflows.
• Data product decisions: Informs whether tags are first-class product entities (governed vocabulary, moderation, analytics) or lightweight labels; the package is best treated as infrastructure, with governance layered on top if needed.
• Release risk read (0.1.22): This release is test-only maintenance — removal of deprecated methods in tests. No public API changes, no new features, no deprecations affecting consumers, and no migration requirements. It does not change the adoption decision; it is a low-risk patch suitable for routine upgrade. The package remains pre-1.0, so pin versions and monitor changelogs.

When to Consider This Package

Consider it when:

• You are building on Laravel/PHP and want simple, reusable tagging for one or more Eloquent models without introducing an external search or taxonomy service.
• You are already in or integrating with the EscolaLMS ecosystem, where conventions and compatibility align.
• Your tagging needs are flat labels (many-to-many/polymorphic tags) used for filtering, categorization, and admin curation — not complex hierarchies or heavy analytics.
• You want a small dependency surface and are comfortable evaluating pre-1.0 code, pinning versions, and reviewing release notes.
• You need a fast path to a minimum viable taxonomy while deferring investment in a dedicated taxonomy/search platform.

Look elsewhere or plan supplemental work when:

• You require advanced taxonomy: hierarchical/nested tags, synonyms, controlled vocabularies, multilingual tag labels, or tag governance/approval workflows.
• You need high-scale faceted search, analytics, or ranking — pair with a search service (e.g., Meilisearch/Elasticsearch/Algolia) rather than relying on the package alone.
• You operate multi-tenant environments needing per-tenant tag isolation and governance; verify tenant scoping explicitly.
• You need long-term API stability guarantees; pre-1.0 packages can churn. Confirm maintainership activity, license compatibility, and upgrade path.
• You are not on Laravel or require framework-agnostic tagging.

How to Pitch It (Stakeholders)

For executives: We can add content tagging and filtering with a small, low-cost Laravel package instead of building a taxonomy system from scratch. This unlocks faster catalog discovery, related-content features, and admin curation with limited engineering investment. The latest release (0.1.22) is a test-only cleanup — no functional or breaking changes — so risk is minimal. Because the package is pre-1.0, we will pin the version and monitor upgrades.

For engineering: This is a focused Laravel tagging package supporting model tagging for filtering and categorization. Adopt it behind our own service/interface boundary so we can swap it if taxonomy needs grow. Version 0.1.22 only removes deprecated test methods; no API impact. Recommended actions: pin the dependency, add regression tests around tag assignment/querying, and document the upgrade/exit path. If we later need hierarchies, multilingual labels, or faceted search at scale, we layer those on or migrate to a dedicated search/taxonomy service.