README

A visual page builder for Laravel 12 and 13 with Filament 5, with Persian and RTL authoring built in. Create responsive pages in a Filament panel, then render published revisions as server-generated HTML in a Laravel site.

FilaForge stores pages as validated, versioned JSON documents. The editor and public renderer are separate: public pages do not load the editor runtime, and the host application keeps control of routes, authorization, tenants, and caching.

Composer package · GitHub repository · Installation guide · Security guide

Preview

An English sample page rendered by FilaForge Studio:

The page open in the Filament editor:

What you can build

Visual authoring: isolated canvas, drag and drop, nested layouts, layers, inline rich text, undo and redo, responsive settings, and preview.
Page building blocks: 32 built-in widget types and 18 presets for layouts, content, media, navigation, FAQs, testimonials, pricing, carousels, wizards, and more.
Persian and RTL: 17 interface locale catalogs, page language and direction, mixed RTL/LTR content, and configurable fonts.
Media library: Laravel Filesystem uploads, stable media references, folders, categories, metadata, image editing, and remote image/video references.
Dynamic content: explicitly registered providers, field and filter allowlists, bounded query loops, conditional display, and controlled shortcode-to-widget conversion.
Publishing: versioned documents, draft and published revisions, optimistic concurrency checks, atomic publication, and draft restoration from publication history.
Server rendering: HTML fragments for an existing layout, complete HTML documents, Laravel responses, or the exact published revision for a page locale.
Reusable content: independent published sections, linked shared sections, sanitized HTML blocks, database card repeaters, and typed shared styles.
Editing workflow: optional client locks and exposed fields, autosave, tab-local recovery, and publication history with draft restore.
Extensibility: trusted custom widgets with Filament inspectors, presets, fonts, and Laravel data providers.
Developer customization: publishable Blade views, public assets and translations; host-controlled column headings; replaceable or disabled resources per Filament panel.

See reusable sections and database repeaters, widgets and presets, media and fonts, dynamic content, and current capabilities and limitations for details.

Requirements

PHP 8.2 or newer
Laravel 12 or 13 (Laravel 13 requires PHP 8.3+)
Filament 5 and its compatible Livewire version
PHP extensions: DOM, Fileinfo, GD, and mbstring
A database driver supported by the host Laravel application
pdo_sqlite to run the package test suite
Optional intl for Persian calendar date formatting

Install and register Filament

composer require filaforge-studio/filaforge-studio
php artisan filaforge:install
php artisan migrate

use FilaForge\Studio\Filament\FilaForgeStudioPlugin;
use Filament\Panel;

public function panel(Panel $panel): Panel
{
    return $panel->plugin(FilaForgeStudioPlugin::make());
}

Package discovery registers the service provider. The plugin is opt-in per panel. Configure host authorization before editors create, update, publish, or moderate content. FilaForge does not create public website routes; your Laravel app owns page lookup and access rules. Follow the installation guide and security guide.

Customize the package in your application

View and asset publishing, resource replacement, and resource inheritance are available starting with v0.2.2. See the changelog for release details.

Publish only the files you want to own in your application:

php artisan vendor:publish --tag=filaforge-config
php artisan vendor:publish --tag=filaforge-views
php artisan vendor:publish --tag=filaforge-assets
php artisan vendor:publish --tag=filaforge-translations

Or run php artisan filaforge:install --views --assets --translations to publish all four groups. Views go to resources/views/vendor/filaforge, public assets to public/vendor/filaforge, and translations to lang/vendor/filaforge. Set 'published_assets' => true in config/filaforge.php to use the published assets; otherwise the package serves its bundled assets through allowlisted routes.

Choose resources independently for each panel:

use App\Filament\Resources\PageResource as CustomPageResource;
use FilaForge\Studio\Filament\FilaForgeStudioPlugin;

$panel->plugin(
    FilaForgeStudioPlugin::make()
        ->pageResource(CustomPageResource::class)
        ->commentResource(null),
);

Resource methods accept a Filament Resource class or null to disable its registration. Application-wide defaults are available under filaforge.resources. You can extend package resources and their page classes to customize forms, tables and navigation. When extending a resource, also override getPages() and bind each extended page's $resource to your resource, as shown in the developer customization guide.

For headings alone, configure literal labels or translation keys from your own application:

// config/filaforge.php
'resource_labels' => [
    'pages' => ['columns' => ['title' => 'admin.pages.title']],
    'comments' => ['columns' => ['body' => 'admin.comments.message']],
],

Define those keys in your application's lang/en/admin.php, lang/fa/admin.php, or other locale catalogs. Omitted labels use package translations. See localization for every available column.

Published files are preserved unless you explicitly use vendor:publish --force. Review and merge package changes into your overrides after upgrades. Disabling an admin resource does not disable public comment endpoints or change host authorization. See configuration and upgrade guidance.

Render a published page in Laravel

