Markdown Explained: Writing That Becomes Any Format
Introduction Every README on GitHub, every post on Dev.to and Hashnode (the platforms this blog distributes to), and most technical documentation is written in Markdown: plain text with a few simple marks for formatting. It was designed to be readable as-is — even before conversion — and to convert cleanly into HTML, PDF, slides, and more. If you write anything technical, Markdown is the format to learn first. The syntax in one minute Markdown's core is small enough to learn in a sitting: # Heading 1 ## Heading 2 **bold text** and *italic text* - A bullet list item - Another item 1. A numbered item 2. Another numbered item [link text](https://example.com) `inline code` and a fenced code block (shown in the draft file as a nested example) ``` a fenced code block ``` Headings, emphasis, lists, links, and code cover the vast majority of documents. Tables, images, and blockquotes extend it slightly, and "flavours" (GitHub Flavoured Markdown being the standard) add convenience...