- Does sevendays/filament-page-builder support Filament v4?
- The package is built for Filament 3.x and its latest release dates to September 2024, with no published Filament 4 support. Filament moves through major versions quickly, so confirm compatibility with Sevendays Digital before planning a panel upgrade. Budget time for an in-house port if Filament v4 is on your roadmap.
- How do I install and set up the page builder in a Laravel app?
- Install with Composer, then publish the package's config, migrations, and views via vendor:publish and run the migrations. After that you register the Page resource in your Filament panel and author block classes that pair a Filament form schema with a Blade view. A mid-level Laravel developer can typically render a first page in one to two days.
- Do I need Filament to use it, or can I use it headlessly with a SPA?
- Filament is required: the package is Filament-native and reuses Filament form schemas, policies, and Livewire rendering rather than exposing an API. It is not headless or framework-agnostic and assumes server-rendered Blade output. If your front end is a separate SPA or Next.js app consuming an API, this package is a poor fit.
- How is page content stored and rendered?
- Each page is an Eloquent model whose content is stored as a JSON array of typed blocks, edited through a Filament resource with a drag-and-drop interface. Rendering happens through Blade components, so output stays server-rendered. There is no separate content API or delivery layer.
- How do I create a custom block?
- A block is a class that pairs a Filament form schema with a Blade view, giving editors fields in the panel and a matching render template. You register the block, then verify rendering, route binding, and asset publishing in your panel. Building a production-grade block library that mirrors your design system is the bulk of the integration effort.
- What happens to published pages if I rename or delete a block type?
- Block payloads live as JSON in the database with no evident schema version, so renaming, removing, or restructuring a block type can throw render-time exceptions on already-published pages. Plan block migrations or graceful fallbacks in your Blade views before you ship. Treat block type names as a contract once content exists.
- Is there a free and Pro version, and what does Pro cost?
- Yes, a commercial Pro tier exists alongside the free package. The exact feature split and pricing at your expected scale are not spelled out in the overview, so request details from Sevendays Digital before committing. Budget either a license or the cost of a maintenance fork of the free tier.
- Is it production-ready, and how should I handle XSS and caching?
- The package is a small, single-vendor project with no observable production track record, so treat it as a component to harden rather than a turnkey CMS. HTML and rich-text blocks shift XSS and layout-sanitization responsibility onto your team, so sanitize output and restrict which blocks editors can use. Measure rendering cost per request and add caching for published pages before launch.
- Does it support drafts, revisions, scheduled publishing, and multi-language pages?
- The surface area targets CMS-lite marketing and landing pages: page management and flexible block editing, but no first-class revisions, scheduling, or granular editorial roles are implied. Multi-language or translatable pages are not documented out of the box. If you need editorial workflow or localization, plan custom work or look at a fuller CMS.
- Who maintains the package, and what is the bus factor?
- It is maintained by Sevendays Digital, a single small agency, with around 55 stars, zero dependents, and a last release in September 2024. That makes the bus factor effectively one, with no visible community fork momentum. Ask about support commitments and PR acceptance, or plan an internal fork you can maintain.