- What is haringsrob/filament-page-builder and what does it do?
- It is a Filament plugin that adds a visual page builder for Laravel applications. You create and manage dynamic pages in the Filament admin panel using reusable content blocks and customizable layouts, then render the stored content anywhere in your app. It best fits Filament-based apps that need CMS-lite page authoring rather than complex editorial workflows.
- How do I install haringsrob/filament-page-builder in a Laravel Filament app?
- Install it with Composer using the package name haringsrob/filament-page-builder, then register the Filament plugin in your panel provider. You will typically publish and run migrations, publish config or assets if the package provides them, and create or configure the page model and resource. Confirm the exact commands in the README for your Filament version before rollout.
- Which Laravel, Filament, and PHP versions are supported?
- The provided overview does not list a precise support matrix for Laravel, Filament, PHP, Livewire, or database versions. The last release date is 2024-09-02, so you should verify compatibility against your current stack in a staging spike. Pin Composer versions and test panel registration, migrations, and asset publishing before committing.
- How is page content stored and rendered?
- Content is stored by the package and rendered in your Laravel app, typically through Blade views that output the saved block content. The exact schema and rendering API should be confirmed from the package code and README during a technical spike. Keep rendering behind an internal contract so you can change or replace the package later.
- Can I define custom content blocks without forking the package?
- The overview suggests reusable blocks and customizable layouts, but it does not confirm whether blocks can be defined entirely in application code. You should inspect the package's extension points or test a small custom block in a spike. If extension requires patching, isolate block definitions in app-owned code and consider a fork.
- Does it support drafts, previews, scheduling, or revisions?
- Draft, preview, scheduling, and revision support are not confirmed in the provided overview, and the TPM notes flag them as open questions. Treat these as features to verify before using the package for editorial workflows. For regulated or multi-stage publishing, plan to add your own workflow or choose a fuller CMS.
- Is it suitable for production or high-traffic marketing pages?
- It can be a tactical accelerator for low-risk content surfaces such as marketing pages, landing pages, and modular content. Production suitability depends on caching, CDN strategy, media optimization, and query design for uncached render paths. With limited stars and a 2024 release, budget for internal ownership and compatibility patches.
- How do I handle SEO metadata and localization with this page builder?
- SEO metadata and localization are not confirmed features in the overview, so you should plan to own SEO fields and hreflang or multi-locale routing in application code. Keep metadata logic outside the package's block payloads where possible. Test how stored content behaves across locales before migrating important pages.
- What are alternatives to this package for Laravel and Filament page building?
- Alternatives include full CMS packages, custom Filament resources with block models, or other Filament page-builder plugins. The right choice depends on whether you need drafts, revisions, localization, multi-tenancy, and long-term support. Evaluate this package as a lightweight Filament-native option, not a strategic CMS replacement.
- How do I migrate away from or fork the package if it becomes unmaintained?
- Because the package has limited adoption evidence and a low release cadence, keep an exit plan: isolate it behind a content service or renderer contract, store block definitions and templates in app-owned code, and document the schema. A fork is reasonable if you need urgent Filament or Laravel compatibility fixes. Test migration and rollback on sample content before broader rollout.