Announcing Bonfire - A jumpstart for your web apps

[eluser]kilishan[/eluser]
You are correct. That is exactly why I am building Bonfire. It's something that I will be using on all of my future projects, also.

There are routes built in which automatically recognize controllers within modules named after the contexts (content, stats, developer, etc.).

So, to create a page in the Content area of the admin pages, you would create a controller file named content.php. A barebones controller would look something like:

Code:

class Content extends Admin_Controller {

    public function __construct()
    {
        parent::__construct();

        Template::set('toolbar_title', 'Manage Articles');
    }


    public function index()
    {
        Template::render();
    }
}

This would automatically create a new submenu item in the Content context called Articles (assuming your module was named articles). It would look for the view file under:

Code:

modules/articles/views/content/index.php

To create the public-facing file, you would do something very similar, but the controller would be called articles.php and would simply be:

You are correct. That is exactly why I am building Bonfire. It's something that I will be using on all of my future projects, also.

There are routes built in which automatically recognize controllers within modules named after the contexts (content, stats, developer, etc.).

So, to create a page in the Content area of the admin pages, you would create a controller file named content.php. A barebones controller would look something like:

Code:

class Articles extends Front_Controller {

    public function index()
    {
        Template::render();
    }
}

The view would be found at modules/articles/views/index.php. The page could be found at http://mysite.com/articles.

Hope that helps you get started!