You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
To create a block you simply execute the command php artisan make:block SwiperHomepage for example. This creates a class where you have to declare what fields you want for this block (text, rich_text, color, upload_image, select, repeatable). You can also enable multilanguage on text and rich_text.
And we also create a block blade file where you can also push scripts and styles in a stack.
The source code for this demo you can find in the example folder. The example project also uses docker-compose and sqlite, this way is super easy to play with this project.
Note: The reason this project is called customberg-php and not customberg-for-backpack is because I plan to make this framework and admin-panel agnostic (meaning it will work in other admin panels and other frameworks as well). I'm not sure if I need separate packages for all admin-panels or I can keep everything under the same repo/package.
The text was updated successfully, but these errors were encountered:
Hi !
I created this plugin that uses VanOns/laraberg under the hood and allows you to create gutenberg blocks only using php.
https://github.com/customberg/customberg-php
To create a block you simply execute the command
php artisan make:block SwiperHomepage
for example. This creates a class where you have to declare what fields you want for this block (text, rich_text, color, upload_image, select, repeatable). You can also enable multilanguage on text and rich_text.And we also create a block blade file where you can also push scripts and styles in a stack.
The source code for this demo you can find in the example folder. The example project also uses docker-compose and sqlite, this way is super easy to play with this project.
Note: The reason this project is called customberg-php and not customberg-for-backpack is because I plan to make this framework and admin-panel agnostic (meaning it will work in other admin panels and other frameworks as well). I'm not sure if I need separate packages for all admin-panels or I can keep everything under the same repo/package.
The text was updated successfully, but these errors were encountered: