You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is rather an important change, and needs to be discussed but I see the following advantages:
Asciidoc is well defined, and does not have the dozen of dialects that has markdown, which mean the javascript renderer will render the same things as a "server side renderer" (or it's a bug, not a "well markdown does not define really that" or "yeah but this javascript library implement this or that extensions" )
Asciidoc supports much more things than "pure" markdown (table anyone ?)
Asciidoc has a nice toolset for producing not only HTML, but also pdf, ebooks etc. which would make tatowiki suitable for the collaborative redaction of ebooks
it would be not "impossible" to convert existing "markdown" articles into asciidoc (as I guess most of the Taoteba's instance of tatowiki does not use complex structures nor specific extensions ?
The text was updated successfully, but these errors were encountered:
This is rather an important change, and needs to be discussed but I see the following advantages:
The text was updated successfully, but these errors were encountered: