Idea: Reorganize the book in more meaningful section oriented to use case

[cderv]

Example:

• "Don't repeat yourself!"
• "Customize looks and feel of your publication"
• "Configure code execution behavioir"
• ...

This would be more useful than technical organization (Word, PDF, Knitr, Tables, ...)

Also, maybe there should be a companion blog or website to the cookbook with a cross organization (with tags and categories) that would allow more broader flexibility.
The R Markdown Cookbook could be a selection of those recipes organize in a book ready to print.