As I'm formulating the exact focus of the book I've been finding myself wondering how much introductory material I should include. I think you're right about le

As I'm formulating the exact focus of the book I've been finding myself wondering how much introductory material I should include. I think you're right about leaving as much out as possible. When there is prerequisite knowledge for a particular topic, I can just point them to the documentation and avoid cluttering the book with that stuff. Regarding the schedule, since I've gotten I few comments on this I'm starting to think it might have a little weight to it. I'm pretty determined to get it done by that launch date, but my primary concern is writing a really good book. If I must delay launch, I'd rather do that than rush it. I really like the idea of explaining the "Why?" Do you mean explaining why certain practices are preferable, or why the creators of plugins and Flask itself did certain things? Also, your notes are all amazing and I'll be referring to them as I outline the book!