laravel4cookbook

File-Based CMS 349
99 }
100 }
.
This file should be saved as app/controllers/IndexController.php.
In the IndexController class, we’ve injected the same two dependencies: $filesystem and $engine.
We need these to fetch and extract the template data.
We begin by fetching all the files in the app/views/pages directory. We iterate through them filtering
out all the returned items which have a type of file. From these, we fetch the metadata and check
if the route defined matches that which is being requested.
If there is a match, we extract the template data and save it to a new file, resembling app/views/-
pages/extracted/[original name]. We then fetch the layout defined in the metadata, performing a
similar transformation. We do this because we still want to run the templates through Blade (so that
@extends, @include, @section etc.) all still work as expected.
We filter the page metadata and the layout metadata, to omit any items which do not have values,
and we pass the merged array to the view. Blade takes over and we have a rendered view!
Extending The CMS
We’ve implemented the simplest subset of October functionality. There’s a lot more going on that I
would love to implement, but we’ve run out of time to do so. If you’ve found this project interesting,
perhaps you would like to take a swing at implementing partials (they’re not much work if you
prevent them from having metadata). Or perhaps you’re into JavaScript and want to try your hand
at emulating some of the Ajax framework magic that October’s got going on…
.
You can learn more about OctoberCMS’s features at: http://octobercms.com/docs/cms/themes.