README

Filament Flexible Content Block Pages is a CMS solution for Laravel applications built on Filament Flexible Content Blocks. This package extends the flexible content block system, into a full page management solution with routing, SEO, menus, tags and multilingual support.

Designed for developers who need a content management system that provides a lot of flexibility to fit requirements, while providing content editors with an intuitive interface for managing pages and content.

Key Features

📄 Flexible page management - Create pages with hero images, flexible content blocks, SEO fields, and publication controls
🍔 Hierarchical menu builder - Drag-and-drop interface for creating navigation menus
🌍 Multilingual support - Full localization with automatic route generation for multiple languages
🔍 SEO tools - Automatic sitemap generation, meta tag management, SEO tag pages, and URL redirect handling when slugs change
⚡ Ready-to-use admin interface - Pre-configured Filament panel with all resources and management tools
🛠️ Developer-friendly - Extendable models & tables, customizable templates, and comprehensive configuration options
🏷️ Content organization - Tag system, hierarchical page structure, and settings management
🚀 Works out-of-the-box - Get the package quickly up and running, while focussing on easy configuration, customisation & extendability.

This package makes use of several great open-source packages to be able to bundle these features.

Installation
Setup in your project
Page management
Menu builder
Settings
- Use settings
Routing
Redirects
- Redirect middleware configuration
Sitemap Generator
Tags and SEO Tag Pages
Authorisation
Configuration
TODO's
Future work
Development
Changelog
Contributing
Security Vulnerabilities
Credits
- Used packages
License

Installation

You can install the package via composer:

composer require statikbe/laravel-filament-flexible-content-block-pages

Publish the config file with:

php artisan vendor:publish --tag="filament-flexible-content-block-pages-config"

If you want to alter the names of the database tables, do so in the config file, before running the migrations.

You can publish and run the migrations with:

php artisan vendor:publish --tag="filament-flexible-content-block-pages-migrations"
php artisan vendor:publish --provider="Spatie\MediaLibrary\MediaLibraryServiceProvider" --tag="medialibrary-migrations"
php artisan migrate

Configure the Filament tailwind styling of the frontend by adding these view paths to content array of tailwind.config.js:

content: [
    ...
    './vendor/solution-forest/filament-tree/resources/**/*.blade.php',
    './vendor/statikbe/laravel-filament-flexible-content-block-pages/**/*.blade.php',
    './vendor/statikbe/laravel-filament-flexible-content-blocks/**/*.blade.php',
    './config/filament-flexible-content-blocks.php',
]

In the tailwind config of your filament back-end, add the following lines to the content array:

content: [
    ...
    './config/filament-flexible-content-blocks.php',
]

You can now seed the home page and default settings by running:

php artisan flexible-content-block-pages:seed

Further configure the third-party packages that are used. Check the installation documentation of the following packages:

Laravel Filament Flexible Content Blocks

Probably, you will want to tweak the configuration of the Flexible blocks package. Publish the configuration using the installation guide.

Laravel Localization

Follow the installation and make sure the middlewares are properly set up if you want to use localised routes.

Laravel Tags

Follow the installation and publish the config and change the tag model to the package model:

[
    'tag_model' => \Statikbe\FilamentFlexibleContentBlockPages\Models\Tag::class,
]

Check the configuration documentation for more explanations on how to tweak the package.

Most likely you want to publish the views, so you can customise it for your project:

php artisan vendor:publish --tag="filament-flexible-content-block-pages-views"

Setup in your project

Translations

If you want translated content and routes, go through the following steps:

Configure the supported_locales in the Filament Flexible Content Blocks configuration or in a service provider
Configure the route_helper in filament-flexible-content-block-pages.php

Routes

Register the routes in your route file, probably web.php. Best at the bottom of the file, since the pages routes with slugs will catch many urls.

\Statikbe\FilamentFlexibleContentBlockPages\Facades\FilamentFlexibleContentBlockPages::routes();

Filament panel

The package contains a pre-configured panel. You can register the panel in the bootstrap\providers.php configuration file.

return [
    // ...
    \Statikbe\FilamentFlexibleContentBlockPages\FlexibleContentBlockPagesPanel::class,
    // ...
],

If you want you can build your own panel from the provided resources.

Redirects

Add the redirect middleware, see Redirect configuration

Schedule

We suggest to add media library maintenance tasks to your schedule in routes/console.php:

Schedule::command('media-library:clean')
    ->weeklyOn(1, '11:00');
Schedule::command('media-library:regenerate --only-missing')
    ->dailyAt('4:20');

Page management

The package provides a comprehensive page management system built on flexible content blocks.

Features

Flexible content creation - Rich page editor with hero sections, flexible content blocks, and media integration
Hierarchical organization - Three-level page structure (parent → child → grandchild) with automatic URL generation
Publication workflow - Draft/published status with optional scheduling (publishing_begins_at/publishing_ends_at)
Multilingual support - Full translation support, including slug localization
SEO optimization - Built-in meta tags, Open Graph, Twitter cards, and structured data
Author system - Optional author assignment and attribution
Media management - Hero images, content images, and SEO images via Spatie Media Library
Template system - Custom page templates with fallback support
Protected pages - Undeletable flag for critical pages
Search & filtering - Full-text search across page content, ready for Laravel Scout

Creating Pages

TODO screenshot

Create new pages through the Filament admin interface with a multi-tab form:

Content Tab - Title, slug, intro, and flexible content blocks
Hero Tab - Hero image and call-to-action buttons
Publication Tab - Status, scheduling, and author assignment
SEO Tab - Meta tags, Open Graph, and Twitter card settings
Parent Tab - Page hierarchy and template selection (if enabled)

Pages use automatic slug generation from the title but can be manually overridden for custom URLs.

Page Hierarchy

Create organized page structures with automatic URL generation:

Homepage (/)
├── About (/about)
│   ├── Team (/about/team)
│   └── History (/about/history)  
└── Services (/services)
    ├── Web Development (/services/web-development)
    │   └── Laravel (/services/web-development/laravel)
    └── Consulting (/services/consulting)

You can configure hierarchy support in your configuration file. In case you need deeper nesting, you can add extra routes.

Publication Controls

Control page visibility with by setting publishing begin and end dates. So you can achieve the following statuses by setting these dates in the past or future:

Draft - Page exists but not visible to public users
Published - Page is live and accessible via URL
Scheduled - Automatically publish/unpublish at specific times

Use the published() scope in your queries to show only published content:

$pages = Page::published()->get();

Multilingual Support

When using the LocalisedPageRouteHelper (see configuration), pages automatically support multiple languages:

Translated content - All text fields support per-locale content
Localized URLs - Each language gets its own slug (e.g., /en/about, /nl/over-ons)
Content blocks - Flexible content blocks are fully translatable
SEO per language - Meta tags and descriptions for each locale

The content can be copied between languages using the built-in "Copy to locales" action in the content blocks editor.

There is also a language switch component, that provides a simple way to navigate to another locale. For customisation, publish the views and if needed extend the LanguageSwitch component.

Frontend Integration

You can best publish the views and customise the styling and HTML structure to your project requirements.

For detailed frontend templating, theme customization, and available Blade components, see the frontend documentation.

For advanced page customization, extending models, and custom workflows, see the extending documentation.

Menu builder

The package includes a powerful hierarchical menu builder with a drag-and-drop interface, using solution-forest/filament-tree. Menus support multiple types of links and can be easily styled with custom templates.

Features

Hierarchical structure - With configurable max depth per menu
Multiple link types - Internal routes, external URLs, and linkable models (Pages or your own project models)
Drag & drop management - Intuitive tree interface for reordering and nesting items
Translation support - Multilingual menu labels with locale-aware URLs
Conditional visibility - Show/hide menu items without deleting them
Icon support - Optional icons for menu items (basic implementation currently)
Dynamic labels - Use model titles or custom labels for linked content

Adding a menu to Blade

