Make suggestions for repo organization

I'd love to see this repo become more of an e-book over time — if anyone wants to make suggestions for how to best organize everything, suggest away!

Also, I'm curious if we may be able to organize the data in such a way that it becomes easy to add to our coming API. Any thoughts? Should we keep REST in mind when organizing things?

The issue names no files, tests, or entry points. Review the repository's current organization and the e-book content, then consider how the data could support a future API while keeping REST in mind. Done is not defined because the request asks for suggestions rather than a scoped change.

Written by the indexing model from the issue text.