Skip to content
Capell CMS

Theme SaaS Credits And Acknowledgements

Theme SaaS 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: Conversion-led SaaS renderer for Capell theme system

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

What We Especially Appreciate

Section titled “What We Especially Appreciate”

Theme SaaS is useful because it turns the shared theme model toward conversion pages. SaaS-specific layout fixes can happen without changing agency or corporate renderers.

Keeping This Page Current

Section titled “Keeping This Page Current”

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