<p align="center"><img src="https://raw.githubusercontent.com/statikbe/laravel-filament-flexible-content-blocks/main/documentation/img/banner-laravel-filament-flexible-content-blocks.png" alt="Laravel Filament Flexible cContent Blocks"></p>
# Laravel Filament Flexible Content Blocks
[](https://packagist.org/packages/statikbe/laravel-filament-flexible-content-blocks)
[](https://github.com/statikbe/laravel-filament-flexible-content-blocks/actions?query=workflow%3Arun-tests+branch%3Amain)
[](https://github.com/statikbe/laravel-filament-flexible-content-blocks/actions?query=workflow%3A"Fix+PHP+code+style+issues"+branch%3Amain)
[](https://packagist.org/packages/statikbe/laravel-filament-flexible-content-blocks)
The Laravel Filament Flexible Content Blocks package helps you to easily create content in Filament for any
model, with predefined blocks, and for each block an extendable Blade view component.
You can use this opinionated package to create a basic CMS, by setting up your own page model and implementing the predefined traits to
select the functionality you need, then quickly setup a Filament resource by implementing the ready-made fields. Or you can
add flexible content to a model for your specific business case, for instance to allow the flexible creation of a
product description. Each project is different and to foster changing requirements, the focus is on the building blocks and
not a default implementation for a CMS-like page.
The key goals of this package are:
- provide a quick way to add content to a model through reusable fields and content blocks
- quickly set up the frontend and allow different frontend stylings for each block
- have fully-working, extendable Blade view components with basic Tailwind styling
- allow the liberty to pick and choose which fields and blocks you need for your requirements
- provide easy configuration to override the behaviour of the fields, blocks and image conversions
- support SEO
- support overview fields to display the content in a list with custom title, image and description
- support content translations
- provide a start set of content blocks for most general requirements
:sparkles: **New features:**
- Improved styling of the blocks in Filament to improve UX when editing many blocks.
- Replicate action to copy the model with content blocks and its images.
- Content block previews! You can now show a preview of what the block looks like on the actual page, styled with the
correct stylesheet. See [the preview block configuration](documentation%2Fconfiguration.md#block-previews).
- :art: Simple asset manager, see [Filament Flexible Blocks Asset Manager](https://github.com/statikbe/laravel-filament-flexible-blocks-asset-manager)
- Filament theme to easily render content blocks within Filament.
- [Laravel Boost](https://laravel.com/ai/boost) skills.
**NOTE:**
:rocket: For a complete, out-of-the-box, content management solution, check out our new [Filament Flexible Content Block Pages](https://github.com/statikbe/laravel-filament-flexible-content-block-pages) package with page management,
a menu builder, tag management and many SEO features.
## Versions & compatibility
| Filament Version | Package Version | Development Branch |
|---|---|---|
| v3 | `statikbe/laravel-filament-flexible-content-blocks:^3.0` | `v3` |
| v4 & v5 | `statikbe/laravel-filament-flexible-content-blocks:^4.0` | `main` |
## Upgrades
### Upgrade to v2
The image conversions in the configuration file have changed due to a refactor of spatie-medialibrary v11. Check [the
upgrade guide](./UPGRADE.md) for details.
### Upgrade to v1
If you need to upgrade to v1.0.0 it is **IMPORTANT** to [read the upgrade guide thoroughly](./UPGRADE.md), because the data model of the
content blocks has changed and needs to be upgraded via a command.
## Installation
You can install the package via composer:
```bash
composer require statikbe/laravel-filament-flexible-content-blocks
```
You will most likely need to edit [the extensive configuration](#configuration), so you can publish the config file with:
```bash
php artisan vendor:publish --tag="filament-flexible-content-blocks-config"
```
Optionally, you can publish the views (e.g. if you want to tweak the content blocks) using:
```bash
php artisan vendor:publish --tag="filament-flexible-content-blocks-views"
```
Since you can apply the flexible content blocks to any view, we do not provide required or default migrations.
However, we provide two example migrations, one for a translatable page and one for a single-language page.
You can use these migrations as an example to create your own migrations. (see [ToDo's](#todo))
You can publish and run the migrations with:
```bash
php artisan vendor:publish --tag="filament-flexible-content-blocks-migrations"
#first edit the migrations and then run:
php artisan migrate
```
### Optional installation steps
When you want to use the [BackgroundVideo](src/View/Components/BackgroundVideo.php) component, you have to make sure that the javascript files, which
are used by the component, are available in your project. To do this, you have to publish the compiled
javascript assets by using:
```bash
php artisan vendor:publish --tag="filament-flexible-content-blocks-assets"
```
To automate the above, so that these assets will be re-published each time you perform a composer update, you
can add the following publish command within the `scripts.post-update-cmd` array of your `composer.json`:
```json
{
"scripts": {
"post-update-cmd": [
"@php artisan vendor:publish --tag=filament-flexible-content-blocks-assets --force"
]
}
}
```
## Dependencies
This is an opinionated package with batteries included. So we picked a set of dependencies to build upon.
Here is a brief overview of the choices made:
- `filament/filament`: obviously ;-)
- `spatie/laravel-medialibrary` & `filament/spatie-laravel-media-library-plugin`: all image handling is done with `spatie/medialibrary`
- `spatie/laravel-sluggable`: for slugs
- `spatie/laravel-translatable`: for translations as this works together with the first party filament translatable package.
- `dereuromark/media-embed`: to support video embeds of [various media services](https://github.com/dereuromark/media-embed/blob/master/docs/supported.md).
- `openai-php/laravel`: to generate content and add other smart features ;-).
## Usage
If you are looking for a CMS-like page builder that makes use of this content blocks package, check out our [Filament Flexible Content Block Pages](https://github.com/statikbe/laravel-filament-flexible-content-block-pages).
If you want to apply it to a different context, there is [an example project](https://github.com/statikbe/laravel-filament-package-sampler) of all the package features, which includes:
- migrations
- data models for default & translatable pages
- Filament resources & pages
- Http controllers
- views
- a data seeder to generate test pages
You can use this as a starting point to see how the package can be used for a CMS pages.
Below we briefly discuss how to setup a migration, a model and a Filament resource in four steps. In the future,
we want to add question-based commands to create these, see [roadmap](#roadmap).
### 1. Setup migrations
You can start from [the example migrations that can be published](#installation). Then prune and pick the fields that fit
your requirements, note that some model traits need a combination of fields, e.g. the hero image needs both `hero_image_copyright` and
`hero_image_title`. The clusters are commented in the migration or have a look in [the model traits](src/Models/Concerns) to get an idea.
### 2. Setup the model
If you do not have a model yet, create one with `php artisan make:model`, then you can add the interfaces and its default
implementation via traits. Below is an overview of the provided interfaces and traits and their functionality:
#### __[HasPageAttributes](src%2FModels%2FContracts%2FHasPageAttributes.php)__:
This adds a title and publishing begin and end date variables, together with functions and scopes to help with
finding published models. Implement this interface with the trait [HasPageAttributesTrait](src%2FModels%2FConcerns%2FHasPageAttributesTrait.php)
or [HasTranslatedPageAttributesTrait](src%2FModels%2FConcerns%2FHasTranslatedPageAttributesTrait.php)
for translated content.
#### __[HasIntroAttribute](src%2FModels%2FContracts%2FHasIntroAttribute.php)__:
This adds an introduction text variable. Implement this interface with the trait [HasIntroAttributeTrait](src%2FModels%2FConcerns%2FHasIntroAttributeTrait.php)
or [HasTranslatedIntroAttributeTrait](src%2FModels%2FConcerns%2FHasTranslatedIntroAttributeTrait.php).
#### __[HasCode](src%2FModels%2FContracts%2FHasCode.php)__:
Adds a code variable to be able to select a specific content model in your source code by string instead of a
varying id or slug. For instance, this is useful to look up a home page. Implement this with the trait [HasCodeTrait](src%2FModels%2FConcerns%2FHasCodeTrait.php).
#### __[HasHeroImageAttributes](src%2FModels%2FContracts%2FHasHeroImageAttributes.php)__:
Adds a hero image as well as a title (e.g. for accessibility in `alt` tags) and copyright variable to the model. This can
be implemented with [HasHeroImageAttributesTrait](src%2FModels%2FConcerns%2FHasHeroImageAttributesTrait.php) and
[HasTranslatedHeroImageAttributesTrait](src%2FModels%2FConcerns%2FHasTranslatedHeroImageAttributesTrait.php).
#### __[HasHeroVideoUrlAttribute](src/Models/Contracts/HasHeroVideoAttribute.php)__:
Adds a hero video URL that can be used to create a hero with a video playing in the background.
This can be implemented with [HasHeroVideoAttributeTrait](src/Models/Concerns/HasHeroVideoAttributeTrait.php) and
[HasTranslatedHeroVideoUrlAttributeTrait](src/Models/Concerns/HasTranslatedHeroVideoUrlAttributeTrait.php).
#### __[HasContentBlocks](src%2FModels%2FContracts%2FHasContentBlocks.php)__:
Adds a JSON column to your model to store the data of the flexible content blocks.
This is required if you want to use the flexible content blocks. Implement it with
[HasContentBlocksTrait](src%2FModels%2FConcerns%2FHasContentBlocksTrait.php) or
[HasTranslatedContentBlocksTrait](src%2FModels%2FConcerns%2FHasTranslatedContentBlocksTrait.php).
#### __[HasMediaAttributes](src%2FModels%2FContracts%2FHasMediaAttributes.php)__:
This provides some helper functions for handling media.
You do not need to add traits, since the trait will be included by other traits that handle images.
#### __[HasTranslatableMedia](src%2FModels%2FContracts%2FHasTranslatableMedia.php)__:
If you want to support translatable media (e.g. a different image for each locale), include this interface.
The implementation is done by the trait [HasTranslatedAttributesTrait.php](src%2FModels%2FConcerns%2FHasTranslatedAttributesTrait.php).
The traits that implement translatable images, will make use of this implementation to keep track of the media that needs
translation.
#### __[HasOverviewAttributes](src%2FModels%2FContracts%2FHasOverviewAttributes.php)__:
Overview fields can be used to display the content models as brief snippets in lists, for instance a list of news articles.
Implement this with [HasOverviewAttributesTrait](src%2FModels%2FConcerns%2FHasOverviewAttributesTrait.php) or
[HasTranslatedOverviewAttributesTrait](src%2FModels%2FConcerns%2FHasTranslatedOverviewAttributesTrait.php).
#### __[HasSEOAttributes](src%2FModels%2FContracts%2FHasSEOAttributes.php)__:
This adds a new title, description, image and keywords for SEO. It provides fallbacks to the regular title, intro
and hero image if no SEO fields are completed. Implement the
[HasSEOAttributesTrait](src%2FModels%2FConcerns%2FHasSEOAttributesTrait.php) or the
[HasTranslatedSEOAttributesTrait](src%2FModels%2FConcerns%2FHasTranslatedSEOAttributesTrait.php) for translatable content.
#### __[Linkable](src%2FModels%2FContracts%2FLinkable.php)__:
Add this interface if you want to use the model to link in call-to-actions to create dynamic URL's, or if you want to
use the view action in the Filament table. The interface asks you to implement two functions one to get the url where the
content can be publicly viewed and another to view the unpublished content.
There is no default implementation trait, because this package is unaware of the used routes and controllers.
#### Slugs:
For slug support you can include the [HasSlugAttributeTrait](src%2FModels%2FConcerns%2FHasSlugAttributeTrait.php) or the
[HasTranslatedSlugAttributeTrait](src%2FModels%2FConcerns%2FHasTranslatedSlugAttributeTrait.php) for translatable slugs.
If you use translatable slugs, please change [the page routing the Filament Resource](#resource-with-translated-slugs).
#### Parent-child content aka subpages:
To support hierarchical content you can include the [HasParent](src%2FModels%2FContracts%2FHasParent.php) interface and
the implementation is done by [HasParentTrait](src%2FModels%2FConcerns%2FHasParentTrait.php).
If you want to implement a nested URL structure, check [this documentation](documentation%2Fparent-child.md).
### 3. Setup the Filament resource
Create a filament resource and its page with the filament command.
If your model is translatable, add the [`FlexibleContentBlocksTranslatable`](./src/Filament/Resource/Concerns/FlexibleContentBlocksTranslatable.php)
trait, to use the locales configured by this package.
#### Setup the table
There are few column fields provided by the package and a filter to select published/unpublished models.
Below is an overview of all available columns in a code sample:
```php
public static function table(Table $table): Table {
return $table->columns([
TitleColumn::create(),
PublishedColumn::create(),
])
->filters([
PublishedFilter::create(),
])
->actions([
Tables\Actions\EditAction::make(),
PublishAction::make(),
ReplicateAction::make(),
])
->bulkActions([
Tables\Actions\DeleteBulkAction::make(),
]);
}
```
#### (optional) Adding a ViewAction to your table
If your model uses the [`Linkable`](src%2FModels%2FContracts%2FLinkable.php) interface, you can also use the
provided `ViewAction` in your table.
This action will simply open the url returned by the `getViewUrl()` method on your model.
```php
use Statikbe\FilamentFlexibleContentBlocks\Filament\Table\Actions\ViewAction;
->actions([
Tables\Actions\EditAction::make(),
PublishAction::make(),
ViewAction::make(), // <-- Add this
])
```
#### (optional) Adding a ReplicateAction to your table
If you want to be able to replicate the model record, you can add the `ReplicateAction`.
This action will copy all data attributes and also copy all media/images of the record.
```php
use Statikbe\FilamentFlexibleContentBlocks\Filament\Table\Actions\ViewAction;
->actions([
Tables\Actions\EditAction::make(),
PublishAction::make(),
ReplicateAction::make(), // <-- Add this
])
```
#### Setup the form
And then you can implement the `form()` function with Filament fields provided by the package. Below is an example with tabs.
Note that we sometimes make use of `create()` static functions, because we want to set the
names to the fixed variables used in the models. Some fields in the example are bundled in groupings
(e.g. [SEOFields](src%2FFilament%2FForm%2FFields%2FGroups%2FSEOFields.php)), you can also use the single fields if you
want make a custom layout.
```php
public static function form(Form $form): Form {
return $form
->schema([
Tabs::make('Heading')
->columnSpan(2)
->tabs([
Tab::make('General')
->schema([
TitleField::create(true),
SlugField::create(),
PublicationSection::create(),
AuthorField::create(),
HeroImageSection::create(),
IntroField::create(),
ParentField::create(),
]),
Tab::make('Content')
->schema([
ContentBlocksField::create(),
]),
Tab::make('Overview')
->schema([
OverviewFields::make(1),
]),
Tab::make('SEO')
->schema([
SEOFields::make(1),
]),
]),
]);
}
```
If you have translatable content, you need to include the traits and language switch field of the [`filament/spatie-laravel-translatable-plugin`](https://filamentphp.com/docs/2.x/spatie-laravel-translatable-plugin/installation) to
[the resource](https://filamentphp.com/docs/2.x/spatie-laravel-translatable-plugin/getting-started#preparing-your-resource-class)
and its [pages](https://filamentphp.com/docs/2.x/spatie-laravel-translatable-plugin/getting-started#making-resource-pages-translatable).
**Important:** On the edit page, you need to use the [EditRecord\Concerns\TranslatableWithMedia](src%2FFilament%2FPages%2FEditRecord%2FConcerns%2FTranslatableWithMedia.php) trait if you use translatable images.
And on the create page use [CreateRecord\Concerns\TranslatableWithMedia](src%2FFilament%2FPages%2FCreateRecord%2FConcerns%2FTranslatableWithMedia.php).
#### <a name="resource-with-translated-slugs"></a> Note on translated slugs
If you are using translated slugs on your model, it is possible that you create a new model instance without a translated slug.
When you then switch to the language without a translated slug, Filament uses the slug as the route binding key as
defined in the model class. This will result in an error since the slug translation does not yet exist. To solve this it is
easiest to use the ID as route binding key in Filament instead of the slug. You can do this by changing the page urls in
the Filament resource class, so that they do not try to resolve the object with `/{record}/edit`, but use the ID attribute
`/{record:id}/edit`. Then set the `$recordRouteKeyName` of the Filament resource to `id`.
```php
protected static ?string $recordRouteKeyName = 'id';
public static function getPages(): array
{
//note: replace the page classes!
return [
'index' => Pages\ListArticles::route('/'),
'create' => Pages\CreateArticle::route('/create'),
'edit' => Pages\EditArticle::route('/{record:id}/edit'),
];
}
```
### 4. Setup the controller and Blade view
Now you need to create a controller and `GET` route that returns a Blade view to display your content. See the example code for [controller examples](example%2Fapp%2FHttp).
We provide Blade components for all fields (except SEO fields). Below is an example of a simple Blade template,
where the model is passed to this view as `$page` variable. The `<x-flexible-hero>` component renders a default hero with
title and full screen image, and the `<x-flexible-content-blocks>` component renders all the content of each block.
__Note:__ The `x-flexible-hero` component requires [Alpine.js](https://alpinejs.dev/).
```html
<x-layouts.flexible title="{{ $page->getTitle() }}" wide="true">
<x-flexible-hero :page="$page" />
<div>
<x-flexible-content-blocks :page="$page">
</x-flexible-content-blocks>
</div>
</x-layouts.flexible>
```
If you want to customise these component views, you can [publish the views](#installation).
You can use the SEO library of your preference to render the SEO tags on the page, e.g. with [`artesaos/seotools`](https://github.com/artesaos/seotools).
### 5. Configure tailwind
Do the step below to ensure that tailwind will pick up the css classes used by the flexible content blocks components.
1. In the tailwind CSS file (probably in `resources/css/filament/admin/theme.css`) of your filament back-end, add the following line:
```
@source '../../../../resources/views/filament';
```
2. Likewise, in the CSS of your front-end, add the following lines:
```
@source "../../vendor/statikbe/laravel-filament-flexible-content-blocks/**/*.blade.php";
@source "../../config/filament-flexible-content-blocks.php";
```
## Themes
The package ships several sets of Blade views ("themes") that decide how the blocks are rendered. Pick one with the `theme` option in `config/filament-flexible-content-blocks.php`:
```php
'theme' => 'tailwind', // 'tailwind' (default), 'bootstrap4-kul' or 'filament'
```
Each theme is a directory of views under `resources/views/content-blocks/<theme>` and `resources/views/components/<theme>`. To tweak the markup of a theme, [publish the views](#installation) and edit the copies under `resources/views/vendor/filament-flexible-content-blocks`.
| Theme | Use case |
|-------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| `tailwind` | Public, front-end pages styled with Tailwind (the default, see [Setup the controller and Blade view](#4-setup-the-controller-and-blade-view)). |
| `bootstrap4-kul` | Front-end pages on a [Bootstrap 4 design system for KULeuven](https://stijl.kuleuven.be/releases/1.0.2/stijlgids/). |
| `filament` | Renders the blocks with native Filament UI components so the content displays *inside* a Filament panel — e.g. a read-only "view" page for editorially-managed content — instead of a public front-end. Useful for documentation pages inside Filament. |
### Filament theme
Enable it in [the config](./documentation/configuration.md#frontend-theme):
```php
'theme' => 'filament',
```
Because this theme is built on Filament's own components (`<x-filament::section>`, `<x-filament::button>`, `<x-filament::link>`), its classes have to be compiled by your **Filament panel theme**, not your front-end CSS. Create a [custom Filament theme](https://filamentphp.com/docs/styling/overview#creating-a-custom-theme) and add the following to its CSS (e.g. `resources/css/filament/admin/theme.css`):
1. The typography plugin — the text and rich-text blocks render with `prose`:
```css
@plugin '@tailwindcss/typography';
```
2. `@source` directives so Tailwind scans the theme's views **and the package config**. The image-width and background-colour utility classes are defined in the config file (not in the Blade), so it has to be scanned too:
```css
/* the first line covers published views, the second the package defaults */
@source '../../../../resources/views/vendor/filament-flexible-content-blocks/**/*.blade.php';
@source '../../../../vendor/statikbe/laravel-filament-flexible-content-blocks/resources/views/**/*.blade.php';
@source '../../../../config/filament-flexible-content-blocks.php';
```
3. Styling for the background-colour classes. Each block outputs the class name configured under `background_colours` in the config file (`content-block_bg--default`, `content-block_bg--primary`, …) — the theme applies the class, your CSS decides how it looks. The default option is meant to be a no-op so the block stays flat; the others can be turned into tinted panels, for example:
```css
.content-block_bg--default {
/* keep the block flat: no background, border or padding */
}
.content-block_bg--primary,
.content-block_bg--secondary,
.content-block_bg--light {
padding: 1.5rem;
border: 1px solid var(--color-gray-200);
border-radius: 0.75rem;
}
.dark .content-block_bg--primary,
.dark .content-block_bg--secondary,
.dark .content-block_bg--light {
border-color: var(--color-gray-700);
}
.content-block_bg--primary { background-color: var(--color-primary-50); }
.dark .content-block_bg--primary { background-color: var(--color-primary-950); }
.content-block_bg--secondary { background-color: var(--color-gray-100); }
.dark .content-block_bg--secondary { background-color: var(--color-gray-800); }
.content-block_bg--light { background-color: var(--color-gray-50); }
.dark .content-block_bg--light { background-color: var(--color-gray-900); }
```
Then rebuild the theme (`npm run build`, `vite build`, or your project's build command).
## AI features
We are dreaming up some exciting new AI-based features to ease content creation and translation. The first has arrived:
### SEO fields generation
There is a form action `SEOAIAction` that generates an SEO title, description and tags based on the model's content.
To enable this, you should complete the configuration of [the OpenAI library](https://github.com/openai-php/laravel).
Do not forget to run the install command:
```
php artisan openai:install
```
Create an OpenAI API key and set this up in the `.env` file of your project:
```shell
OPENAI_API_KEY=sk-...
OPENAI_ORGANIZATION=org-...
```
You will find the SEO AI action already set up in the `SEOFields` group.
### AI development
There is [Laravel Boost](https://laravel.com/ai/boost) support for [AI coding agents](#ai-coding-agents).
## Blocks
To build your content, the package provides the default blocks listed below.
### Text with image block
Additionally to the text block, you can add an image with its title and copyright. The image can be positioned left or
right of the text and an image conversion and background colour of the block can be set. One can also add a call-to-action
button with configured button styles. You can link to URL's, but also dynamically to other models or routes.
### Image block
This displays an image with copyright message and you can set image conversions, the position and the width the image
should use on the page.
### Video block
You can embed videos from [numerous media services](https://github.com/dereuromark/media-embed/blob/master/docs/supported.md)
and set an overlay image that will cause the video embed to be lazy loaded after clicking the image.
### Quote block
A block to show a quote and it's author.
### HTML block
A block to insert custom HTML.
### Call-to-action block
This block focuses on adding call-to-actions with image and text.
### Overview block
This block can be used to display the overview fields and image of other model records, e.g. for displaying related blog posts.
One can configure the grid columns and background colour.
### Cards block
This block is comparable to the overview block, however you can add the title, description, image and CTA for each card.
The image conversion, background colour and grid columns can be configured.
### Template block
You can select Blade templates that you want to include. This can be handy to add small forms or interactive components,
e.g. a newsletter signup form or a map.
### Create your own custom block
You can easily create your own content block by extending [AbstractContentBlock](src%2FContentBlocks%2FAbstractContentBlock.php).
__Note:__ Do NOT use [AbstractFilamentFlexibleContentBlock.php](src%2FContentBlocks%2FAbstractFilamentFlexibleContentBlock.php)
to extend from, because this super class contains logic to add the package's own namespace to the custom block.
## AI coding agents
This package ships [Laravel Boost](https://laravel.com/framework/docs/boost) guidelines and agent skills,
so AI coding agents know how to work with it. If your project has Boost installed, run
`php artisan boost:install` (or `php artisan boost:update --discover`) and the following are installed
for the agents you selected:
- __AI guidelines__: a short overview of the package, loaded upfront.
- __`filament-flexible-content-blocks-setup` skill__: wiring the package onto a model - migration, model
contracts and traits, the Filament resource form and table, the front-end Blade view and Tailwind sources.
- __`filament-flexible-content-blocks-custom-block` skill__: writing a custom content block, including a
block class and Blade view template to start from. It explains, amongst others, that custom blocks must
extend [AbstractContentBlock](src%2FContentBlocks%2FAbstractContentBlock.php) and never
[AbstractFilamentFlexibleContentBlock](src%2FContentBlocks%2FAbstractFilamentFlexibleContentBlock.php).
The sources live in [`resources/boost`](resources%2Fboost).
## Configuration
A lot of the customisation of content blocks and their behaviour can be done through the configuration file.
Please, consult [the configuration documentation](documentation%2Fconfiguration.md).
## Package development
See [DEV.md](src/DEV.md)
## Roadmap
Below is a list of ideas and missing features. PR's are welcome!
- ~~Command to generate migrations~~, use the new [Filament Flexible Content Block Pages](https://github.com/statikbe/laravel-filament-flexible-content-block-pages)
- ~~Command to generate models~~, use the new [Filament Flexible Content Block Pages](https://github.com/statikbe/laravel-filament-flexible-content-block-pages)
- ~~Command to generate Filament resource and pages~~, use [Filament Flexible Content Block Pages](https://github.com/statikbe/laravel-filament-flexible-content-block-pages)
- ~~Integrate image asset manager~~, see [Filament Flexible Blocks Asset Manager](https://github.com/statikbe/laravel-filament-flexible-blocks-asset-manager)
- Store links to models in rich editor
- ~~Redirects~~, see
- Reusable blocks. Name: global block?
- Focal point for image resizing
- Widget to show which records do not have a translated version
## Changelog
Please see [CHANGELOG](CHANGELOG.md) for more information on what has changed recently.
## Contributing
Please, submit bugs or feature requests via the [Github issues](https://github.com/statikbe/laravel-filament-chained-translation-manager/issues).
Pull requests are welcomed! Thanks!
## Security Vulnerabilities
Please review [our security policy](../../security/policy) on how to report security vulnerabilities.
## Credits
- [Sten Govaerts](https://github.com/sten)
- [Seppe Van Besauw](https://github.com/sevbesau)
- [All Contributors](../../contributors)
## License
The MIT License (MIT). Please see [License File](LICENSE.md) for more information.
Read the source README