Weave Code
Filament Cms Laravel Package
tomatophp/filament-cms
Full CMS builder for Filament: manage posts, categories, and content with built-in comments and ratings, multi-meta and SEO fields, plus import/export of integrations. Install with Composer, run filament-cms:install, then register the FilamentCMSPlugin in your admin panel.
Full CMS System with support of importing integrations and multi meta functions
Frequently asked questions about Filament Cms
- What is tomatophp/filament-cms and when should I use it?
- It is a Filament plugin that adds CMS features to Laravel admin panels, including posts, categories, SEO meta, comments, ratings, and import/export. Use it when your application already uses Laravel and Filament and you need an editorial content manager inside the panel. It is not a standalone CMS and is a poor fit for headless, API-first, or non-Filament admin architectures.
- Which Laravel and Filament versions does filament-cms support?
- Version lines differ significantly, so version selection matters. The v1.x line targets Filament 3, v5 targets Filament 5 with Laravel 12/13 and PHP 8.2+, and v4 appears transitional with feature-loss warnings. Pin the package major in composer.json and validate it against your exact Laravel, Filament, and PHP versions before adopting it.
- How do I install Filament CMS Builder in a Laravel app?
- Install it with Composer using composer require tomatophp/filament-cms, then run php artisan filament-cms:install. Register FilamentCMSPlugin in your AdminPanelProvider and enable only the features you need, such as useCategory, usePost, allowImport, and allowExport. Publish and review config, views, language files, and migrations as needed before importing content.
- How do I enable or disable posts, categories, import, and export in the Filament plugin?
- The plugin exposes fluent toggles on FilamentCMSPlugin::make(), including useCategory(), usePost(), allowExport(), and allowImport(). Register only the features your editorial workflow actually needs. This keeps the admin surface smaller and reduces permission and maintenance complexity.
- Why can't I edit pages or posts without a Post policy in filament-cms?
- The package can require an authorization policy for TomatoPHP\FilamentCms\Models\Post, and without it page editing can be blocked. You need to create and register an appropriate policy for the Post model in your Laravel application. Review editor permissions and author types as part of the security setup, not just the install step.
- Do I need the legacy Splade page builder routes in filament-cms?
- No, the legacy Splade builder routes are off by default and must be explicitly enabled. Only enable them if you actually need that page-builder surface and have reviewed its permissions and security implications. Most Filament-first editorial installs can leave them disabled.
- Can I customize Filament CMS post and category forms, tables, actions, filters, and infolists?
- Yes, the package provides extension points such as FilamentCMS::types(), FilamentCMS::authors(), registerImportAction(), post events, and static registries for Post and Category form, table, action, filter, and infolist components. This gives teams a staged customization path before forking. Customization does depend on familiarity with Filament form, table, and infolist APIs.
- Is tomatophp/filament-cms ready for production use?
- It is MIT licensed and forkable, but its ecosystem maturity is the main risk: the package has limited stars and dependents, which suggests limited production validation. Pin a specific major, install it in a sandbox branch, and run regression tests for your Filament and Laravel versions. Plan a fork or patch budget in case the package stalls or breaks on future upgrades.
- How do I migrate existing content into Filament CMS Builder?
- Treat it as a new CMS surface rather than a drop-in migration target. Review the created schema after installation, then map existing content into Post, Category, and multi-meta fields, or introduce custom CmsType entries where the default Post model is too restrictive. Do not plan an in-place major upgrade from v1 to v4 or v5 without a feature-by-feature regression pass, and validate import/export data quality carefully.
- When should I avoid filament-cms and what alternatives should I consider?
- Avoid it if your product is headless, API-first, uses a non-Filament admin, or needs content primitives that do not fit the opinionated Post and Category model. In those cases, consider a standalone Laravel CMS, a headless CMS, or custom Filament resources tailored to your domain. If you adopt filament-cms, confirm Filament fluency, policy ownership, translatable content needs, and long-term fork or patch capacity first.
Weaver
How can I help you explore Laravel packages today?