# Linking to internal content in non-markdown content

**URL:** <https://zola.discourse.group/t/linking-to-internal-content-in-non-markdown-content/320>\
**Category:** Support\
**Created:** [February 15, 2020, 9:58am UTC](https://zola.discourse.group/t/linking-to-internal-content-in-non-markdown-content/320 "2020-02-15T09:58:28Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![HugoTrentesaux](https://yyz2.discourse-cdn.com/free1/user_avatar/zola.discourse.group/hugotrentesaux/32/105_2.png) [@HugoTrentesaux](https://zola.discourse.group/u/HugoTrentesaux)\
**Post date:** [February 15, 2020, 9:58am UTC](https://zola.discourse.group/t/linking-to-internal-content-in-non-markdown-content/320/1 "2020-02-15T09:58:28Z")

</div>

Sometimes in markdown files you want to insert custom html (or even in shortcodes).  
Is there a way to link to internal content this way ?

e.g.

```auto
<a href="@/page.md">Page</a>

```

Linking to internal content (including files) is central to avoid broken links when moving stuff. I’ve been missing this after “hard”-linking colocated assets and setting the path of the page in the front-matter or simply in case of typo. Why not doing the same for assets? i.e `![img](@/non_collocated/asset.jpg)`

---

<div class="post-metadata">

**Author:** ![keats](https://avatars.discourse-cdn.com/v4/letter/k/34f0e0/32.png) [@keats](https://zola.discourse.group/u/keats)\
**Post date:** [February 15, 2020, 7:27pm UTC](https://zola.discourse.group/t/linking-to-internal-content-in-non-markdown-content/320/2 "2020-02-15T19:27:29Z")

</div>

No, HTML content is ignored when rendering markdown and to do that we would need to parse HTML which is not trivial… That’s unlikely to happen as it would crash performance
