Move Hacking How To Guides into Documentation
I'm working to update and revise a few documents from existing
resources into our documentation (i.e. docs/).
The goal here is to provide an introduction to hacking on
MediaGoblin that outlines both "how to get all of the necessary
components working," in order to begin hacking on GMG.
As part of this, I want to include sections that answer the
questions, "what/where are the (popular) components that one might
be interested in working on," (i.e. templates, db schema,
configuration files, urlmapping.) and "why are things the way they
are," (drawing from existing design documents.)