> Create a PDF tutorial (with Hi res and stuff) > Print it to become an offical book > Put together tutorials, templates, images and whatever helps to produce > professional material > Sell it together with non-selled stable cross-plataform versions of > Scribus burned in a CD
The points people have been making here are: 1. What version should that manual cover? Is it really good use of work to spend months writing a manual for 1.3.3.10, the release it when Scribus 1.3.5 has been released? Scribus development goes fast, things change from one week to another. 2. If a manual is to be done, the single most important thing to make sure is that someone is willing to write it. Without someone who wants to write it it will never be written. No matter how many "good ideas" people come up with. /Peter
