pinto_layout
2 sites
Security covered
Automates creation of Layouts, for Layout Builder, etc, discovered and mapped automatically.
Minimal object
Here, we'll set up an object to be a Layout in as little code as possible.
If your object doesn't conform exactly to this format, there are various other way to transform objects into layouts, whether you own the object code or not.
Setup and configure Pinto objects as usual.
use Drupal\pinto\Object\DrupalObjectTrait;
use Drupal\pinto_layout\Attribute\Region;
use Drupal\pinto_layout\PintoLayout\Data\RegionAttributes;
use Pinto\Slots\Build;
final class Obj {
use DrupalInvokableSlotsTrait;
public function __construct(
#[Region]
public readonly mixed $region1,
#[Region]
public readonly mixed $region2,
public RegionAttributes $regionAttributes,
) {
}
}
Associated Twig template:
<div {{ regionAttributes.containerAttributes() }}>
<div {{ regionAttributes.regionAttributes('region1') }}>
{{ region1 }}
</div>
<div {{ regionAttributes.regionAttributes('region2') }}>
{{ region2 }}
</div>
</div>
Note, this setup requires the following to be added to site settings.php:
$settings['twig_sandbox_allowed_classes'] = [
\Drupal\Core\Template\Attribute::class,
\Drupal\pinto_layout\PintoLayout\Data\RegionAttributes::class,
];
Clear container, and this object will be made available as a Layout, for use with Layout Builder.
There are other examples on how to customize these Layout objects in the example test code directory, including:
- Customizing Layout ID
- Customizing Layout Label
- Pinto objects implementing an interface, as an alternative to
#[Region]attribute, so you can make constructors private or custom. - If you do not have control over Pinto object code, you can nominate a object as a layout, by providing regions and a factory method to wire things together.