Implement a function that generate the .md documentation file from the parsed structure.

[gaspardcereza]

Context

I implemented a function parse_doc that parses the documentation of a function and returns a structure that contains the following information:

|.summary (string)
|
|.syntax (array of strings of size 1*nSyntaxes)
|
|.description (string)
|
|.inputs (struct)
|           \______ .names (array of strings of size 1*nInputs)
|            \______ .description (array of strings of size 1*nInputs)
|
|.outputs (struct)
|           \______ .names (array of strings of size 1*nInputs)
|            \______ .description (array of strings of size 1*nInputs)
|
|.notes (string)

We now want to generate a .md file destined to display the documentation on our website.

[jcohenadad]

related to #20

[rtopfer]

We now want to generate a .md file destined to display the documentation on our website.

I may have misunderstood, but if you want to integrate the parsed+reformatted doc into the current workflow, then it wouldn't be a question of "generating" a .(new) md file so much as just swapping-out part of the original doc string with your new reformatted part, as I suggested here

e.g. just add an option (e.g. isParsingHeader=[true|false]) to the Documentor.draftdoccontent method to call your function within this for loop (i.e. for every .md file in the list)