One of the problems I grappled with early on with was how do you come up with a table of contents for a book? It’s a complicated process, and it’s really important. If the book doesn’t flow, then people are left confused about what goes where, and the book is a lot less useful. Additionally, when you sit down to actually write, then you need to know what is covered where so that you can refer the reader to the right place to find out more about a specific topic — even if you haven’t covered that topic yet.
So how did I come up with the first cut of the table of contents for the ImageMagick book? Well, I started by looking at all of the command line options to the various ImageMagick commands. I wrote this down on a stack of old business cards, and then distributed those cards in logical sounding piles on the floor. Those piles pretty much became the chapters that I originally submitted.
That’s the card mound. Anyway, once that was done, Matt (the editor) and I sat down and worked on the table of contents description until it flowed nicely, covered everything we could think of, and had approximate page counts. It turns out in hindsight that the table of contents wasn’t completely correct, but that’s ok because I’ve been tweaking it as I go along, and it was more of a help than a hindrance in that it tells me stuff like which chapter to refer the reader to for certain kinds of information, and that sort of thing.
So what’s the point I’m trying to make here? When you’re writing something big, it’s important to have a feel for where you’re going in the document, the point you’re trying to make, and how you’re going to get there.
Update: Fixed my spelling in the title line, as per the helpful comments from Peter.