- How do I install rizky-dhani/filabuilder in a Laravel Filament app?
- Install the package with Composer (composer require rizky-dhani/filabuilder) and register it as a plugin in your Filament panel provider, typically through a plugin() call in the panel configuration. FilaBuilder is a presentation-layer add-on, so no migrations or data changes are indicated by the v1.0.12 release. After installing, clear compiled views and config caches so the builder Blade views load current assets, then open the builder in your admin panel to confirm it renders.
- Does FilaBuilder require database migrations or schema changes?
- No. The v1.0.12 change is limited to the admin builder view, swapping SVG block thumbnails for FontAwesome icon markup and adding a CDN stylesheet, so there is no backend, database, or API impact. You can update the package and clear caches without running migrations. If a future release adds persistence for saved pages, review its changelog before upgrading.
- Which Laravel and Filament versions does FilaBuilder support?
- FilaBuilder targets Laravel applications running Filament, so confirm the exact Laravel, PHP, and Filament version constraints in the package's composer.json before installing. Because it is a Filament plugin, your Filament major version (v3 versus v4) matters most for compatibility. Pin the package version and test the builder in staging rather than assuming compatibility from the package name alone.
- How do I build a custom page with GrapesJS blocks in Filament using FilaBuilder?
- FilaBuilder embeds a GrapesJS-based editor inside Filament, so you compose layouts visually instead of hand-writing Blade markup for each page. The package ships blocks such as HeroBlock, TextBlock, and CtaBlock that you can drag into the canvas. Check the repository README for the exact panel registration and block registration API, since the public docs are the source of truth for method signatures.
- Does FilaBuilder load FontAwesome from a CDN, and can I self-host it instead?
- Yes. v1.0.12 adds FontAwesome 6.7.2 through a CDN reference in the builder view. If your security policy requires self-hosting, publish or override the builder Blade view and point it at your own FontAwesome asset, or allowlist the CDN in your CSP. The release notes do not state that the CDN URL is configurable, so a view override is the safest route.
- Will a strict Content Security Policy break the FilaBuilder block icons?
- It can. If your Content-Security-Policy blocks the FontAwesome CDN stylesheet, block icons render blank or fall back to plain text; the builder still works but looks degraded. Check the browser console and network tab for CSP violations against the FontAwesome URL. Fix it by allowlisting the CDN in style-src and font-src, or by self-hosting FontAwesome through a view override.
- How do I add custom blocks with icons to the FilaBuilder editor?
- Built-in blocks like HeroBlock, TextBlock, and CtaBlock moved from SVG thumbnails to FontAwesome icon HTML in v1.0.12, so custom blocks you registered with SVG thumbnails may need equivalent icon mappings. Update your block registration to supply a FontAwesome class that exists in the pinned 6.7.2 set. Clear compiled views afterward and verify each custom block icon renders in the editor.
- What happens if the FontAwesome CDN is blocked or the admin runs offline?
- The builder's icons fail to render, which is a visual degradation rather than a data-loss scenario, but the page can look broken in offline or air-gapped environments. Test by blocking the CDN in browser dev tools before rollout so you know exactly what admins will see. If graceful fallback matters, self-host FontAwesome or add your own icon fallback styling.
- After upgrading to v1.0.12 my block thumbnails still look like SVGs. How do I fix it?
- That usually means compiled Blade views are still serving the old template. Run php artisan view:clear and php artisan config:clear (or optimize:clear in some setups), then reload the builder. If you publish or override the builder view, confirm your override includes the new FontAwesome icon markup instead of the old SVG thumbnails.
- Is FilaBuilder maintained, and how should I test it before production?
- Track the package's releases and the pinned FontAwesome 6.7.2 version, since the CDN reference is an external dependency your team now owns operationally. Test upgrades in staging: update via Composer, clear caches, load the builder, verify HeroBlock, TextBlock, and CtaBlock icons, then repeat with the CDN blocked to observe failure behavior. Because support issues are likely visual, keep a short runbook covering CSP errors, network failures, and view overrides.