What are the benefits of browser-based documentation over book-like (PDF) documentation for API/SDK docs? -


I am often encouraged to use company documentation standards while documenting my API / SDK and programmer guides. I'm looking for rational / examples that I can take in management to support my experience that developers like the document which does not look like a book.

Regarding, what is it that you do not like to see in this kind of document? ("Everything is needed, but now no more" is something more specific.)

Based on documents found, it is very easy to navigate through the use of PDF viewers that I can make a lot better. Plus I can bookmark the pages and see the document in any browser. In my experience, web based documentation is much easier and faster than PDF.

Most developers I've worked with feel more comfortable with the web on the basis of PDFs.


Comments

Popular posts from this blog

python - Overriding the save method in Django ModelForm -

html - CSS autoheight, but fit content to height of div -

qt - How to prevent QAudioInput from automatically boosting the master volume to 100%? -