The Page Field Type has limited write support with the Public API as of , part of v5.4.7 releases, before this it where read-only. In all versions it is still possible to edit content with it through the admin interface (which runs through the legacy stack). 

You still need to define your available layouts and blocks in the legacy part to get them available in the admin interface. Please refer to eZ Publish legacy documentation to learn how to do so.

ezpublish:
    system:
        my_siteaccess:
            ezpage:
                layouts:
                    myLayoutIdentifier:
                        name: "My über cool layout"
                        template: "AcmeDemoBundle:page/zonelayouts:my_template.html.twig"
				enabledLayouts: [myLayoutIdentifier]

You can specify a legacy template in your layout definition.

ezpublish:
    system:
        my_siteaccess:
            ezpage:
                layouts:
                    myLegacyLayout:
                        name: My legacy layout
                        template: "design:zone/my_legacy_template.tpl"
				enabledLayouts: [myLayoutIdentifier]

However, doing so will defer block display to the legacy templates as well.

ezpublish:
    system:
        my_siteaccess:
            ezpage:
                blocks:
                    myBlockIdentifier:
                        name: "My über cool block"
                    myBlockIdentifier2:
                        name: "My über cool block 2"
				enabledBlocks: [myBlockIdentifier, myBlockIdentifier2]

Template selection rules are applied only when you render a block with the PageController (using ez_page:viewBlock from templates), see below.

ezpublish:
    system:
        my_siteaccess:
            block_view:
                # A simple unique key for your matching ruleset
                my_rule_set:
                    # The template identifier to load, following the Symfony bundle notation for templates
                    template: AcmeTestBundle:block:campaign.html.twig
                    # Hash of matchers to use, with their corresponding values to match against
                    match:
                        # Key is the matcher "identifier" (class name or service identifier)
                        # Value will be passed to the matcher's setMatchingConfig() method.
                        Type: Campaign
                another_rule:
                    template: AcmeTestBundle:block:custom_block.html.twig
                    match:
                        Type: CustomBlock

You can define your template selection rules in a different configuration file. Read the cookbook recipe to learn more about it .

Matchers for block_view follow the same behavior than matchers for regular location_view / content_view, except that their relative namespace will be eZ\Publish\Core\MVC\Symfony\View\BlockViewProvider\Configured\Matcher .

Hence you can combine matchers with AND and OR capabilities (see main matchers' documentation page).

This section focuses on how to display blocks from zone/layout templates.

Render of these templates are triggered when using ez_render_field() helper, like for any other field type.

See field rendering documentation for more information.

You can use a custom controller to display a block.

However, if you do so, you might need to get access to the PageService. You can get it via the service container with identifier ezpublish.fieldType.ezpage.pageService.

{{ render( controller( "ez_page:viewBlock", {'block': myBlock} ) ) }}

If no template selection rule is matched, the system will fallback to the legacy kernel and will use rules you might have defined in legacy. The result will be the same as when using legacy block_view_gui function.

However, additional variables (from the params argument) won't be passed to the resulted template.

valid_items and valid_contentinfo_items variables are available as of v5.2 / 2013.11.

Usage of pageService is deprecated as of v5.2 / 2013.11 and will be removed in v6.0.

This feature is available from eZ Platform 5.3.2.

<h2>Twig Template for 2 zoneslayout1 zone</h2>
<div class="zone-layout-{{ zone_layout|lower }} row">
    <div class="span8">
        <section class="content-view-block">
        {% if zones[0].blocks %}
            {# Rendering blocks with default PageController #}
            {% for block in zones[0].blocks %}
                {{ render( controller( "ez_page:viewBlock", {'block': block} ) ) }}
            {% endfor %}
            <div class="block-separator"></div>
        {% endif %}
        </section>
    </div>
    <div class="span4">
        <aside>
            <section class="content-view-block content-view-aside">
            {% if zones[1].blocks %}
                {# Still rendering with default PageController, but passing specific cache value (TTL of 100 seconds) and using ESI #}
                {% for block in zones[1].blocks %}
                    {{ render_esi( controller( "ez_page:viewBlock", {'block': block, 'cacheSettings': {'smax-age': 100}} ) ) }}
                {% endfor %}
                <div class="block-separator"></div>
            {% endif %}
            </section>
        </aside>
    </div>
</div>

<h3>Twig Template for Campaign Block type</h3>
{% set validContentInfoItems = pageService.getValidBlockItemsAsContentInfo( block ) %}
{% set validItems = pageService.getValidBlockItems( block ) %}
<!-- BLOCK: START -->
<div class="block-type-campaign">
    <div class="campaign">
        <a href="#" class="navig prev" style="opacity:0;"><span class="hide">&lt;</span></a>
        <a href="#" class="navig next"><span class="hide">&gt;</span></a>
        <ul class="indicator">
            {% for contentInfo in validContentInfoItems %}
                <li><span>{{ contentInfo.name }} (#{{ contentInfo.id }})</span></li>
            {% endfor %}
        </ul>
        <ul class="images">
        {# Rendering valid items with regular view controller, with "block_item_campaign" view type #}
        {# Also passing an "image_class" parameter which will be available in sub-template. #}
        {% for item in validItems %}
            {{ render(
                controller(
                    'ez_content:viewLocation',
                    {
                        'locationId': item.locationId,
                        'viewType': 'block_item_campaign',
                        'params': {'image_class': 'campaign'}
                    }
                )
            ) }}
        {% endfor %}
        </ul>
    </div>
</div>
<!-- BLOCK: END -->