A second thought... cookbook

I've been going back and forth lately on how I want to set up my upcoming cookbook. I have decided that it will begin as an e-book as CD's cost significantly less than the paper, ink, and binding costs of a traditional book, as well as the cost to ship a traditional book. CD mailers are much cheaper and there's always the possibility to have the file emailed or downloaded. Part of my thought process is that an e-book also eliminates the cost-per-square-inch that would traditionally dictate what you do and don't want to include in the book. So I may opt to do a quick nutritional summary at the bottom of the recipe as well as a full nutritional analysis chart. (I have a program that spits it all out for me as long as I accurately input the nutritional information of the ingredients.)

As far as a plan of attack is concerned, I think the best way to do this is to get it typed up in some kind of word processing or notepad type of program so that it can be copied and pasted into the analysis program when I get home. This way I can work on any computer and use my flash drive for storage, or use the pda I have if Bryan's workout program won't sync and he doesn't want to use it anymore. (Or if I can find the really old pda)

Guess that's it for now. Just thinking how many recipes I should include and how to organize... though the organization should go by type of dish. Breakfast, breads, snacks, beef entree, poultry entree, pork entree, seafood entree, sides - veggies, sides - starches, cakes, cookies, pies, other desserts. If you think I'm missing something, feel free to post it.