3 ms·
I don't see how AsciiDoc source is any more or less readable than Markdown. AsciiDoc does everything Markdown does, but since there's a specification there are
by Symbiote 7y ago
I don't see how AsciiDoc source is any more or less readable than Markdown. AsciiDoc does everything Markdown does, but since there's a specification there are no inconsistencies.
It also has features beyond that. You don't need to use them.
Edit: here's an example from KiCAD's documentation ("Raw" to view the source, as GitHub supports AsciiDoc as well as Markdown) https://github.com/KiCad/kicad-doc/blob/master/src/getting_started_in_kicad/getting_started_in_kicad.adoc https://github.com/KiCad/kicad-doc/blob/master/src/getting_s...
- jmilloy 7y ago> You don't need to use them. You do if you are reading a source that uses them.
- dwohnitmok 7y agoThe argument that certain features are optional overlooks the fact that other people can and will use them, especially in collaborative projects. That's not a death knell. You can gate the features behind style guides, linters, or social conventions. However, those are costs in and of themselves. Additional features of a language always have a carrying cost, even behind optional flags.
- untog 7y ago> You don't need to use them. But people will, though. If you're lucky enough to be there at the start of project you could establish a list of allowed functionality but at that point you're documenting your documentation, which feels, uh, sub optimal.