The package includes a default built-in menu style which is developed in a generic way so that you can tweak its styling, by passing some attributes without having to publish the corresponding blade templates.

Example usage to have a horizontal menu using tailwind:

<x-flexible-pages-menu
    code="HEADER"
    style="default"
    ulClass="flex flex-row justify-start items-center gap-x-4"
    itemLinkClass="text-black hover:text-primary hover:underline"
    currentItemLinkClass="text-grey hover:no-underline"
/>

See the file ../tailwind/components/menu/default.blade.php for all possible attributes.

Adding linkable models

To make your models available in the menu builder, add them to the configuration:

// config/filament-flexible-content-block-pages.php
'menu' => [
    'linkable_models' => [
        \App\Models\Page::class,
        \App\Models\Product::class,
        \App\Models\Category::class,
    ],
],

Your models should implement the [HasMenuLabel](src/Models/Contracts/HasMenuLabel.php) contract and the HasMenuItemTrait trait:

use Statikbe\FilamentFlexibleContentBlockPages\Models\Contracts\HasMenuLabel;
use Statikbe\FilamentFlexibleContentBlockPages\Models\Concerns\HasMenuItemTrait;

class Product extends Model implements HasMenuLabel
{
    use HasMenuItemTrait;
    
    public function getMenuLabel(?string $locale = null): string
    {
        return $this->getTranslation('name', $locale ?? app()->getLocale());
    }
}

Tip: If you are using the Flexible Content Blocks title trait in your model, you can implement HasMenuLabel easily with HasTitleMenuLabelTrait.

Menu seeding

It makes a lot of sense to create most of the menu's in seeders, so they can be automatically synced over different environments. See the menu seeding documentation for programmatic menu creation.

For creating custom menu styles and advanced menu customization, see the menu customization documentation.

Settings

All settings are stored in one table in one record. The reason is to be able to add spatie medialibrary media as a config value. By using one record and a new media collection for each media setting, you can more easily add media. Furthermore, by manually adding a specific column for a setting, the data types are also correct and castable. In contrast, if we would use a key-value or JSON-based solution, not all our requirements could be served.

Each setting is cached and refreshed when the settings change.

Use settings

Access settings values using helper functions or static methods:

use Statikbe\FilamentFlexibleContentBlockPages\Models\Settings;

// Helper functions (recommended)
$siteTitle = flexiblePagesSetting(Settings::SETTING_SITE_TITLE);
$contactInfo = flexiblePagesSetting(Settings::SETTING_CONTACT_INFO, 'en', 'info@statik.be');
$seoImageUrl = flexiblePagesSettingImageUrl(Settings::COLLECTION_DEFAULT_SEO, Settings::CONVERSION_DEFAULT_SEO);

// Static methods
$siteTitle = Settings::setting(Settings::SETTING_SITE_TITLE);
$seoImageHtml = Settings::imageHtml(Settings::COLLECTION_DEFAULT_SEO, Settings::CONVERSION_DEFAULT_SEO);
$settings = Settings::getSettings();

To add custom settings fields and extend the settings functionality, see the settings extension documentation.

Routing

The package provides a flexible routing system that supports hierarchical page structures and multilingual sites.

URL Structure

Pages are organized in a three-level hierarchy:

Root pages: /about, /contact
Child pages: /services/web-development
Grandchild pages: /services/web-development/laravel

Route Registration

Register the package routes in your web.php file. Place this at the bottom of your routes file since page routes with slugs will catch many URLs:

// At the bottom of routes/web.php
\Statikbe\FilamentFlexibleContentBlockPages\Facades\FilamentFlexibleContentBlockPages::routes();

Generating URLs

Use the facade to generate URLs for pages:

use Statikbe\FilamentFlexibleContentBlockPages\Facades\FilamentFlexibleContentBlockPages;

// Generate URL for a page
$url = FilamentFlexibleContentBlockPages::getUrl($page);

// Generate URL for a specific locale
$url = FilamentFlexibleContentBlockPages::getUrl($page, 'en');

