Add Intial View

A hook is placed in the application url.py file mapping all URI requests
that are prefixed with /recipes to the main app. Subsquent url mapping
is defined in the recipes/main/urls.py. At this point there is only one
url mapped which points to a hello world view.
Implement Collection Base View

We can now write a class that handles requests for a particular url
which inherits from the django BaseView class. We can define what HTTP
verbs it will respond to and write a method for each. This allows for
modularity and lessens the conditional branching within a view.
Sorted URL Matching

We now use some regex to catch collection sorting ideas. The base url
does not inlcude a sort. We can then sort alphabetically, ingredient,
and category as a whole. In addition a pivot can be applied for these
sorted collections to produce subsets of the sorted collections.

Each url points to the same view but paramertization occurs so wan sort
accordingly.
Indvidual Recipe Url Match

If an integer is used as a parameter on the collection we are asking for
a particular recipe with an id.
initial model
checkin, can't figure out why db won't build, starting from master...
Add app to project

This deals with dependency junk.
Add Some test data

Using yaml(please feel free to change to other formats) to seed the
database.
working model relationships
removed unneeded import
__str__
make fixtures match schema
ZOMG NOT WHITESPACE MY NAME IS YAML
Simple Template Example

This is an example of how templates can extend a base class. The
application can resue *alot* of the same html. Lets just change what we
need to.
Application serves from root url
Moved to root url
Simple iterative view
Add Missing Fields and Correct Assocations
Refactor UI

Added some UI elements as well as refactored how sorting occurs in view.
Add URL identifiers

In urls they use names to build links. You can use the url command in
the template with the first arg the url name plus a list of args.