"Why do you think that hundreds of pages would perform worse than hundreds of posts?"
Because we found in recent version of WP, it added ELEVEN rewrite rules for each page. Eleven.
And they are meant to be static, as in not really related to other pages, like a book would be.
"If I have to create a page for every post with a redirect to that post in order to get it in the (list_pages) menu, it defeats the purpose of using posts at all?"
I don't even know why you would do that in the first place?
Pages :
- about
- contact
- FAQ
Content Categories:
- chapter 1
- chapter 2
- chapter 3
post tile:
- subchapter headings
extra plugins:
- reverse chronology
- paginated entries
...etc
Setup:
- set welcome page as front page, not posts
- change permalink to category/post-title
Also, in WP by default, the pages don't show up in the internal search. Pages don't have an RSS feed. The navigation from "Next" to "previous" only applies to posts not pages. Using posts works *with* WP, not against it. An archive page can be generated dynamically and you won't have to manually make a table of contents.
If you note this blog post:
http://www.lostaddress.org/2008/01/07/writing-a-book-use-wordpress
He does talk about using pages, but in the comments many people (including the famous Lorelle) suggest posts would be better.
Oh, okay now I see you were wanting them in pages to list them in the menu. You can list the blog posts as well, like I said up there in the archives. You can list categories in menus the exact same way you do with pages.
If you *really* wanted to do it in MU, the main blog is the landing site for the book, info etc.. and each blog off that would be a chapter, with posts being sub-chapter sections. you could probably use pages there as chapter overviews.
Navigation to each chapter would be easy here too, as you'd just list the blogs. I'd use a subfolder/subdir install.
I think you're overthinking the idea a little too much as well, maybe being too close to it. :)