Personally I am ok either way, however the question I have is consistency and how different artifacts written via html will be different (look-and-feel) from the once created using mark up and then transformed.
Oleg > On Jun 7, 2016, at 2:28 PM, Bryan Rosander <bryanrosan...@gmail.com> wrote: > > Hey all, > > When writing documentation (e.g. the additionalDetails.html for a > processor) it would be nice to have the option to use Markdown instead of > html. > > I think Markdown is easier to read and write than raw HTML and for simple > cases does the job pretty well. It also has the advantage of being able to > be translated into other document types easily and it would be rendered by > default in Github when the file is clicked. > > There is an MIT-licensed Markdown maven plugin ( > https://github.com/walokra/markdown-page-generator-plugin) that seems like > it might work for translating additionalDetails.md (and others) into an > equivalent html page. > > Thanks, > Bryan Rosander
