Markdown: Difference between revisions

From miki
Jump to navigation Jump to search
Line 12: Line 12:
* [http://ericholscher.com/blog/2016/mar/15/dont-use-markdown-for-technical-docs/ Why You Shouldn’t Use “Markdown” for Documentation]
* [http://ericholscher.com/blog/2016/mar/15/dont-use-markdown-for-technical-docs/ Why You Shouldn’t Use “Markdown” for Documentation]
:This author advocates instead AsciiDoc (using [https://asciidoctor.org/ Asciidoctor]), or reStructuredText (using [http://www.sphinx-doc.org/en/stable/usage/quickstart.html Sphinx]).
:This author advocates instead AsciiDoc (using [https://asciidoctor.org/ Asciidoctor]), or reStructuredText (using [http://www.sphinx-doc.org/en/stable/usage/quickstart.html Sphinx]).

== Reference==
=== Flavors ===
There are at least 3 main Markdown flavors:
* Original flavor from John Gruber.
* GitHub flavor (with eg. syntax highlighting extension).
* Pandoc flavor.


== Tips ==
== Tips ==
=== Preview standard MarkDown ===
Use {{deb|markdown}} package.
<source lang="c">
sudo apt install markdown
</source>

Then, for instance, using {{deb|entr}}:

<source lang="c">
echo README.md | entr sh -c 'markdown README.md > README.html'
</source>
This will generate a new {{file|README.html}} every time {{file|README.md}} is modified.

=== Preview Markdown before pushing to GitHub ===
=== Preview Markdown before pushing to GitHub ===
Use the wonderful tool [https://github.com/joeyespo/grip GRIP &mdash; GitHub README Instant Preview].
Use the wonderful tool [https://github.com/joeyespo/grip GRIP &mdash; GitHub README Instant Preview].

Revision as of 07:09, 16 October 2018

Links

References
Tools
Review
This author advocates instead AsciiDoc (using Asciidoctor), or reStructuredText (using Sphinx).

Reference

Flavors

There are at least 3 main Markdown flavors:

  • Original flavor from John Gruber.
  • GitHub flavor (with eg. syntax highlighting extension).
  • Pandoc flavor.

Tips

Preview standard MarkDown

Use markdown package.

sudo apt install markdown

Then, for instance, using entr:

echo README.md | entr sh -c 'markdown README.md > README.html'

This will generate a new README.html every time README.md is modified.

Preview Markdown before pushing to GitHub

Use the wonderful tool GRIP — GitHub README Instant Preview.

sudo apt install grip
cd /my/repo
grip                      # Now, open up browser to http://localhost:6419/

Comments in Markdown

We abuse link tags [1]:

[//]: # (This may be the most platform independent comment)

Align images

To center image on GitHub [2]:

<p align="center">
  <img width="460" height="300" src="http://www.fillmurray.com/460/300">
</p>

To left/right align:

<img align="left" width="100" height="100" src="http://www.fillmurray.com/100/100">
<img align="right" width="100" height="100" src="http://www.fillmurray.com/100/100">