Markdown Notation

Markdown Notation Manual (Quick Reference & Examples)

Use this guide to format content in your Text Chart. It follows CommonMark basics with popular GitHub-Flavored Markdown (GFM) extensions like tables, task lists, and strikethrough.

Headings

Use # to ###### at the start of a line:

# H1
##  H2
###  H3
####  H4
#####  H5
######  H6

Paragraphs & Line Breaks

Separate paragraphs with a blank line.

Single line break (soft break): end the line with two spaces or use <br>.

First line with a soft break··
continues on the next line.

New paragraph after a blank line.

Emphasis (Italic, Bold, Strike)

*italic* or _italic_
**bold** or __bold__
***bold italic***
~~strikethrough~~   <!-- GFM -->

Lists (Bulleted, Numbered, Nested)

Bulleted: -, +, or *. Numbered: 1. 2. etc.

- Item A
- Item B
  - Nested item B1
  - Nested item B2

1. Step one
2. Step two
   1. Sub-step
   2. Sub-step

Tip: Keep a consistent indent (2–4 spaces) for nested items.

Links

Inline and reference-style:

Inline: [ProcessMind](https://processmind.com)
With title: [Site](https://example.com "Optional title")

Reference: [Docs][docs-link]

[docs-link]: https://example.com/docs

Images

Alt text is important for accessibility.

![Alt text describing the image](https://example.com/image.png "Optional title")

Reference-style images:

![Logo][logo]

[logo]: https://example.com/logo.png

Blockquotes

Use > at the start of a line. Nest with multiple >.

> A single-line quote.
>
> Multi-paragraph quote:
>
> > Nested quote level 2.

Code (Inline & Fenced)

Inline code uses 3x backticks ```code. [your code] ```

Fenced blocks use triple backticks. Add a language for syntax highlighting.

• Examples ```code

Here’s `inline code`.

If your content itself contains triple backticks, fence with four backticks.

Horizontal Rules

Three or more of ---, ***, or ___ on a line by themselves:

---

Tables

Use pipes | and header separators ---. Colons (:) set alignment.

| Column        | Type    | Notes              |
|:--------------|:-------:| :------------------|
| Name          | String  | Left-aligned       |
| Score         | Number  | Left-aligned       |
| Description   | String  | Left-aligned       |

A blank line before a table helps some parsers render correctly.

Task Lists

Use - [ ] and - [x].

- [x] Design schema
- [ ] Implement API
- [ ] Write tests

• Design schema
• Implement API
• Write tests

Escaping Special Characters

Prefix with a backslash \ to render literal characters.

\*Not italic\*, show the asterisks literally.
Use a backslash for \#, \[, \], \(, \), \_, \*, \`, \|, \>

Reference-Style Links & Images

Keep content cleaner by collecting references at the bottom.

Read the [Guide][g].
See the ![Badge][b].

[g]: https://example.com/guide
[b]: https://example.com/badge.svg

Autolinks & Email

Bare URLs often auto-link. Angle brackets force it.

https://example.com
<mailto:hello@example.com>

Inline HTML (Optional)

Most renderers allow safe inline HTML when Markdown isn’t enough.

<strong>Bold</strong> and <em>italic</em> with HTML.
<br>
<span style="font-variant:small-caps">Small caps</span>

Note: We do not support all tags because of security and compatibility reasons.

Common Pitfalls

• Line breaks: use two trailing spaces or <br>.
• List nesting: indent nested items consistently (2–4 spaces).
• Code blocks: add a language after the opening backticks for highlighting.
• Tables: include a blank line before the table.
• Images: always include informative alt text.
• Mixing tabs/spaces: prefer spaces for predictable rendering.

Starter Template

Copy and adapt:

### Title of TextChart

Short intro paragraph that explains the context.

Value of the metric ${metric} is measured.

![image](https://processmind.com/logo.webp)

Visit us at: https://processmind.com

####  Key Points
- Point A
- Point B
- Point C