Searching for a Kohana Beginner's Tutorial for PHP [closed]

Question

The "Kohana Tutorial" pages are pants. Not so much for their content, but for the fact that they have a pretty damn unorganised wordpress blog and finding useful info isn't exactly made easy. What they need is a post/page at http://learn.kohanaphp.com that lists the most important tutorials, rather than forcing you to wade through the whole blog.

Anyway, rant over, I'd start here:

http://zacklive.com/hello-world-tutorial-for-kohana/15/

Then:

http://learn.kohanaphp.com/2008/03/26/blog-tutorial-1/

http://learn.kohanaphp.com/2008/03/28/blog-tutorial-part-2/

Other articles of interest:

http://www.ninjapenguin.co.uk/blog/2008/06/21/kohana-pagination-tutorial/

http://learn.kohanaphp.com/2008/04/25/using-auto_modeler-to-write-quicker-code/

http://www.ninjapenguin.co.uk/blog/2008/06/29/practical-kohana-hooks-example-phpids/

http://learn.kohanaphp.com/2008/04/14/5-tips-to-help-you-find-something-youre-looking-for-in-kohana/

And, of course, Google.

I had exactly the same problem! After a few searches I found the Kohaha101.pdf. This guide/tutorial really got me started!

Link:[http://pixelpeter.com/kohana/kohana101.pdf1

Good luck and enjoy Kohana!

Since this is bumped anyway:

If you're looking for Kohana 3 beginners tutorials, the ones listed at the bottom of the unoffical Wiki are pretty good.

Learning Kohana is a pain. There is some information out there but it's all over the place and Google is your best ally. The support forums are pretty good but it's very much a framework for PHP geeks. It addresses all of the fundamental flaws of PHP and provides a clean MVC design pattern but nothing more.

The advantage of such a minimal approach is that it's lean and lightning fast. When things don't work you will find the need to go through the libraries as sometimes it's easier to understand what methods/properties are available or how they work by looking through the underlying code. It would be nice for somebody to donate some money and for the team to pump it into proper documentation as it's the achilles heel of the whole project.