DEV Community

loading...

Discussion on: These lifehacks will change the way you write Markdown!

Collapse
jmfayard profile image
Jean-Michel Fayard πŸ‡«πŸ‡·πŸ‡©πŸ‡ͺπŸ‡¬πŸ‡§πŸ‡ͺπŸ‡ΈπŸ‡¨πŸ‡΄

My best markdown lifehack is to ditch it in favor of asciidoc as soon as you are doing something non trivial.

Simple things should be easy, complex things should be possible said a wise man. Markdown got only the first part right. Asciidoc is as easy as markdown for the simple things but won't let you down if you do something more complex

asciidoctor.org/docs/user-manual/#...

Collapse
ppetermann profile image
ppetermann

If I really need more complex I might just use good ol' latex

Collapse
jmfayard profile image
Thread Thread
ppetermann profile image
ppetermann

Which really is the only time where I need something more complex than markdown.

Thread Thread
jmfayard profile image
Jean-Michel Fayard πŸ‡«πŸ‡·πŸ‡©πŸ‡ͺπŸ‡¬πŸ‡§πŸ‡ͺπŸ‡ΈπŸ‡¨πŸ‡΄

That's what I thought also, but in fact markdown is never enough if you look at it closely :

  • on GitHub I'm using "markdown plus" some GitHub extensions
  • on dev.to, I'm using "markdown plus" some handy native liquid tags
  • with a static site generator, I'm using "markdown plus" a static front matter thingy

The question then is whether to use multiple incompatible "markdown plus extension" or a standardized better format like asciidoc.