Practically, even coordinating 3–4 people without distributed version control becomes a nightmare, with people rereading sections all over until they get tired of it an no longer notice the errors anymore. Git + Markdown is probably the cleanest way of doing this currently, and doing anything else results in multiple rounds of revisions and proofreading is probably a false economy as it will take up much more time for everyone compared to learning some tools, or result in an inferior outcome. Personally, I believe the primary reason for investing in learning some tooling is avoiding all kinds of transcription/conversion errors that result from a convoluted process with people using multiple formats. For FOSS or similar, I am still a hardliner like but in a commercial setting whatever the parties agree on should be OK - it’s their funeral.Įg if someone wants to edit documentation in MS Word, transcribe it to parchment using a quill, send it by carrier pigeon, and they are willing to pay for the overhead of dealing with this on the other end, then is should be fine. Markdown follows a simple easy-to-read and easy-to-write plain text formatting syntax. It is supported by major sites like GitHub, Bitbucket, GitLab, Stack Exchange, and Reddit.
When exporting as HTML, PDF, epub, docx, those rendered diagrams will also be included, but diagrams features are not supported when exporting markdown into other file formats in current version. Markdown is a widely used markup language, which is now not only used for creating documentation or notes but also for creating static websites (using Hugo or Jekyll).
Is that what you mean depends on the context. Flowchart Curve Gantt Padding Typora supports some Markdown extensions for diagrams, once they are enabled from preference panel.
0 kommentar(er)
