It suddenly dawned upon me that Habari is in fact the long talked about CMS that was brewing since Kohana 3 was in RC. Gosh, it took me awhile to connect the dots!
Unfortunately, I am currently engaged in a project using WP as the backend & Kohana 3 as the front end. The backend is only for the site admin. 100% of the user experience is in the front-end. I am using WP's api ( I know, I know... ) The good news is I have read and understood the WP workflow pretty well. And since my application is rather social-esk, I have dug deep in most of buddyP. as well. Thankfully for me, the latest release of WP is actually significantly better than all the rest. Alot of functionality is being centralised and more core API is object based. One of the primary reasons for Kohana as the front-end of my app is for it's brilliant routing. Okay, I should get to my point! I really feel that I can make a worthy contribution to Habari and I cannot wait to come on-board. My Massive project isn't finished ( it is certainly of no help that I'm doing it alone! ) but I'll be here as soon as it does. In the meantime, if you guys need a WP internals "dictionary", I'm your man! Sorry for the long irrelevant post, just had to share it with someone. Thanks for reading! -- To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/habari-dev
