Extensible documentation

[Thomas Hoffmann]

As I read about extensions of Octave's m-file basis I remembered
a problem that I often have when trying to do something new with
Octave: Although there is documentation of Octave's core functions, 
the great amount of contributed m-files is (naturally) not included
and I have to dig into the m-file directories, armed with grep and
some wild guesses how the function I look for could be named.

Is there any interest to reason about a possible framework
of documentation for contributed code, e.g. to be able to extend stepwise
an .info file for "Octave contributions"? 

Thomas.