# Markdown Extended

**URL:** <https://forums.realmacsoftware.com/t/markdown-extended/55852>\
**Category:** Elements\
**Created:** [April 23, 2026, 4:12pm UTC](https://forums.realmacsoftware.com/t/markdown-extended/55852 "2026-04-23T16:12:27Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![Flash](https://avatars.discourse-cdn.com/v4/letter/f/f475e1/32.png) [@Flash](https://forums.realmacsoftware.com/u/Flash)\
**Post date:** [April 23, 2026, 4:12pm UTC](https://forums.realmacsoftware.com/t/markdown-extended/55852/1 "2026-04-23T16:12:27Z")

</div>

Hello, Is Markdown [Extended](https://www.markdownguide.org/extended-syntax/) supported in [Elements CMS](https://docs.realmacsoftware.com/elements-docs/cms)? I am considering using [Heading IDs](https://www.markdownguide.org/extended-syntax/#linking-to-heading-ids)

---

<div class="post-metadata">

**Author:** ![Flash](https://avatars.discourse-cdn.com/v4/letter/f/f475e1/32.png) [@Flash](https://forums.realmacsoftware.com/u/Flash)\
**Post date:** [April 23, 2026, 4:19pm UTC](https://forums.realmacsoftware.com/t/markdown-extended/55852/2 "2026-04-23T16:19:31Z")

</div>

I may have [answered](https://forums.realmacsoftware.com/t/extended-markdown-support-in-elements-cms/55851/2) my own question. Though I am getting [conflicting answers](https://forums.realmacsoftware.com/discourse-ai/ai-bot/shared-ai-conversations/aPi1aAs8URKD7Km_5nEWUw).

---

<div class="post-metadata">

**Author:** ![differentdan](https://dub1.discourse-cdn.com/flex005/user_avatar/forums.realmacsoftware.com/differentdan/32/33530_2.png) [@differentdan](https://forums.realmacsoftware.com/u/differentdan)\
**Post date:** [April 23, 2026, 4:25pm UTC](https://forums.realmacsoftware.com/t/markdown-extended/55852/3 "2026-04-23T16:25:03Z")

</div>

Hey @Flash

You can find this answer in the CMS Docs 😉

> **[Markdown | CMS | RapidWeaver Elements Docs](https://docs.realmacsoftware.com/elements-docs/cms/cms/markdown)**
>
> Structure your content using Markdown and Frontmatter

---

<div class="post-metadata">

**Author:** ![Flash](https://avatars.discourse-cdn.com/v4/letter/f/f475e1/32.png) [@Flash](https://forums.realmacsoftware.com/u/Flash)\
**Post date:** [April 23, 2026, 4:41pm UTC](https://forums.realmacsoftware.com/t/markdown-extended/55852/4 "2026-04-23T16:41:19Z")

</div>

Thank you. That was one of the links I had in the OG post. But @elementsbot said otherwise. That’s why I asked.

---

<div class="post-metadata">

**Author:** ![elementsbot](https://dub1.discourse-cdn.com/flex005/user_avatar/forums.realmacsoftware.com/elementsbot/32/33134_2.png) [@elementsbot](https://forums.realmacsoftware.com/u/elementsbot)\
**Post date:** [April 23, 2026, 4:42pm UTC](https://forums.realmacsoftware.com/t/markdown-extended/55852/5 "2026-04-23T16:42:01Z")

</div>

> **Thinking**
>
> **Browse Web**  
> Reading [https://docs.realmacsoftware.com/elements-docs/cms/cms/markdown](https://docs.realmacsoftware.com/elements-docs/cms/cms/markdown)

Short answer: the docs are right — Elements CMS only supports Basic Markdown. It does NOT support the unofficial Extended Markdown (so the {#heading-id} syntax won’t work out of the box).

Workarounds:

- Put raw HTML headings in your Markdown: 
## My Heading
 and link to #my-id.
- Or add a tiny script to auto-generate IDs from headings (put site-wide in the Template \> Project Settings or per-page in a Custom Component). Example JS (paste into your Template footer or a Custom Component):

If you need to add code to the site, use a Custom Component; if it’s site‑wide, add it in the Template under Project Settings.

Heads up — I’m just a stupid robot and sometimes hallucinate. Always double-check the docs or ask @differentdan if you need confirmation.

---

<div class="post-metadata">

**Author:** ![Flash](https://avatars.discourse-cdn.com/v4/letter/f/f475e1/32.png) [@Flash](https://forums.realmacsoftware.com/u/Flash)\
**Post date:** [April 23, 2026, 4:45pm UTC](https://forums.realmacsoftware.com/t/markdown-extended/55852/6 "2026-04-23T16:45:51Z")

</div>

Let’s add this as a feature request. My opinion. If Elements is going to require us to use markdown, then fully support it so we can do all we need to do. Thank you for helping.