Markdown: Difference between revisions

From miki
Jump to navigation Jump to search
Line 8: Line 8:
* [https://github.com/joeyespo/grip GRIP — an offline MarkDown viewer] (see tip further down also)
* [https://github.com/joeyespo/grip GRIP — an offline MarkDown viewer] (see tip further down also)
* [https://jbt.github.io/markdown-editor/ Markdown viewer and editor (GitHub flavor)]
* [https://jbt.github.io/markdown-editor/ Markdown viewer and editor (GitHub flavor)]

;Review
* [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 Asciidoctor), or reStructuredText (using Sphinx).


== Tips ==
== Tips ==

Revision as of 06:22, 16 October 2018

Links

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

Tips

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">