Your suggestions for tutorials

Yesterday’s tutorial was quite a delivery. It was sort of a longtime goal of mine to write a Kohana/jQuery tutorial so I’m glad it’s done. Anyway, the question is now; what should come next? What sort of tutorials are high in need? The very basic or the very advanced? A couple of suggestions from me:

  • Autocomplete tutorial with jQuery and Kohana
  • Tutorial covering installation of Kohana
  • Tutorial on the Auth module (I also don’t know how it works though)
  • Tutorial on events and the so-called ‘catchall’ controller (example.com/username stuff)

I will happily cover any other suggestions as long as its in high demand.

As always, I gladly accept any guest posts. The current speed of posting is something I am unlikely to keep up :)


20 Responses to “Your suggestions for tutorials”

  1. tahlon Says:

    hi!

    i would like to see a tutorial of how to use unit tests while writing a project. i am not really in touch with kohanas unit testing module but i remember some forum posts about it.

    Another great thing would be a series of tutorials aiming to create a more complex application (like cake did, from 1st to 24th december). A german magazine is doing something similar with ruby on rails at the moment, they are creating “trainspotr” (pictures of trains, geotagged etc..) with a 3 part tutorial series.

  2. n Says:

    how to use calendar_library (nothing about it in docs :( )

  3. Delapouite Says:

    @n : right now, the Calendar_library is a work in progress.
    Lots of crucial functionalities aren’t implemented yet, this explains the docs lacks of consistency.

  4. Martin Kjems Says:

    I would like to see your take on an outline for a plug-in architecture for a generic CMS built on kohana that would facilitate greater re-use and sharing of code and modules between kohana developers. …..just that ;-)

  5. Bobby Says:

    i would like to see a pagination tutorial. Please

    Thank You

  6. Errant Says:

    Personally I’d love to see the auto-complete tut mentioned - it’s a weak area of mine :)

    BTW I’m happy to write up some stuff if there is space! I’ll put some stuff together and get in touch :)

  7. Deimos Says:

    I would like to see a example using Auth with different sets of user logins. So let’s say we have a user ‘developer’ which has access to everything and a ‘editor’ which can only do only limited things.

    And then especially how the developer can switch between all available editors.

    And I also like the autocomplete tutorial ;)

  8. Fede Says:

    The AutoComplete and the Auth tutorial will be pretty nice, thanxs

  9. dlib Says:

    Thanks for all the comments. I’ve covered the unit testing library on this blog before so I won’t cover it now. One pointer, TDD comes down to defining the behaviour of your application, writing tests for that behaviour and run the test suite. Everything that fails, fix it. Run suite. Fix. Run suite etc. I hope to post on it in the future though.

    The complex application is certainly something I intend on doing despite the work. Demios: I can then also cover Auth.

    The calendar and pagination will also receive some attention although my experience with either of them is limited.

    Kjems: I might release the Modules library I use for managing modules. I’m not sure how generic it is though.

    The autocomplete tutorial I hopefully will get to very soon.

    Errant: I welcome anything :) register and I’ll give you the proper priviliges.

  10. Tristan Says:

    I’d like to see something on sessions. The AutoComplete and the Auth tutorials sound good also

  11. Errant Says:

    Registered! (I forgot :))

    I’ll write something up about pagination seeing as I’ve been using that and it’s a fairly simple start. :D

  12. dlib Says:

    Great, I’ve given you the proper rights.

  13. Siner Says:

    Auth module and hooks it will be nice.

  14. SiNNuT Says:

    I’ve always liked what Symfony did with their ‘Askeet’ tutorial series (http://www.symfony-project.org/askeet/1_0/en/)

    I do think this kind of thing is pretty demanding on the authors but it gives a very nice oversight of the framework and it’s capabilities.

  15. DavidZ Says:

    Hi!.

    I’ve been searching for some documentation about Kohana, but I could find it only online. So… I took a little of my time to copy/paste ALL (or the most) of the Online Kohana Doc pages into a PDF file…

    First, I’d like to know if it’s ok to share it… Second… I’d like to share it: Put it somewhere everyone can see it and Download it!!!…

    Of course, if there’s some Kohana tutorial or book (jeje), please… somebody tell me!

  16. DavidZ Says:

    Ahh. One more thing.. I’ve put a PDF version of Kohana Documentation on my SkyDrive site… So if someone would like to get it, here is the URL:

    http://cid-c12a38c5716b43a6.skydrive.live.com/self.aspx/Documentos/Kohana%20doc.pdf

    I hope it to be usefull… else, here is my email… ask for it… I’ll try to give a copy to you…

    sonofsundz@hotmail.com

  17. bennythemink Says:

    How about a very short post on how best to structure your kohana project?

    Most projects will have a front end section containing pages accessable to all users and a back end section, e.g. an admin section.

    It would be great to know about whats the best practice on how to separate these controllers (sub-folders in the Controllers dir) and what pitfalls to look out for.

    This topic was touched on in this thread before and I thought your suggested structure was very good dlib.

  18. Learning Kohana » Kohana’s User Guide Says:

    [...] has been so kind to make the user guide into a PDF. Thank you David. I’d also like to thank everyone for [...]

  19. neovive Says:

    I second the suggestions for the Akismet style tutorial and structuring your application. Some of the structuring concepts are covered in the Kohana 101 document, but it’s not linked to the user guide at the moment.

  20. jalex Says:

    Auth definitely!
    Also you could make a security tutorial. In this tutorial you could explain vulnerabilities that appear during development of sites with Kohana framework. Something like a check list for unexpirienced users. So they could easily check if their application is secure to common threats. Or something like that :)

Leave a Comment