After being a upset at the progress with Pico, myself and a developer from Germany(Frank) have developed a fork project.

The project is PhileCMS. It maintains the philosophy of Pico, being fast and small, but it makes a lot of improvements on the core. Most the project is now OOP based with classes and models.

Also the parser and the template engine have been pushed into services. Which means they can be overloaded and replaced with different ones. Don't like Markdown? Use a plugin for TextTile instead. Don't like Twig? Replace it with Lex!

The hooks system was completely replaced with an Evented system. The plugins have also changed. They now have a config.php file that is used instead of having to write your own file reader for each plugin.

So why use this over Pico?

Here is a small list of differences in design from Pico:

  • OOP based (Classes)
  • Events system
  • Parser Overloading
  • Template Engine Overloading
  • Performance Improvements (33% to 65% speed increase)

The main increase in speed is when there are multiple pages. Once you get to 20 pages you see a minumum of a 50% increase in load times.

I have actually converted this site to run on Phile. It is probably the first site in production to be using it. I also use the Sundown Plugin I wrote since I have PHP-Sundown installed on my server.

Anyway, check out the project. It is pretty cool and I am very happy with the work of Frank.

Github Repo