> For the complete documentation index, see [llms.txt](https://docs.realmacsoftware.com/elements-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.realmacsoftware.com/elements-docs/using-elements/components/content-and-media/markdown.md).

# Markdown

Write and render structured content using Markdown syntax

The Markdown component renders standard Markdown inside an Elements layout. It is useful for documentation, articles, technical content, and text written outside Elements.

Markdown content inherits a Theme Studio Typography style, keeping headings, paragraphs, lists, links, and code visually consistent.

{% embed url="<https://youtu.be/ZkmYC_rAN4o>" %}

### How to Use Markdown

You’ll find Markdown under **Content** in the Components list.

1. Drag **Markdown** onto the page.
2. Right-click the component and choose **Edit Markdown**.
3. Enter or paste Markdown in the editor.
4. Choose a Typography Style and semantic Tag in the Inspector.
5. Preview links, images, lists, and code on the page.

The content renders live as you type. You can also drag an image from Resources into the Markdown editor to insert its correct path.

### Supported Markdown Syntax

**Headings**

```markdown
# Heading 1
## Heading 2
### Heading 3
```

**Emphasis**

```markdown
*Italic text*
**Bold text**
***Bold and italic***
```

**Lists**

```markdown
- Unordered item
- Another item

1. First item
2. Second item
```

**Links and images**

```markdown
[Visit Realmac Software](https://realmacsoftware.com)
![Alternative text](https://example.com/photos/image-name.jpg)
```

**Quotes and code**

```markdown
> This is a blockquote.

`inline code`
```

Paragraphs are separated by a blank line. The component supports standard [Markdown syntax](https://daringfireball.net/projects/markdown/syntax).

### Component Settings

#### General

**Style** chooses a Theme Studio Typography style and defaults to Article. It styles all nested Markdown elements.

**Tag** sets the semantic wrapper and defaults to Article. Options are Article, Section, Aside, Main Content, Header, Footer, Div, and Span.

The tag changes document meaning rather than visual styling. Use Main Content only once per page.

### Notes and Limitations

* Markdown renders as static content.
* Elements components cannot be embedded inside Markdown.
* Visual styling is controlled at block level through Theme Studio.
* Use separate Elements components when you need fine-grained layout or interaction.

### Accessibility

Use one clear page heading, keep heading levels in order, describe images with useful alternative text, and write link text that makes sense out of context.

### Related Components

* [Typography](/elements-docs/using-elements/components/content-and-media/typography.md) — Styles long-form content as a structured block.
* [Text](/elements-docs/using-elements/components/content-and-media/text.md) — Gives detailed control over individual headings and short text.
* [Image](/elements-docs/using-elements/components/content-and-media/image.md) — Provides responsive image, alt text, and lightbox controls.

| Common Control                                                                                                     | Description                                                             |
| ------------------------------------------------------------------------------------------------------------------ | ----------------------------------------------------------------------- |
| [Link](/elements-docs/using-elements/components/common-controls/link.md)                                           | Link to a page, resource, anchor, email address, or website.            |
| [Layout](/elements-docs/using-elements/components/common-controls/layout.md)                                       | Control positioning, stacking, visibility, overflow, and isolation.     |
| [Sizing](/elements-docs/using-elements/components/common-controls/sizing.md)                                       | Set width, height, and responsive size constraints.                     |
| [Spacing](/elements-docs/using-elements/components/common-controls/spacing.md)                                     | Add responsive margin and padding.                                      |
| [Typography & Text Styles](/elements-docs/using-elements/components/common-controls/typography-and-text-styles.md) | Control fonts, text spacing, decoration, colour, and semantic wrappers. |
| [Backgrounds](/elements-docs/using-elements/components/common-controls/backgrounds.md)                             | Apply colour, image, gradient, SVG, video, and hover backgrounds.       |
| [Transitions](/elements-docs/using-elements/components/common-controls/transitions.md)                             | Choose what animates and set its timing curve, duration, and delay.     |
| [Effects](/elements-docs/using-elements/components/common-controls/effects.md)                                     | Apply shadows, opacity, and hover effects.                              |
| [Filters](/elements-docs/using-elements/components/common-controls/filters.md)                                     | Apply blur, brightness, saturation, shadow, and backdrop effects.       |
| [Transforms](/elements-docs/using-elements/components/common-controls/transforms.md)                               | Scale, rotate, move, and skew components.                               |
| [Borders](/elements-docs/using-elements/components/common-controls/borders.md)                                     | Set border style, colour, opacity, width, radius, and hover states.     |
| [Advanced](/elements-docs/using-elements/components/common-controls/advanced.md)                                   | Add CSS classes and IDs, or change supported HTML tags.                 |


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.realmacsoftware.com/elements-docs/using-elements/components/content-and-media/markdown.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.