- What is stephenjude/filament-blog and what features does it include?
- It is a blog management package for Laravel Filament admin panels. It ships Filament resources and pages for posts, categories, tags, authors, and comments, plus drafts, scheduled publishing, rich text editing, and SEO fields. It is an editorial admin layer, not a complete CMS, so the public blog experience is still built in your application.
- How do I install filament-blog in a Laravel application?
- Install it with Composer, register the plugin in your Filament panel provider, and publish and run its configuration and migrations. You then configure the rich text or markdown editor and media storage for post content. Exact commands and panel registration details are in the package README.
- Which Laravel and Filament versions does filament-blog support?
- Version 5.x targets Filament 5 and Laravel 13. Teams on Filament 3 or 4, or Laravel 12 and below, should pin the 4.2.x line instead. Check your version matrix before starting because the package line determines your whole upgrade path.
- Does filament-blog provide public blog routes, controllers, or frontend views?
- No. The package is faceless: it manages content in Filament but does not ship public routing, templates, or a reader-facing frontend. You build the delivery layer yourself with Blade, Inertia, an API, or a separate frontend that queries published posts. Budget time for controllers, slug routing, redirects, and rendering.
- Does filament-blog handle SEO metadata, sitemaps, and RSS feeds?
- It provides SEO-friendly fields in the admin for editing post metadata. It does not generate meta tags, canonical URLs, sitemaps, or RSS feeds on the public site. Those remain application responsibilities and usually require your own controllers, templates, and caching.
- How does comment moderation work in filament-blog?
- Comments are managed as a Filament resource, so editors can review, approve, or delete them from the admin panel. The package does not provide a public comment form or spam protection out of the box. You need to build submission handling, validation, spam checks, and authorization in your application.
- Can I use filament-blog with an existing blog database and posts?
- The package ships its own migrations and model schema, so existing content usually needs field mapping and a migration into its tables. If your current posts use a different structure, expect adapter or dual-model work unless the schema maps cleanly. Test the migration on a copy of production data before committing.
- How should I handle richtext HTML and XSS with filament-blog?
- The package lets you configure the rich text or markdown editor, but sanitization and rendering are your responsibility. Standardize one storage format across the team rather than mixing raw HTML, markdown, and editor-specific output. Sanitize stored HTML on output or before saving, and treat media uploads as an application security concern.
- Does filament-blog support drafts and scheduled publishing?
- Yes, it includes draft status and scheduled publishing controls for posts. The Laravel scheduler must be running for scheduled posts to go live, and your public delivery layer must filter to published content only. Draft exposure is an application authorization concern, not something the admin package enforces on the frontend.
- Is filament-blog production-ready and actively maintained?
- It has a modest adoption signal with roughly 200 stars and few dependents, and it is maintained by a single author. The 5.0.0 release shows the maintainer tracking Filament majors, but it is a major bump and should be assumed to drop Filament 4 support. The MIT license allows forking, so plan to own upgrade compatibility internally.