Paul-Elliot Anglès d'Auriac

> I think that allowing this only in odoc pages makes it even worse I don't agree. Most projects already have files written using the markdown format: often a README...

Your quotation is removing part of my sentence! > **If we stick to strict GFM,** this PR is simply adding support to generate docs for files which were already there....

I see a lot of docs written in markdown [here](https://github.com/janestreet/bonsai/tree/master/docs) for instance, which would benefit from being rendered by odoc in ocaml.org. I also think that having people actually writing...

> Where is the nice tutorial on ocaml.org on writing doc strings and package documentation with .mld pages ? I think it is there: https://ocaml.org/docs/generating-documentation. I agree it is a...

Thanks a lot for the PR, and sorry for the very long delay! It looks good to me, but I still have some suggestions regarding the structure. I think the...

I accidentally pushed my PR in this branch. I have reverted this, I prefer that you accept (or not) my suggested modifications on the PR on your fork.

> Well, if nothing is yet using the Quoter module, then it would still be possible to integrate its contents into Expansion_helpers as a flat hierarchy by renaming them to...

Thanks! It's also possible with the current syntax for inline attributes using `[]{pause}`. However, I think this harms the readability, so the workaround might work in some context, but in...

Good idea, I did no think of using a symbol for my specific use-case. About standalone attributes, if I understand correctly your suggestion is to have "empty nodes", represented by...

About the use-case: I'd like to use a markup language for a [presentation framework](https://slipshow.readthedocs.io/en/latest/) where there are a lot of `` or ` and I wanted to have a lighter...