Skip to content

Foundation Theme Credits And Acknowledgements

Foundation Theme 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: Capell default theme — ships the standard Tailwind asset pipeline, Blade directives, URL generator, and SVG media component.

  • 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, blocks, forms, tables, actions, and panel integration.
  • 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 Frontend supplies the Capell-side contracts, surfaces, or runtime that Foundation Theme builds on.
  • Spatie Laravel Package Tools, by Freek Van der Herten and Spatie, keeps service provider setup, config publishing, migrations, and command registration predictable.

Foundation Theme is useful because it stays boring on purpose. It gives every theme a known Blade, Tailwind, asset, URL, and media baseline that can be patched once and reused everywhere.

When Foundation Theme 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.