Content Pages

The pages component is a very powerful content management functionality that allows you to quickly convert a static Laravel page into a dynamic page that can be modified from the admin panel.

In order to provide you with a complex crud functionality inside the admin, the pages crud implements the following out of the box:

Admin Interface

Before going deeper, you should know that there's already a section in the admin from where you can manage all your pages.

You can find the pages section inside Admin -> Manage Content -> Pages.
Feel free to explore all available options this section offers.

Pages List

How It Works

First of all, let's understand the architecture behind content pages and their workflow.

The Workflow

Configuration File

The pages component comes bundled with a config/varbox/pages.php config file.

From here you can specify what page types your application contains and a custom upload configuration for pages only, if you happen to use file uploads.

You should specify a new page type only if you want to dispatch the request to another controller or action, or if you have different block locations in that page.

You should specify a custom upload config only if your pages use file uploads and you want to overwrite the default configuration.

Controller Dispatcher

By default the config/varbox/pages.php config file comes with a single page type called default so any pages created from the admin will point to App\Http\Controllers\PagesController@show

You can customize to what controller and method to dispatch the route of a page, either by modifying the default type configuration or by adding a new page type

Specifying custom route dispatches for some of your pages might be a good idea if you have different content pages that also hold different additional logic, thus keeping your controllers and methods clean.


Let's see the most common things you can do using content pages.

Display Frontend Page

After you've created a page from inside the admin, it's time to display its contents in your frontend.

Initially if you access that page's url in your browser, you'll get an error saying that view doesn't exist. This happens because behind the scenes, when you're accessing that url, the request is dispatched to App\Http\Controllers\PagesController specifically to the show method.

For more information, you can inspect that controller in order to fully grasp what it does.

All you have to do in order to display that page's information in your frontend is to create the resources/views/pages/show.blade.php view file.

<h1>{{ $page->data['title'] }}</h1>
<h2>{{ $page->data['subtitle'] }}</h2>

{!! $page->data['content'] !!}

Create New Page Type

To create a new page type, go to config/varbox/pages.php and under the types section, add your new page type configuration. The newly created page type will then be available inside the admin, when creating / updating a page.

You should create a new page type only if you want a different route dispatch or if you plan on using different or no block locations.

'types' => [

    'your-type' => [
        'controller' => '\App\Http\Controllers\YourController',
        'action' => 'yourMethod',
        'locations' => [
            'yourBlockLocation1', 'yourBlockLocation2'


After this, you just have to create the specified controller with the specified method that will contain your logic.

Add Extra Page Fields

More often than not, in your applications you'll want additional fields for your pages.

By default, the pages component exposes the "title", "subtitle" and "content" fields.
Those fields are all part of the data column from the pages database table.

To add or remove fields for pages, you can just modify the blade view file with your extra fields (make them part of the data column). The blade file you should modify is located at: resources/views/vendor/varbox/admin/pages/_form.blade.php

<div class="col-md-12">
    {!! form_admin()->text('data[author]', 'Author') !!}
<div class="col-md-12">
    {!! form_admin()->textarea('data[intro]', 'Intro') !!}

You can then reference those fields in your resources/views/pages/show.blade.php like this:

<span>{{ $page->data['author'] }}</span>
<p>{{ $page->data['intro'] }}</p>

The above method for adding extra fields was the easy one without no hassle on your part, but if for some reason you actually need additional table columns for pages, you can create a migration to add those fields and then extend the Varbox\Models\Page model with your own model to make those fields fillable

Manage Page Uploads

Besides some basic extra fields, you might need file uploads for your pages component.

If the below code doesn't seem familiar, you might want to take a look at the Upload Files documentation section.

To add file uploads for your pages, you can just modify the blade view file with your fields (make them part of the data column). The blade file you should modify is located at: resources/views/vendor/varbox/admin/pages/_form.blade.php

<div class="col-md-12">
    {!! uploader()->field('data[image]')->label('Image')->model($item)->manager() !!}
<div class="col-md-12">
    {!! uploader()->field('data[video]')->label('Video')->model($item)->manager() !!}

You can then reference those fields in your resources/views/pages/show.blade.php by using the uploaded() helper method.

<img src="{{ uploaded($page->data['image'])->url() }}" />

<video controls>
    <source src="{{ uploaded($page->data['video'])->url() }}" type="video/mp4">

You can also cusomize the upload configuration from inside the config/varbox/pages config file, specifically from the upload section.

Render Location Blocks

As you've probably noticed, the admin crud for pages also supports assigning blocks in different locations for a page.

To learn more about blocks, please see the Content Blocks documentation section.

Assuming you've already created some blocks and assigned them in different locations on your page from the admin, you can render all the blocks assigned to a location by leveraging the render() method from the Varbox\Helpers\BlockHelper class.

{!! block()->render($page, 'your_location') !!}

By applying this line of code you'll be iterating through your assigned blocks from a given location and display their html.


The pages configuration file is located at config/varbox/pages.php.

For more information on how you can customize the content management components, please read the comments from their configuration files.

Overwrite Bindings

In your projects, you may stumble upon the need to modify the behavior of these classes, in order to fit your needs. Varbox makes this possible via the config/varbox/bindings.php configuration file. In that file, you'll find every customizable class the platform uses.

For more information on how the class binding works, please refer to the Custom Bindings documentation section.

The page classes available for binding overwrites are:


Found in config/varbox/bindings.php at models.page_model key.
This class represents the page model.


Found in config/varbox/bindings.php at controllers.pages_controller key.
This class is used for interactions with the "Admin -> Manage Content -> Pages" section.


Found in config/varbox/bindings.php at controllers.pages_tree_controller key.
Used for interactions with the pages tree from the "Admin -> Manage Content -> Pages" section.


Found in config/varbox/bindings.php at form_requests.page_form_request key.
This class is used for validating any page when creating or updating.


Found in config/varbox/bindings.php at filters.page_filter key.
This class is used for applying the filtering logic.


Found in config/varbox/bindings.php at sorts.page_sort key.
This class is used for applying the sorting logic.