Download the PHP package backpack/pagemanager without Composer

BackPack\PageManager

An interface to let your admins add and edit presentation pages to your Laravel 6, 7, 8, 9, 10, 11 or 12 website, by defining page templates with any number of content areas and any number of content types. Uses Laravel Backpack.

Security updates and breaking changes

Please subscribe to the Backpack Newsletter so you can find out about any security updates, breaking changes or major features. We send an email every 1-2 months.

Install

1) Add a file to define your page templates in :

2) In your terminal

3) Publish the views, migrations and the PageTemplates trait:

4) Run the migration to have the database table we need:

5) [optional] Add a menu item for it:

Usage

1. Go to yourapp/admin/page and see how it works.
2. Define your own templates in app/PageTemplates.php using the Backpack\CRUD API.

Example front-end

No front-end is provided (Backpack only takes care of the admin panel), but for most projects this front-end code will be all you need:

(1) Create a catch-all route at the end of your routes file:

(2) Create that actually shows the page.

(3) Create the views for those templates (how those pages actually look - the HTML CSS JS) and place them in your directory. Inside those blade files, you can use the variable. That's where all the page content is stored. For more complicated pages, you can also use fake fields in your page templates. You'll also find those attributes in the variable.

Note: if you find yourself in need of sending extra data to a view you load on multiple pages, you should consider using a view composer;

Extend

If you need to make any modifications to the controller, model or request, you should:

• make sure is published; if not, publish it using ;
• create a new controller/model that extends the one in the package;
• enter controller or model in the pagemanager.php config file, and that's the one that the CRUD will be using;

Optional: Mutator for fields using 'store_in' and 'fake' keys

Fake fields do not trigger individual mutators, they trigger the "fake column" mutator. For example instead of defining a setImageAttribute() mutator, please define a setExtrasAttribute() mutator. You'll have the $value then.

Change log

Please see CHANGELOG for more information what has changed recently.

Testing

Contributing

Please see CONDUCT for details.

Overwriting Functionality

If you need to modify how this works in a project:

• create a file; the package will see that, and load your routes file, instead of the one in the package;
• create controllers/models that extend the ones in the package, and use those in your new routes file;
• modify anything you'd like in the new controllers/models;

Security

If you discover any security related issues, please email [email protected] instead of using the issue tracker.

Credits

• Cristian Tabacitu
• All Contributors

License

Backpack is free for non-commercial use and 69 EUR/project for commercial use. Please see backpackforlaravel.com for more information.

Hire us

We've spend more than 10.000 hours creating, polishing and maintaining administration panels on Laravel. We've developed e-Commerce, e-Learning, ERPs, social networks, payment gateways and much more. We've worked on admin panels so much, that we've created one of the most popular software in its niche - just from making public what was repetitive in our projects.

If you are looking for a developer/team to help you build an admin panel on Laravel, look no further. You'll have a difficult time finding someone with more experience & enthusiasm for this. This is what we do. Contact us - let's see if we can work together.