Container sections simply contain other sections. The standard section container in Cuisine Sections is a grouped container. This does nothing more than contain multiple sections. However; there are seperate plugins that allow you to turn your containers into tab-interfaces, sliders and other fun stuff. The defining factor in this is the container ‘view’ parameter.
It uses the same class system as a regular Section, with the difference that the base class isn’t an extension of BaseSectionClass, but an extension of the \CuisineSections\SectionTypes\Container class.
Registering a container type happens through a filter. We’ll look at an example and then dive into it further:
add_filter( 'chef_sections_containers', function( $data ){
$data[ 'slider' ] = [
'label' => 'Section slider',
'view' => 'slider',
'class' => '\My-Plugin\Containers\SectionSlider'
];
return $data;
});
in the example above we’re registering a slider section container. It’s label (for picking it out in the UI) is “Section Slider” and the class it refers to is \My-Plugin\Containers\SectionSlider.
This class is an extension of the \CuisineSections\SectionTypes\Container class. This class works with the same exact attributes api as the regular content section, but just adds the sections attribute, which is an instance of the InContainerCollection; a collection of all sections in this current container. It also makes sure that the columns collection of each container is absolutely empty.
Base class: \CuisineSections\SectionTypes\Container
Template class: \CuisineSections\Templates\ContainerTemplate
Collection class: \CuisineSections\Collections\InContainerCollection
Admin logic: \CuisineSections\Admin\Handlers\ContainerHandler
Admin ui: \CuisineSections\Admin\Ui\Sections\ContainerSectionUI