Auto-updating name mechanism for cross-content references #3892

New Issue

OVERLORD · 2026-02-05T07:47:23+03:00

OVERLORD commented

2026-02-05 07:47:23 +03:00

Originally created by @Konstantin-Davidneko on GitHub (Jul 1, 2023).

Describe the feature you'd like

Allow mentions of Page/Chapter/Book in other pages. So if page change url or name, it will be automatically updated in all pages it was already mentioned.

I think it should be not a big change, if for that will be used already implemented "Include Tags" system.

Describe the benefits this would bring to existing BookStack users

For general use:

When you have big and convoluted knowledge base, you often have a lot of places which links to different pages. Example:

When starting new project, don't forget to configure logging format to match our standards (see Log Formatting documentation)

But then if you updating "Log Format" page with new information you can see that page name no longer fully represent what this page contain. Since you added not only formatting section there, but also sinks, rotation, etc, you maybe want to rename page to be called just "Logging". But all mentions of this document will keep old name. And you will need to find dozens of pages where it was mentioned, to rename it.

My uses-case:

I am currently working on implementing BookStack as knowledge base for my DnD complain. And I want to update it with information found by players, so they can open it and refresh memory from previous games. But that would mean that a lot of pages will have incomplete data, including page titles. Which will update with every game.
For example, sessions will go like that:

Players found ancient temple, and found out that it was to worship oldest of the Gods, who liked apples as sacrifice.
- I am adding pages with titles "Oldest God" with info about god, and page "Tamale of Oldest God". And both two pages will be mentioned in each other
Players found old manuscript which indicates that oldest god was God of Light and some other information.
- I am updating names "Oldest God" to "God of Light" and "Tamale of Oldest God" to "Tamale of God of Light". Then I will need to update text on all links. And then I will create page about manuscript which will have link to previous pages.
Players found out that gods name was Ra'Ha'Ra.
- I will need to change page titles again, and update all mentions in all places.

With content mentioning functionality it will be much easier. Less time will be spent on updating old content, and more time will be spent writing useful information.

Can the goal of this request already be achieved via other means?

How I understand it should be already achievable with code like that:
<a href="<page_url>">{{@3#bkmrk-page-title}}</a>

But for some reason {{@3#bkmrk-page-title}} does not work for me, so can't test.

Have you searched for an existing open/closed issue?

I have searched for existing issues and none cover my fundemental request

How long have you been using BookStack?

6 months to 1 year

Additional context

No response

Originally created by @Konstantin-Davidneko on GitHub (Jul 1, 2023). ### Describe the feature you'd like Allow mentions of Page/Chapter/Book in other pages. So if page change url **or name**, it will be automatically updated in all pages it was already mentioned. I think it should be not a big change, if for that will be used already implemented "Include Tags" system. ### Describe the benefits this would bring to existing BookStack users ### For general use: When you have big and convoluted knowledge base, you often have a lot of places which links to different pages. Example: > When starting new project, don't forget to configure logging format to match our standards (see [Log Formatting](url) documentation) But then if you updating "Log Format" page with new information you can see that page name no longer fully represent what this page contain. Since you added not only formatting section there, but also sinks, rotation, etc, you maybe want to rename page to be called just "Logging". But all mentions of this document will keep old name. And you will need to find dozens of pages where it was mentioned, to rename it. ### My uses-case: I am currently working on implementing BookStack as knowledge base for my DnD complain. And I want to update it with information found by players, so they can open it and refresh memory from previous games. But that would mean that a lot of pages will have incomplete data, including page titles. Which will update with every game. For example, sessions will go like that: 1. Players found ancient temple, and found out that it was to worship oldest of the Gods, who liked apples as sacrifice. * I am adding pages with titles "Oldest God" with info about god, and page "Tamale of Oldest God". And both two pages will be mentioned in each other 2. Players found old manuscript which indicates that oldest god was God of Light and some other information. * I am updating names "Oldest God" to "God of Light" and "Tamale of Oldest God" to "Tamale of God of Light". Then I will need to update text on all links. And then I will create page about manuscript which will have link to previous pages. 3. Players found out that gods name was Ra'Ha'Ra. * I will need to change page titles again, and update all mentions in all places. With content mentioning functionality it will be much easier. Less time will be spent on updating old content, and more time will be spent writing useful information. ### Can the goal of this request already be achieved via other means? How I understand it should be already achievable with code like that: `<a href="<page_url>">{{@3#bkmrk-page-title}}</a>` But for some reason `{{@3#bkmrk-page-title}}` does not work for me, so can't test. ### Have you searched for an existing open/closed issue? - [X] I have searched for existing issues and none cover my fundemental request ### How long have you been using BookStack? 6 months to 1 year ### Additional context _No response_

OVERLORD added the 🔨 Feature Request label 2026-02-05 07:47:23 +03:00

OVERLORD closed this issue

2026-02-05 07:47:24 +03:00

OVERLORD commented

2026-02-05 07:47:29 +03:00

@ssddanbrown commented on GitHub (Jul 10, 2023):

Thanks for the request. I'm going to update the title to reflect the fundamental underlying desire, since the specific action of mentions is already open in #953.
The suggested workaround is related to #3101.

Personally I'm not fond of adding dynamic abilities to content due to complications they introduce, so would prefer not to have dynamically linked references.

@ssddanbrown commented on GitHub (Jul 10, 2023): Thanks for the request. I'm going to update the title to reflect the fundamental underlying desire, since the specific action of mentions is already open in #953. The suggested workaround is related to #3101. Personally I'm not fond of adding dynamic abilities to content due to complications they introduce, so would prefer not to have dynamically linked references.

OVERLORD commented

2026-02-05 07:47:32 +03:00

@ssddanbrown commented on GitHub (Sep 13, 2025):

I'm going to go ahead and close this off since there's been no additional desire for this, while being something which could lead to issues for others (unless made optional) while adding complication.

@ssddanbrown commented on GitHub (Sep 13, 2025): I'm going to go ahead and close this off since there's been no additional desire for this, while being something which could lead to issues for others (unless made optional) while adding complication.

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: starred/BookStack#3892