Blog Credits And Acknowledgements
Blog 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: Blog 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, 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 Packages Used Here
Section titled “Capell Packages Used Here”- Capell Admin supplies the Capell-side contracts, surfaces, or runtime that Blog builds on.
- Insights supplies the Capell-side contracts, surfaces, or runtime that Blog builds on.
- Capell Frontend supplies the Capell-side contracts, surfaces, or runtime that Blog builds on.
- Core admin/frontend layout builder APIs supply the Capell-side contracts, surfaces, and runtime that Blog builds on.
- Navigation supplies the Capell-side contracts, surfaces, or runtime that Blog builds on.
- Tags supplies the Capell-side contracts, surfaces, or runtime that Blog builds on.
- Publishing Studio supplies the Capell-side contracts, surfaces, or runtime that Blog builds on.
What We Especially Appreciate
Section titled “What We Especially Appreciate”Blog is useful because it composes many Capell packages without absorbing them. Tags, navigation, layout, insights, and Publishing Studio all stay updateable in their own packages while Blog wires them into an editorial surface.
Keeping This Page Current
Section titled “Keeping This Page Current”When Blog 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.