I've just started working on a Content Management Framework using Laravel 3. It is not designed to be a database-driven app (that may come later). It is designed for web-designers wanting an easy and SEO-friendly way to make a static website.
In a nutshell, the designer would only need to create a default site, and any other [optional] sites (making it a multi-site framework, like Drupal) by means of working with a folder structure.
Currently, the structure has been designed as follows (not implemented yet, it is just an idea; it is also an alteration of Laravel's standard path structure):
public[_html]
root
app // application folder
bundles
sites
sites.json // used to determine the default site, and register any others
{site-slug}
info.json
content // for page content that inherits a layout
{page-slug}
info.json
content.blade.php
layouts // site layouts: headers, footers, etc.
stores // storage folder
system // laravel folder
Here's my main issue right now: I have no idea how to extend the View class to look outside the standard views
folder without having to use the path:
prefix.
What is the best method of doing this?
Perhaps there is another templating engine that makes this task easier for me? Is there a suitable HAML engine for Laravel 3?
Note: I know there are content bundles that make use of Markdown, but that is not what I'm looking for.
Any help here would be hugely appreciated.