On January 23, 2015 5:05:55 AM EST, "Paul A. Bristow"
-----Original Message----- From: Boost [mailto:boost-bounces@lists.boost.org] On Behalf Of Damian Vicino
Hi, I’m preparing a library to be proposed and I’m adapting the documentation I had to be more Boost-like.
I’m wondering if there is a preferred style or document structure to use.
There are no fixed rules, but I think that a tutorial-ish "Why use this library? What it does for you." is the best way to start.
Those questions aren't address by a tutorial add I understand the idea. They are addressed by an Introduction or Motivation section. A tutorial walks through how to use the library, step by step with discussion.
Providing links to external documents, other Boost libraries and to internal details is important to the user.
"Internal details?" I'd want to know about the API, the exceptions emitted, etc., and I'd want to know about performance characteristics, for example, but not internal details.
The best tool, again in my opinion, is the Quickbook, Doxygen and Autoindex toolchain.
Right, at least when the author doesn't have contrary ideas about structure and layout. ___ Rob (Sent from my portable computation engine)