- Can I use TallCMS in a Laravel project that doesn’t already have Filament installed?
- No, TallCMS is designed as a Filament plugin and requires Filament 5 to be installed first. If you’re starting a new project, consider the standalone `tallcms/tallcms` package instead, which doesn’t require Filament.
- How do I install TallCMS in my Laravel Filament project?
- Run `composer require tallcms/cms` and then execute `php artisan tallcms:install`. Finally, register the plugin in your Filament panel provider using `TallCmsPlugin::make()`. Ensure your `User` model includes the `HasRoles` trait from Spatie’s Laravel Permission.
- What Laravel and PHP versions does TallCMS support?
- TallCMS supports Laravel 11–13 with PHP 8.2+. Laravel 13 specifically requires PHP 8.3+. Always check the latest compatibility notes in the documentation, as minor updates may introduce version-specific changes.
- Does TallCMS work with multi-tenant or SaaS applications?
- Yes, TallCMS supports multi-panel integration, allowing you to register it in different Filament panels (e.g., admin vs. client dashboards). For multi-site or SaaS needs, consider the commercial Multisite add-on for managing multiple domains and themes.
- How do I customize or extend the block editor in TallCMS?
- TallCMS provides a block-based editor with 30+ daisyUI themes. To customize blocks, refer to the [Blocks documentation](https://github.com/tallcms/tallcms/blob/main/docs/dev-blocks.md). You can create custom blocks by extending the base classes or overriding existing ones via service providers.
- What happens if I only need the media library or forms but not all TallCMS features?
- TallCMS supports selective registration, so you can opt out of features like pages or posts using methods like `withoutPages()` or `withoutPosts()` in your plugin configuration. This reduces bloat and database overhead for unused components.
- Is TallCMS compatible with my existing RBAC or permission system?
- TallCMS integrates with Spatie’s Laravel Permission for role-based access control (RBAC). If you’re already using Spatie’s `HasRoles` trait, no additional setup is needed. For other permission systems, you’ll need to manually map TallCMS’s policies or extend its authorization logic.
- What are the frontend requirements for TallCMS, and how do I handle Vite builds?
- TallCMS requires Node.js 20+ and Vite for frontend assets. Ensure your CI/CD pipeline or local environment supports these requirements. If you encounter build issues, check the Vite manifest and dependencies, as TallCMS relies on Filament’s admin panel rendering.
- Are there any known issues with migrations or database schema conflicts?
- TallCMS publishes 22 migrations, so always run `php artisan vendor:publish --tag=tallcms-migrations` before migrating. Test migrations in a staging environment first, as schema conflicts (e.g., duplicate tables) can occur if other packages use similar structures.
- What alternatives exist if TallCMS doesn’t fit my project’s needs?
- For Laravel Filament, alternatives include **Filament Nova** (for simpler setups) or **Laravel Nova** (if you’re open to non-Filament solutions). For standalone CMS options, consider **October CMS**, **Statamic**, or **Craft CMS**, though these may require more integration effort with Laravel.