# Custom content dir or support absolute internal link

**URL:** <https://zola.discourse.group/t/custom-content-dir-or-support-absolute-internal-link/1242>\
**Category:** Feature requests\
**Created:** [March 23, 2022, 5:49pm UTC](https://zola.discourse.group/t/custom-content-dir-or-support-absolute-internal-link/1242 "2022-03-23T17:49:10Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![theowenyoung](https://yyz2.discourse-cdn.com/free1/user_avatar/zola.discourse.group/theowenyoung/32/705_2.png) [@theowenyoung](https://zola.discourse.group/u/theowenyoung)\
**Post date:** [March 23, 2022, 5:49pm UTC](https://zola.discourse.group/t/custom-content-dir-or-support-absolute-internal-link/1242/1 "2022-03-23T17:49:10Z")

</div>

Can I custom the content folder to another folder instead of `content`.

I want internal link works for both local editors and Zola.

if Zola allowed me to specify the content folder, then I can specify the content folder to `@`, then both the local editor and Zola will work well.

```bash
├── config.toml
├── @
├── sass
├── static
├── templates
└── themes

```

In `config.toml`

```bash
content_dir = "@"

```

Example markdown file:

```auto
[tools](@/tools.md)

```

Alternative:

Treat `content/xxx.md` as `@/xxx.md`, so the following link will work well both local and Zola.

```bash
[post1](content/post1.md)

```

This can change quickly. I have also tested this feature, [treat markdown internal link content/ as @/ · theowenyoung/zola@b0b463a (github.com)](https://github.com/theowenyoung/zola/commit/b0b463adb21c2bfe2ea71664459a6967d6a7208a) , it works well.

Internal Link is the most painful for me on Zola. I don’t want to bind Zola deeply, this will let Zola become the only service to understand my plain document.

I like Zola in everything, it’s a thoughtful framework.

---

<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:** [March 24, 2022, 12:07pm UTC](https://zola.discourse.group/t/custom-content-dir-or-support-absolute-internal-link/1242/2 "2022-03-24T12:07:28Z")

</div>

> [@theowenyoung](#):
>
> Internal Link is the most painful for me on Zola. I don’t want to bind Zola deeply, this will let Zola become the only service to understand my plain document.

You can search & replace `](@/content/` by `](` and end up with your no reference of zola and just the relative path to the md file, that doesn’t seem like a lock in?

> [@theowenyoung](#):
>
> Treat `content/xxx.md` as `@/xxx.md` , so the following link will work well both local and Zola.

Those are potentially referring to 2 different things so they cannot be equivalent.

---

<div class="post-metadata">

**Author:** ![theowenyoung](https://yyz2.discourse-cdn.com/free1/user_avatar/zola.discourse.group/theowenyoung/32/705_2.png) [@theowenyoung](https://zola.discourse.group/u/theowenyoung)\
**Post date:** [March 24, 2022, 12:56pm UTC](https://zola.discourse.group/t/custom-content-dir-or-support-absolute-internal-link/1242/3 "2022-03-24T12:56:12Z")

</div>

yeah, thanks for the quick reply, yeah, you are right. now I think there is no lock-in problem.

so the main problem for me is that I want to work well both in the local file system and Zola. Now I have built the Zola for me using [treat markdown internal link content/ as @/ · theowenyoung/zola@b0b463a (github.com)](https://github.com/theowenyoung/zola/commit/b0b463adb21c2bfe2ea71664459a6967d6a7208a) , this can solve my problem now.