Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
OUTPUT_FILE: agility.markdown The Agility Tutorial - A simple story manager {: .document-title} Contents {: .contents-heading} - contents {:toc} # Introduction In this tutorial we'll be creating a simple "Agile Development" application -- _Agility_. The application tracks projects which consist of a number of user stories. Stories have a status (e.g. accepted, under development...) as well as a number of associated tasks. Tasks can be assigned to users, and each user can see a heads-up of all the tasks they've been assigned to on their home page. This is a bit of an in-at-the-deep-end tutorial -- we build the app the way you would assuming you had already got the hang of the way Hobo works. In the later stages new concepts start coming thick and fast. The goal here is to show you what's possible, and give you a flavour of Hobo-style application development, rather than to provide detailed background on how everything works. Don't worry about it, it's fun! If you'd rather take things a bit slower, you might prefer the [POD tutorial](http://hobocentral.net/pod-tutorial). # Getting Started ## Introduction to Hobo Hobo is a bunch of extensions to Ruby on Rails that are designed to make developing any kind of web application a good deal faster and more fun. This tutorial is designed to show off Hobo's ability to get quite sophisticated applications up and running extremely quickly. While Hobo is very well suited to this kind of throw-it-together-in-an-afternoon application, it is equally useful for longer term projects, where the end result needs to be very meticulously crafted to the needs of its users. Hopefully the tutorial will give you an idea of how to take your Hobo/Rails application much further. For more info on Hobo please see [hobocentral.net](http://hobocentral.net) ## This is a gitorial This is a 'gitorial', a tutorial made with [git](http://git-scm.org). However, we highly recommend that you treat this as you would any other tutorial. The more that you put into the tutorial, the more you will get out of it. If you wish to use 'git' to follow along, see the [sidebar](gitorial). Using git will allow you to skip ahead in the tutorial and to use git to double check your code for errors. We do not recommend learning git and Hobo simultaneously, though. [sidebar: using git with the tutorial](gitorial) ### How code is displayed in this tutorial Code changes in this gitorial are displayed in a modified *patch* format. When you see one of these, they indicate how you should modify the code in your version of this project. Lines that have a "+" in the left hand column and are coloured green indicate lines that you should add to your project. Lines to remove have a "-" in the left hand column and are coloured red. On the other hand, if you see something that looks like code but has a "$" in the left hand column -- those aren't patches! Those are commands that you can type into your command terminal.
- Loading branch information