Table of Contents

Markdown

Conversion

Markdown to ...

Online-Service: https://dillinger.io/

HTML to Markdown

Have a look at to-markdown written by Dom Christie. Thanks to Galen Gidman for pointing this out!

  • Tip 1: If your HTML source makes heavy use of tables it might help to keep the option GitHub Flavored Markdown disabled.

    Disabled Option GitHub Flavored Markdown

    This way the table tags will be left untouched. As HTML tags may be used within Markdown files the resulting syntax is still valid. It is a compromise of course because the output is not clean Markdown. For most migrations it is probably the way to go due to the Markdown table functionality beeing much more restricted compared to HTML. You would certainly end up fixing merged cells, line breaks and so on en masse.

  • Tip 2: When keeping HTML table tags within your Markdown file make sure two tables are seperated by an empty line. Some interpreters will mess up the output otherwise.

    <table>...</table>

<table>...</table>
  • Tip 3: Make sure the line breaks on the converted text work out to your liking. Their conversion works differently between normal and GitHub Flavored Markdown.
    • With normal Markdown, each HTML line break (<br /> that is) will be replaced by two blanks ( ), which is the equivalent in Markdown and always works as expected.
    • With GitHub Flavored Markdown enabled, HTML line breaks are omitted (dropped without replacement). Check if your destination environment treats simple line endings (CRLN / LN / CR that is, depending on your operating system) as new lines and add additional empty lines as needed. Personally, I will always go for two blanks (or empty lines respectively) to make sure the files work in most Markdown environments.