Skip to content
Capell CMS

Diagnostics Credits And Acknowledgements

Diagnostics 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: Developer and operational diagnostics for Capell CMS.

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 Diagnostics builds on.
  • Capell Core supplies the Capell-side contracts, surfaces, or runtime that Diagnostics builds on.

Open-source Packages And Authors

Section titled “Open-source Packages And Authors”
  • Laravel Actions, by Loris Leiva, keeps package behaviour in small action classes instead of burying it in pages, commands, or controllers.
  • Spatie Laravel Data, by Ruben Van Assche and Spatie, keeps request state, settings, and package results typed at the boundaries.

What We Especially Appreciate

Section titled “What We Especially Appreciate”

Diagnostics pays off when something is already broken. It gathers package, cache, queue, migration, and permission state into one admin surface so bug reports can start from evidence.

Keeping This Page Current

Section titled “Keeping This Page Current”

When Diagnostics 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.