After creating a page in the Filament Pages resource and publishing it, resolve the locale and slug in a host-owned route. Scope the query to your tenant and visibility rules where applicable:

use FilaForge\Studio\Models\PageLocale;
use FilaForge\Studio\Rendering\HtmlRenderer;
use Illuminate\Support\Facades\Route;

Route::get('/{locale}/{slug}', function (string $locale, string $slug, HtmlRenderer $renderer) {
    $page = PageLocale::query()
        ->where('locale', $locale)
        ->where('slug', $slug)
        ->firstOrFail();

    // Add tenant, visibility, and access constraints to this lookup as needed.
    return $renderer->publishedResponse($page);
});

publishedResponse() reads the locale's exact published revision, returns 404 when none exists, and never falls back to its draft. The default response uses private/no-store cache headers. The host remains responsible for route authorization and any tenant-aware caching policy.

Embed a reusable section anywhere

Use a host-authorized PageLocale to insert its published content into any Blade view, without requiring a FilaForge layout:

<header>Your existing header</header>
{{ filaforge_section($authorizedPageLocale) }}
<footer>Your existing footer</footer>

Each instance receives isolated IDs and local anchor links. Register shared-section aliases to reuse published content inside other documents, optionally exposing selected text or image properties per instance. The visual database repeater builder creates editable cards from trusted provider fields, with sorting, filters and pagination. See reusable sections and database repeaters for examples, authorization, tokens, HTML sanitization, recovery and custom inspectors.

Rendering helpers

Laravel package discovery loads three global helpers. Each accepts a validated FilaForge document; the optional page locale supplies page context for media, comments, and dynamic rendering.

Put a fragment in an existing Blade layout

Use filaforge_html() when your application already owns the document shell and SEO metadata:

<main>
    {{ filaforge_html($pageLocale->publishedRevision->document, $pageLocale) }}
</main>

It returns an HtmlString containing rendered page markup and required styles/interactions. It does not compile stored content as Blade or include the editor runtime.

Build a full document or HTTP response

filaforge_document() returns a complete HTML document. filaforge_response() wraps it in a Laravel response. HtmlOptions lets the host supply document metadata and stylesheets:

use FilaForge\Studio\Rendering\HtmlOptions;

$document = $pageLocale->publishedRevision->document;
$options = new HtmlOptions(
    title: $pageLocale->title,
    description: 'Explore our services.',
    canonical: route('pages.show', [
        'locale' => $pageLocale->locale,
        'slug' => $pageLocale->slug,
    ]),
    stylesheets: ['/css/site.css'],
);

$html = filaforge_document($document, $options, $pageLocale);
return filaforge_response($document, $options, $pageLocale);

Canonical and stylesheet URLs must be HTTP(S) or root-relative. Page scripts stay off for these helpers unless explicitly enabled through HtmlOptions and allowed by host policy and CSP.

Use the renderer service or facade

For dependency injection, use HtmlRenderer; the StudioHtml facade exposes its fragment and document methods:

use FilaForge\Studio\Facades\StudioHtml;
use FilaForge\Studio\Rendering\HtmlRenderer;

$fragment = app(HtmlRenderer::class)->fragment($document, $pageLocale);
$html = StudioHtml::document($document, $options, $pageLocale);

Embed a published page in a custom Filament view

The Filament plugin provides page editing. If a host Filament page or widget also needs to display a published page, resolve and authorize its PageLocale in the host component, then render its view with the helper:

{{-- resources/views/filament/pages/site-preview.blade.php --}}
<x-filament::section>
    <main>
        {{ filaforge_html($pageLocale->publishedRevision->document, $pageLocale) }}
    </main>
</x-filament::section>

Here $pageLocale must be the authorized locale model supplied by the host Filament page or widget. Keep tenant scoping and access checks in that component; a hidden panel action or URL slug is not authorization.

Create and publish content

Define page-management abilities in the host application.
Open Pages in the selected Filament panel and create a page with its language and direction.
Add a section or container, then drag widgets or presets onto the canvas.
Edit content, typography, colors, background, and responsive settings.
Preview, save a draft, and publish when ready.
Render the published revision from a host-owned Laravel route or Blade view.

See the quick start, HTML output API, and SEO guide for more examples.

Development

composer install
vendor/bin/phpunit -c phpunit.xml

The package suite uses SQLite and covers validation, rendering, Filament integration, permissions, media, dynamic data, scripts, comments, and localization. For contributor workflow and documentation commands, see CONTRIBUTING.md; for test evidence and remaining gaps, see verification and limitations.

Contributing and security

Read CONTRIBUTING.md before making changes. Report vulnerabilities privately using the instructions in SECURITY.md.

License

FilaForge Studio is distributed under the MIT License. Third-party assets may have separate terms; see their bundled notices.

Woman . Life . Freedom

Stand with people of Iran

filaforge-studio / filaforge-studio

Package info

Security

Statistics