// OR there is a shorthand helper:
flexiblePageUrl($page, 'nl');

In Blade templates:

<a href="{{ flexiblePageUrl($page) }}">
    {{ $page->title }}
</a>

Route Helpers

The package includes two route helper implementations:

PageRouteHelper: For non-multilingual sites with simple URLs
LocalisedPageRouteHelper: For multilingual sites with localized URLs (e.g., /en/about, /nl/over-ons)

Configure which helper to use in your configuration file.

For advanced routing customization, custom route helpers, and controller extensions, see the routing customization documentation.

Redirects

The package includes automatic redirect management: when the slug of a page changes, a redirect from the old page to the new page is added. These redirects are stored in the database and are manageable with the Filament resource, so you can add your own redirects. For example, you can add handy redirects for marketing campaigns or quick links.

We have integrated spatie/laravel-missing-page-redirector, so you can easily configure other redirects in the spatie packages config.

Redirect middleware configuration

Prepend/append the RedirectsMissingPages.php middleware to your global middleware stack:

// bootstrap/app.php
->withMiddleware(function (Middleware $middleware) {
    $middleware->append([
        \Statikbe\FilamentFlexibleContentBlockPages\Http\Middleware\RedirectsMissingPages::class,
    ]);
})

Optional: If you want to hardcode a set of redirects, you can do this in the config file of the spatie package. Publish this package:

php artisan vendor:publish --provider="Spatie\MissingPageRedirector\MissingPageRedirectorServiceProvider"

Sitemap Generator

The package includes an automatic sitemap generator that creates XML sitemaps for your website with support for multilingual sites and various content types.

Features

Multiple generation methods - Manual, crawling, or hybrid approach
Multilingual support - Automatic hreflang tags for alternate language versions
Smart priority calculation - Homepage gets priority 1.0, parent pages 0.8, child pages 0.6
Dynamic change frequency - Based on last modification date (weekly, monthly, yearly)
Flexible content inclusion - Pages, routes, linkable models, and custom URLs
URL exclusion patterns - Skip specific URLs or patterns from the sitemap

Usage

Make sure the sitemap is enabled in the configuration. Generate the sitemap manually by running:

php artisan flexible-content-block-pages:generate-sitemap

The sitemap will be saved to public/sitemap.xml and can be accessed at https://yoursite.com/sitemap.xml.

Automatic Generation

You can schedule automatic sitemap generation in your routes/console.php:

$schedule->command('flexible-content-block-pages:generate-sitemap')
         ->daily()
         ->at('03:00');

For advanced configuration options, generation methods, linkable models setup, and extending the sitemap generator service, see the sitemap customisation documentation.

Tags and SEO Tag Pages

The package provides a comprehensive tagging system with SEO-optimized tag pages for content organization and search engine visibility. We make use of Laravel Tags so all features of this spatie package are available. While spatie uses a string for tag type, we have implemented a TagType model with extra SEO and styling functionality.

Features

Hierarchical tag system - Tags organized by customizable tag types (categories, topics, etc.)
Multilingual support - Translatable tag names, slugs, and SEO descriptions
SEO tag pages - Automatically generated landing pages with all content of a tag for search engine optimization
Visual organization - Custom colors and icons for tag types
Flexible routing - Customizable URL patterns for tag pages (default: /tag/{slug})

Tag Management

Create and manage tags through the Filament admin interface:

Tag Types - Define categories like "Topics", "Industries", or "Technologies"
Tags - Individual tags within each type with multilingual support
SEO Settings - Meta descriptions and tags can be enabled to have an SEO tag page
Visual Identity - Colors and icons for better organization

TODO screenshot

Tag Types

Tag types provide structure and organization. You can add more specific tag types, e.g. for news articles only.

// Built-in tag types
TagType::TYPE_DEFAULT = 'default';  // General purpose tags
TagType::TYPE_SEO = 'seo';         // SEO-focused tags with landing pages

Key features:

