- How do I install TallCMS in my Laravel Filament panel?
- Install it with composer require tallcms/cms, then run php artisan tallcms:install. Register TallCmsPlugin::make() in your Filament panel provider and add the Spatie HasRoles trait to your User model. The installer publishes 22 migrations, so run php artisan vendor:publish --tag=tallcms-migrations and review the schema before migrating.
- Which Laravel, PHP, and Filament versions does TallCMS support?
- TallCMS requires PHP 8.2 or newer and supports Laravel 11, 12, and 13; Laravel 13 requires PHP 8.3+. It hard-depends on Filament 5 and supports MySQL 8, MariaDB 10.3, or SQLite. Node 20+ is required in the host app for Vite builds.
- What is the difference between tallcms/cms and the standalone tallcms/tallcms package?
- tallcms/cms is the plugin that adds CMS features to an existing Filament panel, while tallcms/tallcms is the standalone CMS with themes, plugins, and auto-updates. Plugin mode is aimed at existing Laravel apps, and standalone-only features must be explicitly opted out of via TallCmsPlugin::make(). Choose standalone for greenfield projects and plugin mode when you already run Filament.
- Can I use TallCMS without the pages or posts modules?
- Yes. The plugin supports selective component registration, so you can call withoutPages() or withoutPosts() on TallCmsPlugin::make() and adopt only the modules you need, such as the block editor, media library, or forms. This keeps the integration lean instead of pulling in unused content types.
- Does TallCMS support multiple Filament panels or multisite setups?
- TallCMS supports multiple Filament panels with dynamic URL routing, which suits SaaS and multitenant setups where an admin panel and a client dashboard coexist. Full multisite with separate domains, themes, and settings is a commercial add-on. As of v4.9.1, theme display options and daisyUI presets resolve against the site selected in the Theme Manager rather than the admin hostname.
- Why does TallCMS require Node 20 and a Vite build?
- The host application must build its Vite manifest with Node 20+ before the Filament admin can render properly. That means your CI/CD pipeline and Docker images need a Node build step, and broken manifests or missing frontend dependencies become deployment risks to plan for.
- How does TallCMS handle roles and permissions?
- TallCMS integrates with Spatie's laravel-permission through the HasRoles trait on your User model. If your application already uses Spatie permissions, RBAC for CMS resources fits naturally; if not, budget time for migrating existing roles and permissions.
- Is TallCMS a good fit for a single-language Laravel project?
- The multilingual system relies on Spatie Translatable and LaraZeus and adds overhead such as slug management and route prefixes. If your project does not need translated content, that complexity may not be worth it, so validate slug and routing behavior during integration and confirm the configuration you need before committing.
- What changed in TallCMS v4.9.1 and should I upgrade?
- v4.9.1 is a drop-in patch with no migrations, no config signature changes, and no deprecations, so upgrading is a composer update plus a theme-settings verification pass. It fixes theme display options and daisyUI presets being saved against the admin hostname instead of the selected site. The fix does not rewrite already-saved values, so if you integrated at v4.9.0 or earlier, audit persisted theme settings and pin v4.9.1 or newer.
- Where do I report bugs or find TallCMS documentation?
- The tallcms/cms repository is a read-only subtree split of the tallcms/tallcms monorepo and is updated automatically via CI. File issues, pull requests, and consult full documentation in the monorepo. Plan upgrades against monorepo releases, and note that features like themes, plugins, and auto-updates belong to the standalone package.