Skip to content
Capell CMS

Tags Credits And Acknowledgements

Tags is part of the Capell package set. This page names the main frameworks, packages, authors, and services this package leans on, with a short note about what they make possible here. It is intentionally shorter than the repository-wide credits page and closer to the package itself.

Package role: Tags for Capell

Shared Foundations

Section titled “Shared Foundations”
  • Laravel, created by Taylor Otwell, gives this package routing, service providers, Eloquent, validation, queues, events, auth, caching, and the normal Laravel testing surface.
  • Filament and the Filament project give this package admin resources, pages, widgets, forms, tables, actions, and panel integration.
  • Composer, Packagist, and GitHub make the package install, split, and release workflow possible. Composer and Packagist deserve a special nod because Capell packages live and update through Composer metadata.
  • Pest, Orchestra Testbench, PHPStan, Larastan, Laravel Pint, and Rector keep this package easier to test, review, and update when bugs are fixed.

Capell Packages Used Here

Section titled “Capell Packages Used Here”
  • Capell Admin supplies the Capell-side contracts, surfaces, or runtime that Tags builds on.
  • Navigation supplies the Capell-side contracts, surfaces, or runtime that Tags builds on.
  • Publishing Studio supplies the Capell-side contracts, surfaces, or runtime that Tags builds on.

Open-source Packages And Authors

Section titled “Open-source Packages And Authors”

What We Especially Appreciate

Section titled “What We Especially Appreciate”

Tags is useful because it wraps an established tag model in Capell context. Filament fields, navigation, and Publishing Studio can all use tags while fixes stay in the tagging package.

Keeping This Page Current

Section titled “Keeping This Page Current”

When Tags adds a new framework, service, or third-party package that becomes part of the user-facing workflow, update this page and the package README together. Credits should explain the practical help we get from a dependency, not just list a package name.