laravel4cookbook

File-Based CMS 326
.
This was extracted from app/routes.php.
These are quite a few files, so let’s go over them individually:
1. The first file is the main admin layout template. Every page in the admin area should be
rendered within this layout template. As you can see, we’ve linked the jQuery and Bootstrap
assets to provide some styling and interactive functionality to the admin area.
2. The second file is the main admin navigation template. This will also be present on every page
in the admin area, though it’s better to include it in the main layout template than to clutter
the main layout template with secondary markup.
3. The third file is a sub-navigation template, only present in the pages concerning layouts.
4. The fourth file is the layout index (or listing) page. It includes the sub-navigation and renders
a table row for each layout file it finds. If none can be found, it will present a cheeky message
for the user to add one.
5. Finally we add the index route to the routes.php file. At this point, the page should be visible
via the browser. As there aren’t any layout files yet, you should see the cheeky message
instead.
Let’s move onto the layout add page:
1 public function addAction()
2 {
3 if (Input::has("save"))
4 {
5 $validator = Validator::make(Input::all(), [
6 "name" => "required|add",
7 "code" => "required"
8 ]);
9
10 if ($validator->fails())
11 {
12 return Redirect::route("admin/layout/add")
13 ->withInput()
14 ->withErrors($validator);
15 }
16
17 $meta = "
18 title = " . Input::get("title") . "
19 description = " . Input::get("description") . "