I've always thought a bit more explanation up-front about the philosophy, the way high level components/concepts interact, and the use cases would really help w

I've always thought a bit more explanation up-front about the philosophy, the way high level components/concepts interact, and the use cases would really help with backbone. The API is decently documented, but the context is not so well documented, and sometimes that is more important than the functions themselves (I can read code, but I don't want puzzle out which things that are technically allowed are bad/good practice within the lib's architecture). edit/note: its been about 6-8 months since I was looking at backbone hard, so this may have improved.