Description
The documentation strategy (instead of a large book, the Symfony2 documentation is split into small chapters about specific topics);
Fabien Potencier
http://symfony.com/blog/symfony2-documentation
i think, it would be very important to also create and provide the symfony2 docs in "book" form -> pdf / epub.
why?
- no, we don't have a internet connection everywhere
- ebook reader doesn't handle rst
- for people who want to print it out
- ...
of course the format of the symfony docs opens all doors to do it myself (http://symfony.com/doc/2.0/contributing/documentation/format.html),
i only need Sphinx and then i can create pdfs. wait, i have to install rst2pdf. easy
ImportError: No module named setuptools
http://www.happylife.sg/index.php/2010/04/25/importerror-no-module-named-setuptools/
and so on...
what i want to say is, that its not a 5 minute act to create a pdf and if i just want to learn a framework it doesn't mean i want to learn how to convert rst in pdf (or have the time to).
it would be a great thing, to add the conversion to pdf/epub to the docment website build/deploy process, so the problem is solved one time and the users of symfony can focus on symfony instead of building pdf files.
before anyone answer with "we don't need that", "it is ok how it is",... don't forget we are talking about digital/virtual stuff, so if i would ask to print a book in paperback insted of hardcover this would be a decision where only one way would be possible course you can if you look at the costs but in the virtual world we just can deploy both with nearly no overhead.
we don't need to choose between this or that way, we can take both ways at the same time.
to provide a one (all the docs) or three (book, cookbook, components) file(s) doc would really help to use it mobile.
please help the developers to keep focus on developing with php and symfony not sphinx and other stuff.