mirror of
https://github.com/BookStackApp/BookStack.git
synced 2026-02-05 00:29:48 +03:00
BookStack Community Forum? #1356
Closed
opened 2026-02-05 00:40:53 +03:00 by OVERLORD
·
5 comments
No Branch/Tag Specified
development
l10n_development
further_theme_development
release
llm_only
vectors
v25-11
docker_env
drawio_rendering
user_permissions
ldap_host_failover
svg_image
prosemirror
captcha_example
fix/video-export
v25.12.3
v25.12.2
v25.12.1
v25.12
v25.11.6
v25.11.5
v25.11.4
v24.11.4
v25.11.3
v25.11.2
v25.11.1
v25.11
v25.07.3
v25.07.2
v25.07.1
v25.07
v25.05.2
v25.05.1
v25.05
v25.02.5
v25.02.4
v25.02.3
v25.02.2
v25.02.1
v25.02
v24.12.1
v24.12
v24.10.3
v24.10.2
v24.10.1
v24.10
v24.05.4
v24.05.3
v24.05.2
v24.05.1
v24.05
v24.02.3
v24.02.2
v24.02.1
v24.02
v23.12.3
v23.12.2
v23.12.1
v23.12
v23.10.4
v23.10.3
v23.10.2
v23.10.1
v23.10
v23.08.3
v23.08.2
v23.08.1
v23.08
v23.06.2
v23.06.1
v23.06
v23.05.2
v23.05.1
v23.05
v23.02.3
v23.02.2
v23.02.1
v23.02
v23.01.1
v23.01
v22.11.1
v22.11
v22.10.2
v22.10.1
v22.10
v22.09.1
v22.09
v22.07.3
v22.07.2
v22.07.1
v22.07
v22.06.2
v22.06.1
v22.06
v22.04.2
v22.04.1
v22.04
v22.03.1
v22.03
v22.02.3
v22.02.2
v22.02.1
v22.02
v21.12.5
v21.12.4
v21.12.3
v21.12.2
v21.12.1
v21.12
v21.11.3
v21.11.2
v21.11.1
v21.11
v21.10.3
v21.10.2
v21.10.1
v21.10
v21.08.6
v21.08.5
v21.08.4
v21.08.3
v21.08.2
v21.08.1
v21.08
v21.05.4
v21.05.3
v21.05.2
v21.05.1
v21.05
v21.04.6
v21.04.5
v21.04.4
v21.04.3
v21.04.2
v21.04.1
v21.04
v0.31.8
v0.31.7
v0.31.6
v0.31.5
v0.31.4
v0.31.3
v0.31.2
v0.31.1
v0.31.0
v0.30.7
v0.30.6
v0.30.5
v0.30.4
v0.30.3
v0.30.2
v0.30.1
v0.30.0
v0.29.3
v0.29.2
v0.29.1
v0.29.0
v0.28.3
v0.28.2
v0.28.1
v0.28.0
v0.27.5
v0.27.4
v0.27.3
v0.27.2
v0.27.1
v0.27
v0.26.4
v0.26.3
v0.26.2
v0.26.1
v0.26.0
v0.25.5
v0.25.4
v0.25.3
v0.25.2
v0.25.1
v0.25.0
v0.24.3
v0.24.2
v0.24.1
v0.24.0
v0.23.2
v0.23.1
v0.23.0
v0.22.0
v0.21.0
v0.20.3
v0.20.2
v0.20.1
v0.20.0
v0.19.0
v0.18.5
v0.18.4
v0.18.3
v0.18.2
v0.18.1
v0.18.0
v0.17.4
v0.17.3
v0.17.2
v0.17.1
v0.17.0
v0.16.3
v0.16.2
v0.16.1
v0.16.0
v0.15.3
v0.15.2
v0.15.1
v0.15.0
v0.14.3
v0.14.2
v0.14.1
v0.14.0
v0.13.1
v0.13.0
v0.12.2
v0.12.1
v0.12.0
v0.11.2
v0.11.1
v0.11.0
v0.10.0
v0.9.3
v0.9.2
v0.9.1
v0.9.0
v0.8.2
v0.8.1
v0.8.0
v0.7.6
v0.7.5
v0.7.4
v0.7.3
0.7.2
v.0.7.1
v0.7.0
v0.6.3
v0.6.2
v0.6.1
v0.6.0
v0.5.0
Labels
Clear labels
🎨 Design
📖 Docs Update
🐛 Bug
🐛 Bug
:cat2:🐈 Possible duplicate
💿 Database
☕ Open to discussion
💻 Front-End
🐕 Support
🚪 Authentication
🌍 Translations
🔌 API Task
🏭 Back-End
⛲ Upstream
🔨 Feature Request
🛠️ Enhancement
🛠️ Enhancement
🛠️ Enhancement
❤️ Happy feedback
🔒 Security
🔍 Pending Validation
💆 UX
📝 WYSIWYG Editor
🌔 Out of scope
🔩 API Request
:octocat: Admin/Meta
🖌️ View Customization
❓ Question
🚀 Priority
🛡️ Blocked
🚚 Export System
♿ A11y
🔧 Maintenance
> Markdown Editor
No Label
❓ Question
Milestone
No items
No Milestone
Projects
Clear projects
No project
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: starred/BookStack#1356
Reference in New Issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @Wookbert on GitHub (Sep 12, 2019).
Not exactly a feature request, but more a general request: Could you set up a forum/message board, where BookStack users can ask questions, help each other and discuss?
(For instance I'm just asking myself if there is a way to link a BookStack page in a text link on another BookStack page using the page ID, so the link doesn't break if the page title gets changed. Can't figure out how to accomplish that, not documented. Saw this one, but that’s for reusing the content, not the link to the content.
Edit: Just figured out that an internal page link somehow is always memorized under its URL in the moment when linked, regardless of a later page title change and thus URL change).
@ssddanbrown commented on GitHub (Sep 12, 2019):
Hi @Wookbert,
I'd rather not have an additional source of discussion via a forum since it gets hard to keep on top of these things.
The best alternative for open discussion would be the discord chat, Details here.
As you found, BookStack will attempt to resolve old URLs if a page has been renamed. There is some cases where this can fail so it's not 100%. It is possible to get a id-based link to a page via the popover that shows when you select some text:
This specifically references the selected section but you can just remove the hash, and all content afterwards, from the link to only reference the page.
@ssddanbrown commented on GitHub (Oct 9, 2019):
I'll go ahead and close this since the core question has been answered and there has been no further discussion.
@theAkito commented on GitHub (Mar 1, 2020):
@ssddanbrown
So there's no plans or at least the possibility for an actual forum? Discord is quite a horrible application, which I won't use, at all.
Pretty much every other open source project has a Discourse forum and maybe additionally a Discord or IRC or anything similar. Relying only on something like Discord sounds like a really bad idea not only because the platform itself is really bad but also because this type of community exchange and communication is far less result-oriented than an actual forum where you can actually find what someone has written a couple of months ago instead of getting lost in the history of inifinite chat... So it would pretty much save time in the long run to have an actual forum rather than having a chatting platform that, as already mentioned, is atrocious in the first place, not only because you don't have to repeat the same stuff over and over again. With a forum, you can easily find old conversations about a topic and save the time of both community members seeking help and members providing help. (That is just one of the biggest factors, there are many other reasons I can't go into detail about.)
@Wookbert commented on GitHub (Mar 1, 2020):
@theAkito
I assume that time/human resources is the biggest problem here. Setting up a forum is one thing, moderating it another. We need people here who are willing to come forward and spent time and energy on this. Unfortunately I'm already loaded with work.
@ssddanbrown commented on GitHub (Mar 1, 2020):
Yeah, @Wookbert is spot on here.
We already have the GitHub issues, the discord chat and a semi-official subreddit.
Discord acts as the informal, temporary discussion solution. The GitHub issue list is the more permanent, formal discussion solution. It'll be too much work at this time to monitor and maintain yet another community option.
GitHub are exploring the concept of discussions, I may look to enable that when available but the differences between that and issues would need to be clear, which I think will be tricky.