# Enabling relative paths up to the space root

**URL:** <https://community.silverbullet.md/t/enabling-relative-paths-up-to-the-space-root/4446>\
**Category:** General\
**Created:** [October 13, 2026, 4:53pm UTC](https://community.silverbullet.md/t/enabling-relative-paths-up-to-the-space-root/4446 "2026-10-13T16:53:31Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Offray](https://community.silverbullet.md/user_avatar/community.silverbullet.md/offray/32/3900_2.png) [@Offray](https://community.silverbullet.md/u/Offray)\
**Post date:** [October 13, 2026, 4:53pm UTC](https://community.silverbullet.md/t/enabling-relative-paths-up-to-the-space-root/4446/1 "2026-10-13T16:53:31Z")

</div>

Hi all,

As I detailed in a previous post, I'm exploring how to [integrate SB into our pre-existing documentation/publishing workflows](https://community.silverbullet.md/t/markdown-customizations-and-external-lua-programs/4443) and that would mean to require being able to point to dot prefixed files while being compatible with the [security feature recently announced](https://community.silverbullet.md/t/silverbullet-2-12-growing-with-you/4424/13):

> [@SilverBullet 2.12: Growing With You](https://community.silverbullet.md/t/silverbullet-2-12-growing-with-you/4424/13):
>
> - Security: the filesystem API refuses access to dot-prefixed files and directories, consistent with space listings.

In our tests, when you prefix a file with a `./`, SB adds an extra leading `/` (becoming `/./`), trying to address all page addresses from the root of the Space and making the address incompatible with Static Site Genarators that allow leading dots to refer to relative paths.

So, given that SB knows where is located the current page into the working Space, I wonder if the dot prefixed files can be accepted until the Space root. For example, any `./page` can be accepted as it's located in the same space of the page we are editing at the moment and any `../(../)` can be accepted if the page we are pointing is still inside the working space. i.e. a page that is two levels deep in the space would accept until two `../` concatenated sequences, a page three levels deep would accept three levels and so on. This would make the SB editing experience consistent with the one in other editors like VSCode/Codium, that accept relative paths and are used to edit Markdown.

If the proposal makes sense, I will open a feature request in the repository.

Cheers,

---

<div class="post-metadata">

**Author:** ![zef](https://community.silverbullet.md/user_avatar/community.silverbullet.md/zef/32/7_2.png) [@zef](https://community.silverbullet.md/u/zef)\
**Post date:** [October 13, 2026, 4:55pm UTC](https://community.silverbullet.md/t/enabling-relative-paths-up-to-the-space-root/4446/2 "2026-10-13T16:55:25Z")

</div>

I think so, please create a github issue for this.

---

<div class="post-metadata">

**Author:** ![Offray](https://community.silverbullet.md/user_avatar/community.silverbullet.md/offray/32/3900_2.png) [@Offray](https://community.silverbullet.md/u/Offray)\
**Post date:** [October 13, 2026, 7:10pm UTC](https://community.silverbullet.md/t/enabling-relative-paths-up-to-the-space-root/4446/3 "2026-10-13T19:10:29Z")

</div>

Done at: [Enabling relative paths up to the space root · Issue #2200 · silverbulletmd/silverbullet · GitHub](https://github.com/silverbulletmd/silverbullet/issues/2200).