Documentation is forthcoming. I didn't expect people to find out about this yet :) If you follow the project on Github, I'll release updates in the near future.
As the author of Paraglide and Paragon, I thought I'd post here. I knew SeoxyS was writing a blog post that may have included Paraglide, but I didn't know when he would publish it. I'm glad that he did, but had I known when, I may have whipped up a simple homepage, did a little bit more polishing, and created some basic documentation. I wasn't quite ready yet to release this to the wild for mass consumption. It's in the cards, but I just didn't expect to push it publicly for a little while longer.
Thanks to everyone who followed the github project, and whoever had nice comments to say. For anybody that has criticism of the projects, I'm happy to address them in a separate thread when I officially release the project publicly. I'll make a post here when I'm ready and have proper documentation. Please expect more updates in the very near future, and thanks for the interest.
I'd really just like to know why your framework reinvents the wheel for nearly every aspect of the application stack? Looking at the code even thus far, I don't see how Paraglide or Paragon improves on any aspect already offered by the largest frameworks Zend Framework, Symfony and Lithium, which already have documentation, encourage new contributions and follow best practices within their respective paradigms.
Why not contribute to an existing framework? Your efforts will be better received and more widely appreciated.
The absolute last thing the PHP community needs is another framework.
If this were a brand new framework, then maybe it would be a waste of my time, unless I had more compelling reasons. However, I started building my framework a few years ago and have just been making incremental updates here and there. Friends and coworkers have started to use it over time, and people like it. I've been told to publicize it over the last 3-6 months, but haven't gotten around to it.
My framework is minimalist and gets the job done. I'm a big fan of minimalism and I don't like that some modern frameworks are bloated and have something like hundreds of thousands of lines of code, as opposed to just a few thousand, and that includes components outside the core, like helpers.
Paragon has more work in it than Paraglide. Paragon can support multiple different backends with the same code, just different drivers. I know this exists in other PHP ORM frameworks now, but not a few years ago (not saying mine was the first, it just wasn't as widespread). Also, Paragon integrates cleanly with Memcache so the developer doesn't have to deal with cache and uncache logic.
Sure, you could do the same thing with other frameworks, but most of the other frameworks are full of bloat and not particularly fast. I think it's better to have a few components that do one thing really well rather than a monolithic framework that tries to handle every aspect.
Documentation is key! Browsing the code on github gives me an icky feeling - no docblocks :o - but I imagine I'd feel the same about my own preferred frameworks. Looking forward to a good read :)
