- How do I install Filament Atelier in a Laravel app?
- Install it with Composer using composer require safi/filament-atelier, then publish the migrations with php artisan vendor:publish --tag=filament-atelier-migrations. Run php artisan migrate and php artisan storage:link so uploads work. Finally register AtelierPlugin::make()->blocks(DefaultBlocks::all()) inside your Filament panel provider and point Tailwind at the package's views.
- Which Laravel and Filament versions does Filament Atelier support?
- Filament Atelier is built as a Filament plugin for Laravel applications, and the repository ships an example Laravel 13 app that installs it for testing. The README does not publish explicit version bounds, so check the constraints in composer.json on Packagist against your own app before requiring it. If your panel satisfies those constraints, registration is a single AtelierPlugin::make()->blocks(...) call in your panel provider.
- How do I create a custom block in Filament Atelier?
- A block type is one PHP class plus one Blade view. The class declares the block's key, label, icon and category, and exposes a Filament schema that becomes the block's settings form. Register the blocks you want via the blocks() method on AtelierPlugin, and they appear in the section picker in the editor. Adding a block never requires editing a file inside the plugin itself.
- Does Filament Atelier store page HTML in the database?
- No. Each page is stored as a JSON tree of typed blocks and rendered by Blade at request time, so the database never holds raw HTML markup. This is Gutenberg's data model combined with Elementor's rendering approach. It avoids block validation issues and deprecation chains that come with stored markup.
- How accurate is the live preview in the page builder?
- The preview is the real page. The editor's iframe loads your public layout and the public stylesheet, so what the client sees in the editor is what ships on the site. A width switcher for desktop, tablet and mobile lets you catch layout problems such as a headline wrapping onto three lines before anyone else does.
- Does Filament Atelier support multiple languages and per-locale SEO?
- Yes. The package produces bilingual output and supports per-locale SEO settings, along with page settings and public page rendering. Content is rendered server-side per locale rather than shipped as one blob of HTML. Check the wiki for the current known limits before promising a fully multilingual rollout to a client.
- Is Filament Atelier production ready?
- It is an MVP and installable: the builder, blocks, page settings, per-locale SEO and public pages all work. The maintainer explicitly recommends reading the Not built yet section and the known limits on the wiki before promising anything to a client. Treat it as a strong foundation for evaluated projects rather than a finished, battle-tested product.
- Is the public site fast and server-rendered?
- Yes. The public site stays server-rendered Blade, so pages are rendered at request time from the stored JSON block tree. No HTML is persisted in the database and no client-side renderer is required to display content. That keeps the output crawlable, cacheable and multi-language friendly.
- Why is my Atelier block styling missing after install?
- Tailwind must be told to scan the package's views, otherwise the classes used by built-in blocks are purged from your CSS. Add the Filament Atelier view paths to the content array in your Tailwind config and rebuild assets. The README warns that some setup steps fail silently, so verify this first if the editor or preview looks unstyled.
- How does Filament Atelier compare to Gutenberg or Elementor?
- It borrows Gutenberg's JSON block data model and Elementor's rendering approach while avoiding the parts that hurt: no HTML stored in the database, no block validation layer, and no deprecation chains. Instead of a JS-heavy runtime, blocks are a PHP class and a Blade view registered in your panel. The result is a Filament-native builder whose output is plain server-rendered Blade.