A tiny PHP framework for tiny sites.
Femto is something I developed for myself to use for sites that were too small to require the bloat of a full cms or complexity of a framework but still needed some dynamic parts.
Femto is based on the concept of 'pages', 'templates' and 'fragments'. A page maps directly to the URL at present, for example a request to yoursite.com/contact would try to load the page in pages/contact.php. A page can be compromised of any code you want and use multiple fragments. A page can also 'use' a template, a template can consist of several fragments and common code you want to have on multiple pages. For example every page on your site is likely to need to use the header and footer fragments you have set up, a template would be a perfect use case for this. Consider the example set up below:
fragments/header.php
<!DOCTYPE html>
<html>
<head>
<title><?php echo $title; ?></title>
</head>
<body>fragments/footer.php
</body>
</html>templates/main.php
<?php $this->useFragment('header', array('title' => $title)); ?>
<?php $this->templateContent(); ?>
<?php $this->useFragment('footer'); ?>pages/index.php
<?php $this->useTemplate('main', array('title' => 'Home Page')); ?>
<h1>Hello World</h1>It's also worth noting it's possible to embed a fragment inside another fragment.
Femto also supports retrieving pre-defined configuration variables like so $this->getConfig('site', 'env') behind the scenes Femto looks for a file called site.php in the config directory of your application. It expects an associative array to be returned from that file like so:
config/site.php
<?php
return array(
'env' => 'development',
);This is a very basic example that by default Femto uses to determine how to handle 500 errors in it's 500.php page but you could use config variables for anything. You could store a list of products for example.
Femto has very basic exception based error handling, if a page is requested that does not have a corresponding file in the pages directory internally a FemtoPageNotFoundException is thrown which Femto catches and if it exists will load pages/400.php and returns a HTTP 404 status code. Femto also handles internal application errors such as when you request a fragment or configuration variable that doesn't exist, when this happens it tries to load pages/500.php if it exists and returns a HTTP 500 status code.
Femto is very early in development right now but if you have any ideas on how it could be imrproved please feel free to submit a pull requset and I will do my best to review it as soon as possible. At the moment my plan is to keep Femto as simple as possible, so for example I don't have any plans to add features like support for databases as that's not what I see Femto as being for.
I have no ETA's for these but listed below are some rough things I have planned:
Integrate Composer autoloadingDone in v0.2.0Make Femto itself Composer compatible and add it to packagistDone in v0.2.0, see seperate jamesrwhite/femto-core repoAdd some helper functions in for general tasks like string manipulation etcCan be accomplished via a composer packageAdd support for templates, ideally working in a similar way to Django/Twig.Basic implementation in v0.3.0!- Better environment support, like how Laravel allows folders in the config folder that correspond to the env
The MIT License (MIT)
Copyright (c) 2015 James White
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.