Skip to content

Frontend Authoring Credits And Acknowledgements

Frontend Authoring 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: Frontend authoring bridge and in-page editing for Capell frontend

  • 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.
  • Livewire, by Caleb Porzio and the Livewire team, supports interactive admin and frontend behaviour while keeping most of the work close to Laravel and Blade.
  • Blade keeps package views close to Laravel, easy to override, and friendly to theme packages.
  • Tailwind CSS, by Tailwind Labs, gives package themes and frontend views a shared styling language.
  • Vite, by Evan You and the Vite team, keeps package asset builds fast and predictable.
  • 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 Admin supplies the Capell-side contracts, surfaces, or runtime that Frontend Authoring builds on.
  • Capell Frontend supplies the Capell-side contracts, surfaces, or runtime that Frontend Authoring builds on.
  • Spatie Laravel Package Tools, by Freek Van der Herten and Spatie, keeps service provider setup, config publishing, migrations, and command registration predictable.

The package is careful about what it does not render. Admin edit controls are discovered after page load through the beacon, so public cached HTML can stay clean while authoring fixes ship in the package.

When Frontend Authoring 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.