10 Markdown Tips and Tricks for Faster Writing

Most people use inline links: [text](url). But when a paragraph has multiple links, inline URLs create a wall of noise. Reference-style links keep your text clean:

Check out [React][react], [Vue][vue], and [Svelte][svelte]
for modern frontend development.

[react]: https://react.dev
[vue]: https://vuejs.org
[svelte]: https://svelte.dev

The link definitions can go anywhere in the document — most people put them at the bottom. The raw text reads like natural prose instead of being cluttered with URLs.

Need to display literal Markdown characters? Prefix them with a backslash:

\*This is not italic\*
\# This is not a header
\[This is not a link\](or this)
Price: \$19.99

This is especially useful when writing about Markdown itself, or when documenting commands that use special characters.

In GitHub Flavored Markdown and many other renderers, you can use HTML <details> tags to create collapsible sections — perfect for long content that readers can expand on demand:

<details>
<summary>Click to expand installation instructions</summary>

1. Clone the repository
2. Run `npm install`
3. Run `npm start`

You can use **Markdown** inside the details block!

</details>

This is incredibly useful in README files for hiding verbose sections (changelogs, configuration options, FAQ) while keeping the page scannable.

Most Markdown renderers (including GitHub) auto-generate anchor IDs from headings. You can link directly to any section:

## Installation Guide

...content...

## Usage

See the [Installation Guide](#installation-guide) above.

The anchor ID is generated by lowercasing the heading, replacing spaces with hyphens, and removing special characters. So "Getting Started (Quick)" becomes #getting-started-quick.

One of the most confusing things about Markdown: pressing Enter once doesn't create a new line in the output. Markdown requires either a blank line (new paragraph) or two trailing spaces (line break within a paragraph):

This line and
this line render on the SAME line.

This line  ← (two trailing spaces)
and this line are on SEPARATE lines.

This is a new paragraph entirely.

Some Markdown editors and renderers also support <br> tags or backslash line breaks (\ at end of line) for explicit line breaks.

List items can contain multiple paragraphs, code blocks, blockquotes, and even nested lists. The key is indentation — align continuation content with the start of the list item text:

1. First step

   This paragraph is still part of item 1.
   Indented 3 spaces to align with the text.

   ```bash
   npm install
   ```

2. Second step

   > A blockquote inside a list item.

   - A nested sublist
   - With multiple items

This lets you create richly structured documents where each list item is a mini-section with its own formatting.

Need to show a code block that itself contains triple backticks? Use four backticks for the outer fence, or use tildes instead:

````markdown
Here's how to create a code block:

```javascript
console.log("Hello!");
```
````

Or using tildes:

~~~markdown
```javascript
console.log("Hello!");
```
~~~

This is essential when writing documentation about Markdown itself. You can nest any number of backticks — the outer fence just needs more backticks than any inner fence.

While not part of the CommonMark spec, many Markdown processors (PHP Markdown Extra, Pandoc, some static site generators) support definition lists:

Markdown
: A lightweight markup language for creating
  formatted text using a plain-text editor.

HTML
: HyperText Markup Language, the standard
  markup language for documents on the web.

CSS
: Cascading Style Sheets, used for describing
  the presentation of a document written in HTML.

Definition lists are great for glossaries, API documentation, and configuration references. Check your renderer's documentation to confirm support.

Instead of manually maintaining a table of contents, use the heading-link trick from Tip #4 to build one that links to each section:

## Table of Contents

- [Installation](#installation)
- [Configuration](#configuration)
- [Usage](#usage)
  - [Basic Usage](#basic-usage)
  - [Advanced Options](#advanced-options)
- [Contributing](#contributing)
- [License](#license)

Many editors and tools can auto-generate this for you. VS Code has extensions that create and update a TOC from your headings automatically. GitHub also provides a built-in TOC icon on rendered Markdown files with multiple headings.

Front matter is a block of YAML at the top of a Markdown file that stores metadata. It's used by static site generators, documentation tools, and content management systems:

---
title: "My Blog Post"
date: 2026-02-06
author: "Jane Doe"
tags: [markdown, writing, productivity]
description: "A guide to writing better Markdown"
draft: false
---

# My Blog Post

The actual content starts after the front matter...

Front matter is delimited by triple dashes (---). It's invisible in the rendered output but available to the build tool for generating navigation, filtering posts, creating RSS feeds, and managing content.

Tools like Pandoc use front matter for PDF metadata (title pages, author info), and static site generators like Hugo and Jekyll rely on it for page configuration.

Most Markdown editors support keyboard shortcuts that save even more time:

• Ctrl/Cmd + B — Toggle bold
• Ctrl/Cmd + I — Toggle italic
• Ctrl/Cmd + K — Insert link
• Ctrl/Cmd + Shift + C — Toggle code block
• Tab/Shift+Tab — Indent/outdent list items

These work in VS Code, Obsidian, Typora, and many other editors. If you're writing Markdown daily, learning the shortcuts for your editor will pay off quickly.

Want to practice these techniques? Open the MarkdownFTW editor and try them out with live preview — see the results as you type.