Default type - One tag type can be marked as default for new tags
SEO pages - Enable has_seo_pages to generate landing pages for tags of this type and an SEO description can be filled in that will be shown on the tag page for more context.
Visual styling - Custom colors and SVG icons for admin interface
Translatable names - Support for multiple languages

SEO Tag Pages

When enabled (has_seo_pages = true on tag type), the package automatically generates SEO-optimized landing pages. The HTML of the tag pages is focused on the data structure for search engines and is not styled. If you also want to use this for other purposes, you can publish the views and style it.

Content Inclusion: SEO tag pages display content from models configured in tag_pages.models.enabled:

// config/filament-flexible-content-block-pages.php
'tag_pages' => [
    'models' => [
        'enabled' => [
            \Statikbe\FilamentFlexibleContentBlockPages\Models\Page::class,
            \App\Models\BlogPost::class,  // Your custom models
        ],
    ],
],

SEO Benefits:

Automatic meta tags and descriptions
Multilingual hreflang tags
Content grouping by type or chronologically
Pagination for large content sets
Search engine friendly HTML structure
Tag pages are added to the sitemap

For advanced tag page customization, extending models, custom controllers, and template customization, see the SEO tag pages documentation.

For tag configuration options, URL patterns, and content inclusion settings, see the configuration documentation.

Authorisation

Authorisation setup is not included in this package. Most projects will use an authorisation strategy project-wide, e.g. via policies.

However authorisation can be easily implemented. There are two easy strategies:

Use the panel and implement a simple access rule for the panel on the user model in canAccessPanel(Panel $panel).
Remove the unwanted resources from the resources configuration.
Use a Filament authorisation library, like Filament Shield. Shield can automatically generate policies with permissions that you can link to specific roles.

Configuration

The package provides extensive configuration options to customize models, resources, database tables, and various features. You can modify the published configuration file to match your application's requirements.

For detailed configuration options and examples, see the configuration documentation.

If you want to further customise or extend the functionality, have a look at the options.

TODO's

check:

do install docs work
Seppe: tailwind config complete? do we need to add flexible content blocks styling?
Seppe: menu components ok?

release:

policies:
- note: undeletable pages
undeletable page toggle only for permission holder
Kristof: screenshots + banner + packagist + slack + filament plugin store

Future work

Caching of the menu data structure.
Add menu item for subtitle in menus.
A model to store re-usable content blocks, e.g. to create a marketing banner that can be reused on many pages, and edited once.
Contact form
FAQ model, resource and flexible blocks
A component to put on the pages with a quick link to edit this page in Filament
A trait for page indexing in Laravel Scout

Development

To update all table of content sections in the documentation files, run:

update_toc.sh

Changelog

Please see CHANGELOG for more information on what has changed recently.

Contributing

Please see CONTRIBUTING for details.

Security Vulnerabilities

Please review our security policy on how to report security vulnerabilities.

Credits

Used packages

We built this on the shoulders of others by combining several Laravel packages into a cohesive CMS solution, making it opinionated. We would like to thank the developers and contributors of the following packages:

License

The MIT License (MIT). Please see License File for more information.

statikbe / laravel-filament-flexible-content-block-pages

Maintainers

Details

README

Key Features

Table of contents

Installation

Laravel Filament Flexible Content Blocks

Laravel Localization

Laravel Tags

Setup in your project

Translations

Routes

Filament panel

Redirects

Schedule

Page management

Features

Creating Pages

Page Hierarchy

Publication Controls

Multilingual Support

Frontend Integration

Menu builder

Features

Adding a menu to Blade

Adding linkable models

Menu seeding

Settings

Use settings

Routing

URL Structure

Route Registration

Generating URLs

Route Helpers

Redirects

Redirect middleware configuration

Sitemap Generator

Features

Usage

Automatic Generation

Tags and SEO Tag Pages

Features

Tag Management

Tag Types

SEO Tag Pages

Authorisation

Configuration

TODO's

Future work

Development

Changelog

Contributing

Security Vulnerabilities

Credits

Used packages

License