[Feature Request] Linking Articles #2413

Closed
opened 2026-02-05 04:02:02 +03:00 by OVERLORD · 2 comments
Owner

Originally created by @athornfam2 on GitHub (Oct 5, 2021).

Describe the feature you'd like
I was wondering if we could have a feature set to link articles to shelves based on permission. I say that because we have to keep, at this time, a repo for each purchase (IT, Internal, and Public). Unless, I'm missing a settings it can be cumbersome to maintain 3 different areas for users.

Describe the benefits this feature would bring to BookStack users
This would help internal teams maintain a single main repo of documents and then allow them to be linked rather than creating a whole new book, chapter, and page to replicate what's in the primary area where all docs are maintained.

Additional context
Add any other context or screenshots about the feature request here.

Originally created by @athornfam2 on GitHub (Oct 5, 2021). **Describe the feature you'd like** I was wondering if we could have a feature set to link articles to shelves based on permission. I say that because we have to keep, at this time, a repo for each purchase (IT, Internal, and Public). Unless, I'm missing a settings it can be cumbersome to maintain 3 different areas for users. **Describe the benefits this feature would bring to BookStack users** This would help internal teams maintain a single main repo of documents and then allow them to be linked rather than creating a whole new book, chapter, and page to replicate what's in the primary area where all docs are maintained. **Additional context** Add any other context or screenshots about the feature request here.
Author
Owner

@ssddanbrown commented on GitHub (Oct 5, 2021):

Hi @athornfam2,
I can't quite understand your actual use-case or request here. Could you explain it further just using BookStack terms? I don't understand what's exactly being referenced by the terms repo, purchase, areas, or articles.

@ssddanbrown commented on GitHub (Oct 5, 2021): Hi @athornfam2, I can't quite understand your actual use-case or request here. Could you explain it further just using BookStack terms? I don't understand what's exactly being referenced by the terms `repo`, `purchase`, `areas`, or `articles`.
Author
Owner

@ssddanbrown commented on GitHub (Oct 19, 2021):

Since there's been no follow-up I'm going to close this.

@ssddanbrown commented on GitHub (Oct 19, 2021): Since there's been no follow-up I'm going to close this.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/BookStack#2413