Credits And Acknowledgements
Capell Packages is a set of focused add-ons, and each add-on stands on work from the Laravel, Filament, Livewire, Spatie, PHP, and wider open-source communities. This page is not a replacement for composer.lock, package-lock.json, or license files. It is the human version: who we rely on, what their work lets Capell do, and where each package gets a bit of extra help.
The main Capell app has its own broad credits page. This page is more practical and package-shaped. It follows the add-ons in this repository and calls out the credits that matter when someone is choosing, installing, or maintaining a package.
Shared Foundations
Section titled “Shared Foundations”- Laravel, created by Taylor Otwell, gives every package the application model: service providers, routing, queues, Eloquent, validation, auth, events, caching, testing helpers, and Composer-native installation.
- Filament and the Filament project give Capell packages their admin vocabulary: resources, pages, widgets, tables, forms, actions, panels, icons, and a plugin catalog that saves us from rebuilding common CMS screens.
- Livewire, by Caleb Porzio and the Livewire team, keeps interactive UI close to Laravel and Blade. That matters for packages that need admin workflows without moving the whole product into a separate JavaScript app.
- Tailwind CSS and Vite carry the theme and frontend asset story. They keep package styling and builds predictable across themes, blocks, and frontend authoring.
- Composer, Packagist, and GitHub are the services underneath the package workflow. They make path repositories, split packages, dependency metadata, releases, and installation docs possible.
- Pest, Orchestra Testbench, PHPStan, Larastan, Laravel Pint, and Rector keep the packages testable and maintainable while the product surface grows.
Package Shape And Authors
Section titled “Package Shape And Authors”Several package patterns show up across the repo, so they deserve a clear thank you:
- Laravel Actions, by Loris Leiva, gives Capell a consistent home for package behaviour. It keeps commands, Filament pages, controllers, and widgets from becoming the place where business rules hide.
- Spatie Laravel Data, by Ruben Van Assche, gives package boundaries typed data instead of loose arrays.
- Spatie Laravel Package Tools, by Freek Van der Herten and Spatie, keeps package bootstrapping usefully dull: config, migrations, commands, providers, and assets behave the same way from package to package.
- Spatie more broadly influences the package style here. Capell uses Spatie conventions where they make the code plainer, easier to test, and easier for Laravel developers to recognise.
Package Notes
Section titled “Package Notes”| Package | Credits | Something extra |
|---|---|---|
| Address | Built on Capell Admin, Filament forms, Laravel validation, and Blade Country Flags. | The flag picker is a small detail, but it makes country and language fields feel finished instead of looking like raw ISO codes. |
| Agent Bridge | Built on Capell Core, Capell Admin, Laravel MCP, Laravel Actions, Laravel Data, and Package Tools. | The MCP note matters because it gives Capell a clean way to expose site capabilities to agents without teaching every agent about Capell internals. |
| AI Orchestrator | Built on Capell Core/Admin, Laravel Actions, Laravel Data, Package Tools, and provider-style AI service contracts. | Its best borrowed idea is the pipeline shape: capability, review, approval, and execution stay separate enough that teams can add AI without handing it the keys. |
| Blog | Built on Capell Admin, Insights, Frontend, core layout builder APIs, Navigation, Tags, and Publishing Studio. | Blog is a good example of Capell packages composing rather than swallowing each other: analytics, navigation, tags, layout, and publishing all keep their own jobs. |
| Campaign Studio | Built on Capell Core/Admin/Frontend, Insights, Form Builder, core layout builder APIs, Laravel Actions, Laravel Data, and Package Tools. | The extra here is attribution discipline. Campaign pages, goals, forms, and UTM data belong together, but the package still leaves room for SEO and analytics packages to do their own work. |
| Dashboard Reports | Built on Capell Core/Admin, Filament widgets, Laravel Actions, Laravel Data, and Package Tools. | This package is intentionally plain: it gives reporting widgets a shared shape so each feature package does not invent its own dashboard grammar. |
| Deployments | Built on Capell Core/Admin, Laravel’s HTTP and console foundations, Laravel Actions, Laravel Data, Package Tools, and repository services such as GitHub, GitLab, and Bitbucket. | The package credits the deployment platforms directly because marketplace installs are only useful if they can turn a package choice into a reviewable Composer change. |
| Diagnostics | Built on Capell Core/Admin, Laravel console primitives, Filament pages, Laravel Actions, Laravel Data, cache tooling, queue state, migration state, and package manifests. | Diagnostics is where Capell borrows from operations culture: make the hidden state visible before asking a developer to guess. |
| Form Builder | Built on Capell Core/Admin/Frontend, Laravel validation, Filament schema components, Livewire, Blade, and the frontend render hook model. | The extra credit is to Filament’s form language. Capell can offer public form building without creating a second form system for editors and developers to learn. |
| Foundation Theme | Built on Capell Frontend, Blade, Tailwind, Vite, Laravel view helpers, and Package Tools. | This is the base coat for every theme package: deliberately modest, easy to override, and useful as a reference when a custom theme needs to know what Capell expects. |
| Frontend Authoring | Built on Capell Admin/Frontend, signed routes, Laravel auth, cache-safe frontend rendering, package render hooks, and Package Tools. | The package owes a nod to the web’s old “view source” spirit: edit controls are discovered after load, while public HTML stays ordinary and safe for non-admin visitors. |
| GA4 Reports | Built on Capell Core/Admin, Laravel Actions, Laravel Data, Package Tools, and Google Analytics 4. | The package keeps GA4 data local enough to report on it consistently, while still respecting that Google owns the measurement service. |
| Insights | Built on Capell Core/Admin/Frontend, Laravel Actions, Laravel Data, Package Tools, beacon-style frontend events, and consent-aware storage. | The extra acknowledgement here is privacy pressure. Insights is better because it treats consent and retention as product features, not paperwork. |
| Login Audit | Built on Capell Admin, Rappasoft Laravel Authentication Log by Anthony Rappa, and Tapp Network’s Filament Authentication Log. | This package is a thank-you to two layers of work: one records auth events well, the other makes those events useful inside Filament. |
| Media AI | Built on Capell Core/Admin, Filament actions, Laravel service contracts, Package Tools, and optional AI provider implementations. | The package keeps the default path safe with a null image doctor, so teams can add AI media help when they are ready rather than wiring it into every install. |
| Media Library | Built on Capell Core/Admin and AWCodes Curator. | Curator deserves specific credit: it gives Capell a polished Filament media library, and this package turns that into a first-class Capell media backend. |
| Migration Assistant | Built on Capell Core/Admin, Laravel database tools, Laravel Actions, Package Tools, CSV/XML reader patterns, and rollback reporting. | The package borrows from ETL tooling without becoming an ETL platform: inspect, map, validate, run, and keep a rollback story. |
| Navigation | Built on Capell Admin/Frontend, Filament resources, Blade rendering, Laravel routing, and Capell’s frontend URL model. | Navigation is small on purpose. It is the package that lets themes, blogs, and layouts agree on menus without sharing internal models. |
| Password Policy | Built on Capell Core/Admin, Laravel auth, Laravel password rules, Laravel Actions, Laravel Data, and Package Tools. | The package credits Laravel’s built-in auth primitives by staying close to them: expiry, history, and forced changes layer on top instead of replacing login. |
| Publishing Studio | Built on Capell Core/Admin, Migration Assistant, Navigation, Filament Peek by Patrick Boivin, Laravel queues, Filament resources, and php-diff by Jack Cherng and Chris Boulton. | php-diff makes editorial comparison possible, Filament Peek keeps draft previews in the admin flow, and the package’s extra value is judgement: previews, approvals, schedules, comments, and rollback all live in one publishing lane. |
| Search | Built on Capell Core/Admin/Frontend, Laravel Actions, Laravel Data, Package Tools, frontend search views, optional logging, and admin insight widgets. | The package keeps search humble: useful query capture and results flow without forcing a heavy external search service into small sites. |
| SEO Suite | Built on Capell Admin/Frontend, Insights, PHP Sitemap Generator by Dmitrii Prisacari, and Prism PHP by TJ Miller. | SEO Suite gets extra reach from two different communities: sitemap generation for machines, and Prism for AI-assisted metadata where a team wants it. |
| Demo Kit | Built on Capell Core/Admin/Frontend, Laravel package discovery, demo media assets, and Capell’s seed/demo workflow. | Demo Kit is a thank-you to everyone who has ever tried to evaluate a CMS from an empty admin panel. Demo content makes the product explain itself faster. |
| Tags | Built on Capell Admin, Navigation, Publishing Studio, Filament’s Spatie Laravel Tags Plugin, and Spatie Laravel Tags. | The package benefits from Spatie’s tag model and Filament’s form integration, then adds Capell’s publishing and navigation context around it. |
| Theme Agency | Built on Capell Core, Foundation Theme, Blade, Tailwind, and the theme renderer contract. | This theme credits the frontend stack by being opinionated but replaceable: expressive enough for agencies, still bound to Capell’s renderer rules. |
| Theme Corporate | Built on Capell Core, Foundation Theme, Blade, Tailwind, and the theme renderer contract. | The corporate renderer adds restraint as a feature: predictable sections, trust-led composition, and less temptation to over-design operational pages. |
| Theme SaaS | Built on Capell Core, Foundation Theme, Blade, Tailwind, and the theme renderer contract. | SaaS pages need clarity more than theatre. This package credits the shared theme system by turning the same content model toward conversion-heavy pages. |
| WordPress Importer | Built on Capell Core/Admin, Migration Assistant, PHP SimpleXML, WordPress WXR exports, and Package Tools. | WordPress gets a specific credit because its export format is the bridge. This package reads WXR without pretending every migration source looks the same. |
Services We Should Keep Naming
Section titled “Services We Should Keep Naming”- Google Analytics 4 powers GA4 reporting when teams connect their property.
- GitHub, GitLab, and Bitbucket matter to Deployments because package installs often end as pull requests.
- WordPress matters to migration work because many Capell sites will start life as a WordPress export before they become structured Laravel content.
- AI provider services sit behind Prism or package-specific contracts. Capell should keep naming the adapter and the provider in feature docs when a package starts depending on one directly.
Maintenance Rule
Section titled “Maintenance Rule”When a package adds a meaningful framework, service, or third-party package, update both the package README and this page. A credit should say what the tool does for Capell, not just that it exists.