Is there a thumb rule regarding the number of chapters in a technical book? (like 1. number of pages per chapter or 2. minimum number of chapters or 3. minimum number of pages etc)
@monicacellio - I'm thinking that this could be answered by indicating that tech books tend to be organized according to topic, not cutting up chapters to create a rhythm as is often done in fiction. Am I on target here? It just seems irresponsible to answer this question until it has more detail.
@Standback @justkt - Tempted to close this question, what do y'all think?
@NeilFein - Sorry I'm late. I agree with your comments there and here. There's a lot of variety, depending on number of topics and how well they "clump", published format, house style, and consistency with other books of its type. I've written technical docs with 2 chapters and ones with 20.
@Anil - Okay. If you can get a little more specific about the project in the question text, we could probably re-open. Right now, it's kind of asking people to guess.
@Anil : Heh - I actually think _Is a tech book with only 2 chapters publishable?_ would be a **great** question. That's much clearer and more practical than asking what the accepted average is - and more interesting, too :)