Coaster CMS is built upon Laravel 5 and utilises the blade templating engine, because of this building templates in Coaster is slightly different to what you'd expect with vanilla PHP. Instead of using the conventional PHP opening tags, blade uses {!! code goes
As of Coaster CMS v5.4, All blocks can have multiple views in the themes/[theme_name]/blocks/[block_type] folder - this adds consistency to the block behaviour and also greatly enhances the flexibility of displaying certain block types such as string blocks. In addition, all block libraries "display" function will return strings and an additional PageBuilder function "blockData" will retrieve the data before it gets put through the block's display function should you need it.
{{ Pagebuilder::block('block_name', $options) }}
Method options ($options):
'page_id' => 6 (can override the page the block data is loaded from [will always be current page unless otherwise specified])
Browse the block types in the
Custom block types can be added fairly easily.
Coaster will look for custom Block classes in the projects app/Blocks/ folder. These should extend the base block class.
Based on Laravel 5
Additional features always being planned/researched
"git" involved
Announcing (belatedly) Coaster CMS version 5.5...
So, somewhat belatedly we have launched Coaster CMS version 5.5, which is now based on Laravel v5.5 (LTS) and mostly includes a major "under the hood" update that will make Coaster more stable and als...
Coaster CMS v5.4 is here
So, Coaster CMS v5.4 has arrived and I'm just going to give you an overview of the new features. We think this update will really help people grasp the concepts around Coaster and give you ideas o...
Where is Data Stored in Coaster CMS
We've had a couple of discussions recently with people trying to understand the data structure of Coaster and more specifically, where data is stored in Coaster CMS and I thought I'd summarise some of...