Markdown Cheat Sheet

For details, see Markdown Syntax Style Guide.

Basic Syntax


Include blank lines before and after headings.

# H1 (article title)

## H2 (main page headings)

### H3

#### H4 

H4 and higher are simply formatted as **bold**.

## Sample heading with anchor ID for deep linking {#anchor-id}

Anchor IDs are required to creating deep links. See []

Bold and italics

Bold: This is **bold** text

Italic: This is *italicized* text


Include blank lines before and after lists.

Important: Use the same syntax for lists within a document. For example, don’t combine * and +, or you’ll get a validation error.

Ordered List:

1. First item
1. Next item
1. Next item
  1. First item
  2. Next item
  3. Next item

Unordered List:

* First item
* Second item
* Third item
  • First item
  • Second item
  • Third item

Nested List:

To preserve numbering, indent items between steps, and handle blank lines properly.

1. First item

   >Indented item between steps.

1. Second item


1. Third item
  1. First item


    Indented item between steps.

  2. Second item

  3. Third item








Links to internal articles:

See [Using processing rules](admin/getting-started/
See complete [Markdown Syntax Guide](

See complete Markdown Syntax Guide

Root links:


Deep links:

Jump to [Change properties](#change-properties) heading at the end of this page.

See [Links and cross-references](/docs/authoring-guide-exl/using/markdown/syntax-style-guide.html?lang=en#links-and-cross-references) in a different article.

Jump to Change properties heading at the end of this page.

See Links and cross-references in a different article.

Code blocks

Code (inline):

This is `code` text

This is code text

Code block (fenced):

Use three backticks ( ` ) before and after the code lines. The open and close must have the same indent.

Following the backticks, specify the programming language that is used, ie python, javascript, etc, and this will allow syntax highlighting on the front end. If no language is specified, no highlighting will be available.

(Ignore the backslashes \ before the backticks in this example. We added those to show the example code.)

“firstName”: “John”,
“lastName”: “Smith”,
“age”: 25

  "firstName": "John",
  "lastName": "Smith",
  "age": 25


Add metadata to the top of the markdown file. The next line after the metadata line (and blank line) MUST be the article title (# Title).

title: Title for search optimization.
description: This is the article description used for search optimization. Use common search keywords and synonyms.

# Article title {#unique-anchor}

For a list of required and optional metadata, see Metadata for AdobeDocs.

Advanced Markdown Syntax


| Syntax | Description |
| --- | --- |
| Column 1 | Column 2 |
| Paragraph | Text |
Syntax Description
Column 1 Column 2
Paragraph Text

Extended Markdown Syntax for Adobe documentation


We support Note, Tip, Important, Caution, and Warning. New tags include Prerequisites, Admin, and Availability.


>This is a standard NOTE block.
>[!Related Articles]



This is a standard NOTE block.


This is a standard tip.


This is an important note.


This is a warning.


This is a caution.


This is an admin note. EXL only.


This is an availability note. EXL only.


This is a Prerequisites note. EXL only.


The video extension allows the video to be played on the page. You can also create a standard link to the video.


More Like This

Use the “More Like This” component to display related links at the end of an article.


More Like This syntax


Localization tags

Use [!DNL] for certain solution names (such as Target) and third-party names (such as Microsoft Windows) that should remain in English. Use [!UICONTROL] for menu commands, dialog box options, and other UI items.


It is not necessary to use [DNL] for every solution name. The localization team handles common solution names such as Analytics, Audience Manager, and Campaign automatically.


Do not use localization tags in HTML or code because they will display in the rendered output.

Target your objectives by using [!DNL Target] to perform A/B tests.

1. Click the **[!UICONTROL Process]** command.
1. Choose **[!UICONTROL Print All]** to print all the files on your server.

   The [!UICONTROL Print All] dialog box appears.

Change properties

For example, change heading ID:

### My Heading {#custom-id}

For details, see the Markdown Syntax Style Guide.

On this page