Inline commenting #1031

New Issue

OVERLORD · 2026-02-04T23:28:55+03:00

OVERLORD commented

2026-02-04 23:28:55 +03:00

Originally created by @abbeyjackson on GitHub (Feb 7, 2019).

This is a suggestion added to issues as per Dan’s instructions via Twitter.

Inline commenting (selecting a chubk of text to comment on or having a comment associated with a specific line number) is a feature that is missing from Bookstack which I feel would really add value to the product.

Originally created by @abbeyjackson on GitHub (Feb 7, 2019). This is a suggestion added to issues as per Dan’s instructions via Twitter. Inline commenting (selecting a chubk of text to comment on or having a comment associated with a specific line number) is a feature that is missing from Bookstack which I feel would really add value to the product.

OVERLORD added the 🔨 Feature Request 💻 Front-End labels 2026-02-04 23:28:55 +03:00

OVERLORD closed this issue

2026-02-04 23:28:57 +03:00

OVERLORD commented

2026-02-04 23:29:01 +03:00

@JohnnyWild89 commented on GitHub (May 18, 2020):

Looking forward to get this feature! Bookshelf is perfect replacement for any products which use as WIKI. Inline commentaries would greatly expands work possibilities.

@JohnnyWild89 commented on GitHub (May 18, 2020): Looking forward to get this feature! Bookshelf is perfect replacement for any products which use as WIKI. Inline commentaries would greatly expands work possibilities.

OVERLORD commented

2026-02-04 23:29:07 +03:00

@cze-karel commented on GitHub (Jan 6, 2021):

This would be a really great feature that would improve the possibility of people collaborating on the documents. Is it possible this feature will make it into the roadmap?

@cze-karel commented on GitHub (Jan 6, 2021): This would be a really great feature that would improve the possibility of people collaborating on the documents. Is it possible this feature will make it into the roadmap?

OVERLORD commented

2026-02-04 23:29:11 +03:00

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

Further request and ideas proposed within #3063

@ssddanbrown commented on GitHub (Nov 19, 2021): Further request and ideas proposed within #3063

OVERLORD commented

2026-02-04 23:29:16 +03:00

@TiemeWoldman commented on GitHub (Jul 7, 2022):

Any plans on adding annotations (Inline comments) to BookStack? This would be a great addition.

I tried hypothes.is for adding annotations to BookStack pages, but the BookStack text select pop-up interferes with hypothes.

@TiemeWoldman commented on GitHub (Jul 7, 2022): Any plans on adding annotations (Inline comments) to BookStack? This would be a great addition. I tried [hypothes.is](https://hypothes.is/) for adding annotations to BookStack pages, but the BookStack text select pop-up interferes with hypothes.

OVERLORD commented

2026-02-04 23:29:18 +03:00

@EDMJohnny commented on GitHub (Aug 15, 2022):

As far as I can tell BookStack is pretty close to perfect for a writing / collaboration platform. Super simple to use, very intuitive. Inline comments would make it perfect! Is this something you are working on or have an ETA for?
Thanks

@EDMJohnny commented on GitHub (Aug 15, 2022): As far as I can tell BookStack is pretty close to perfect for a writing / collaboration platform. Super simple to use, very intuitive. Inline comments would make it perfect! Is this something you are working on or have an ETA for? Thanks

OVERLORD commented

2026-02-04 23:29:19 +03:00

@ssddanbrown commented on GitHub (Aug 15, 2022):

@EDMJohnny

Is this something you are working on or have an ETA for?

Not at this time.

@ssddanbrown commented on GitHub (Aug 15, 2022): @EDMJohnny > Is this something you are working on or have an ETA for? Not at this time.

OVERLORD commented

2026-02-04 23:29:21 +03:00

@EDMJohnny commented on GitHub (Aug 15, 2022):

Thanks for responding. Is this something you'd be willing to put a bounty on / get paid for completing? Do you have a ballpark for cost of adding this feature?

@EDMJohnny commented on GitHub (Aug 15, 2022): Thanks for responding. Is this something you'd be willing to put a bounty on / get paid for completing? Do you have a ballpark for cost of adding this feature?

OVERLORD commented

2026-02-04 23:29:23 +03:00

@ssddanbrown commented on GitHub (Aug 16, 2022):

@EDMJohnny I'm not really a fan of public bounties, can just cause issues. Not really sure on ballpark costs either as this would need fleshing out into a full proposal since this request could be imagined/desired in different forms.

I've quoted features before (although never accepted) but only for features with clear scope and platform fit. Something makes me uneasy about rushing through a proposal for the sake of money, feel that risks providing an unbalanced larger voice to those with money, not sure the right way to balance that. If I was to quote it'd be somewhere upwards of £1k, even for a minimal implementation.

@ssddanbrown commented on GitHub (Aug 16, 2022): @EDMJohnny I'm not really a fan of public bounties, can just cause issues. Not really sure on ballpark costs either as this would need fleshing out into a full proposal since this request could be imagined/desired in different forms. I've quoted features before (although never accepted) but only for features with clear scope and platform fit. Something makes me uneasy about rushing through a proposal for the sake of money, feel that risks providing an unbalanced larger voice to those with money, not sure the right way to balance that. If I was to quote it'd be somewhere upwards of £1k, even for a minimal implementation.

OVERLORD commented

2026-02-04 23:29:27 +03:00

@danhansen commented on GitHub (Aug 26, 2022):

Why not integrate something like https://github.com/recogito/recogito-js ? It looks like a significant portion of the functionality is already implemented.

@danhansen commented on GitHub (Aug 26, 2022): Why not integrate something like https://github.com/recogito/recogito-js ? It looks like a significant portion of the functionality is already implemented.

OVERLORD commented

2026-02-04 23:29:32 +03:00

@BloodyIron commented on GitHub (Sep 30, 2022):

@ssddanbrown can we please have this added to a roadmap in some regard? As you may remember seeing me elsewhere, likely to switch to Bookstack, and some of our staff use this kind of feature in Confuence (which we are moving away from).

Is there a hurdle on your end for this?

@BloodyIron commented on GitHub (Sep 30, 2022): @ssddanbrown can we please have this added to a roadmap in some regard? As you may remember seeing me elsewhere, likely to switch to Bookstack, and some of our staff use this kind of feature in Confuence (which we are moving away from). Is there a hurdle on your end for this?

OVERLORD commented

2026-02-04 23:29:38 +03:00

@ssddanbrown commented on GitHub (Sep 30, 2022):

Is there a hurdle on your end for this?

Uh, I guess it's some level of formula of:

PRESSURE = ("user actual benefit" + "user demand" + "my own enthusiasm level for the feature")
DRAG = ("implementation cost" + "my predicated cost of maintenance, inc. support")
HURDLE = ((PRESSURE - DRAG) * "my current emotions" * RANDOM_CHANCE())

That's probably the best I can explain it, same for any feature tbh.
Roadmap is reserved for high-level elements. Could maybe have some kind of "Commenting and Communications" item. Not sure though, might want to address other things before.

Realistically, the next step for this specific request would be for me to put forward an implementation proposal, with a scope that I'd be happy to maintain, for community feedback. No reason to rush though IMO.

@ssddanbrown commented on GitHub (Sep 30, 2022): > Is there a hurdle on your end for this? Uh, I guess it's some level of formula of: ``` PRESSURE = ("user actual benefit" + "user demand" + "my own enthusiasm level for the feature") DRAG = ("implementation cost" + "my predicated cost of maintenance, inc. support") HURDLE = ((PRESSURE - DRAG) * "my current emotions" * RANDOM_CHANCE()) ``` That's probably the best I can explain it, same for any feature tbh. Roadmap is reserved for high-level elements. Could maybe have some kind of "Commenting and Communications" item. Not sure though, might want to address other things before. Realistically, the next step for this specific request would be for me to put forward an implementation proposal, with a scope that I'd be happy to maintain, for community feedback. No reason to rush though IMO.

OVERLORD commented

2026-02-04 23:29:44 +03:00

@ironbelly commented on GitHub (Nov 7, 2022):

Agreed with EDMJohnny above that inline comments to facilitate more specific conversation amongst collaborators is one of the biggest items of value that could be added.

Also inline with EDMJohnny about the bounty, would be happy to chip in

@ironbelly commented on GitHub (Nov 7, 2022): Agreed with EDMJohnny above that inline comments to facilitate more specific conversation amongst collaborators is one of the biggest items of value that could be added. Also inline with EDMJohnny about the bounty, would be happy to chip in

OVERLORD commented

2026-02-04 23:29:46 +03:00

@EDMJohnny commented on GitHub (Mar 2, 2023):

@ssddanbrown Hi - just checking in again. I see you've done a lot of updates on Bookstack since I last checked it. All much appreciated. Any chance of bumping this feature request for inline comments on to your To Do?

@EDMJohnny commented on GitHub (Mar 2, 2023): @ssddanbrown Hi - just checking in again. I see you've done a lot of updates on Bookstack since I last checked it. All much appreciated. Any chance of bumping this feature request for inline comments on to your To Do?

OVERLORD commented

2026-02-04 23:29:50 +03:00

@ipimpat commented on GitHub (Mar 27, 2023):

This would be a killer feature !

@ipimpat commented on GitHub (Mar 27, 2023): This would be a killer feature !

OVERLORD commented

2026-02-04 23:29:52 +03:00

@rosequaartz commented on GitHub (Apr 27, 2023):

This feature would be great! :)

@rosequaartz commented on GitHub (Apr 27, 2023): This feature would be great! :)

OVERLORD commented

2026-02-04 23:29:55 +03:00

@shashankvivek commented on GitHub (May 7, 2023):

Yeah, with this feature, bookstack can knock the ball out of the park !

@shashankvivek commented on GitHub (May 7, 2023): Yeah, with this feature, bookstack can knock the ball out of the park !

OVERLORD commented

2026-02-04 23:29:57 +03:00

@stevenvegt commented on GitHub (Feb 1, 2024):

I stumbled on this issue and wanted to chip in. We use bookstack for our open source community. People are working together on projects and keep reverting to google docs. Inline comments are the missing key in bookstack and holding them back to make the switch. I hope this will add some weight to the "user actual benefit" + "user demand" parts of the equation. Either way, thanks for this nice piece of software!

@stevenvegt commented on GitHub (Feb 1, 2024): I stumbled on this issue and wanted to chip in. We use bookstack for our open source community. People are working together on projects and keep reverting to google docs. Inline comments are the missing key in bookstack and holding them back to make the switch. I hope this will add some weight to the` "user actual benefit" + "user demand"` parts of the equation. Either way, thanks for this nice piece of software!

OVERLORD commented

2026-02-04 23:30:02 +03:00

@dtufood-kihen commented on GitHub (Apr 16, 2024):

Just dropping by to say I've been keeping an eye on the chat about inline comments. I get that developers have to juggle a bunch of stuff and can't just jump on every new idea, but I can't help feeling pretty stoked about this particular feature.

Please make it happen ! :-)

@dtufood-kihen commented on GitHub (Apr 16, 2024): Just dropping by to say I've been keeping an eye on the chat about inline comments. I get that developers have to juggle a bunch of stuff and can't just jump on every new idea, but I can't help feeling pretty stoked about this particular feature. Please make it happen ! :-)

OVERLORD commented

2026-02-04 23:30:05 +03:00

@khudari-starpath commented on GitHub (May 4, 2024):

+1 would switch to bookstack if it had this feature!

@khudari-starpath commented on GitHub (May 4, 2024): +1 would switch to bookstack if it had this feature!

OVERLORD commented

2026-02-04 23:30:08 +03:00

@agapoar commented on GitHub (Jun 20, 2024):

Hi. I would also love to see this feature added. By way of suggestion, I expected to see the ability to add an inline comment when I double clicked on a word in the text in read mode. I did see a popup menu, which was great. But obviously it didn't contain the ability to annotate. This screenshot shows the menu.

@agapoar commented on GitHub (Jun 20, 2024): Hi. I would also love to see this feature added. By way of suggestion, I expected to see the ability to add an inline comment when I double clicked on a word in the text in read mode. I did see a popup menu, which was great. But obviously it didn't contain the ability to annotate. This screenshot shows the menu. ![image](https://github.com/BookStackApp/BookStack/assets/166620720/837f59f5-ed58-46dc-9ba5-6a2d50264a21)

OVERLORD commented

2026-02-04 23:30:11 +03:00

@ipimpat commented on GitHub (Jun 20, 2024):

Hi @ssddanbrown,

First, I want to express my gratitude for the incredible work.

I was wondering if you might consider adding the annotation feature to the roadmap. The demand for this feature seems quite high among users.

Currently, the absence of this feature is the main reason my team continues to rely on Word files. They are hesitant to transition to tools that lack annotation capabilities.

Thank you so much for considering this request, and for all the amazing work you continue to do.

@ipimpat commented on GitHub (Jun 20, 2024): Hi @ssddanbrown, First, I want to express my gratitude for the incredible work. I was wondering if you might consider adding the annotation feature to the roadmap. The demand for this feature seems quite high among users. Currently, the absence of this feature is the main reason my team continues to rely on Word files. They are hesitant to transition to tools that lack annotation capabilities. Thank you so much for considering this request, and for all the amazing work you continue to do.

OVERLORD commented

2026-02-04 23:30:14 +03:00

@bendem commented on GitHub (Jun 25, 2024):

The demand for this feature seems quite high among users.

If you look at the most requested feature, it has >100 👍🏻. This one has 25.

Reminder that adding a 👍🏻 on the top post is the way to vote for an issue, pressuring/guilting the developer is not the way to get the feature you want added in.

@bendem commented on GitHub (Jun 25, 2024): > The demand for this feature seems quite high among users. If you look at the most requested feature, it has >100 👍🏻. This one has 25. Reminder that adding a 👍🏻 on the top post is the way to vote for an issue, pressuring/guilting the developer is not the way to get the feature you want added in. ![image](https://github.com/BookStackApp/BookStack/assets/2681677/4b5d3017-93af-4826-ac65-df1d0e5c4003)

OVERLORD commented

2026-02-04 23:30:18 +03:00

@grv688 commented on GitHub (Aug 1, 2024):

Also very interested in this. We're migrating from documents that allowed inline commenting during revision cycles, and it was very useful.

@grv688 commented on GitHub (Aug 1, 2024): Also very interested in this. We're migrating from documents that allowed inline commenting during revision cycles, and it was very useful.

OVERLORD commented

2026-02-04 23:30:24 +03:00

@pato-lama commented on GitHub (Aug 22, 2024):

Tossing a comment in here to support this request - would love having this functionality!

@pato-lama commented on GitHub (Aug 22, 2024): Tossing a comment in here to support this request - would love having this functionality!

OVERLORD commented

2026-02-04 23:30:27 +03:00

@ahnchive commented on GitHub (Sep 23, 2024):

Also very interested in this!

@ahnchive commented on GitHub (Sep 23, 2024): Also very interested in this!

OVERLORD commented

2026-02-04 23:30:30 +03:00

@Yarrax commented on GitHub (Dec 25, 2024):

Also very interested in this!

@Yarrax commented on GitHub (Dec 25, 2024): Also very interested in this!

OVERLORD commented

2026-02-04 23:30:36 +03:00

@Yarrax commented on GitHub (Feb 18, 2025):

Hmmm... I'm sorry, but this feature is looks like most wanted:

Of course, it haven't >100 thumbs up, but... :)

@Yarrax commented on GitHub (Feb 18, 2025): Hmmm... I'm sorry, but this feature is looks like most wanted: ![Image](https://github.com/user-attachments/assets/ce26bccb-aae9-4e3f-aef7-3672b3e39931) Of course, it haven't >100 thumbs up, but... :)

OVERLORD commented

2026-02-04 23:30:37 +03:00

@sjimellor-jr commented on GitHub (Feb 18, 2025):

Is Hypothes.is (https://web.hypothes.is/) an option? It can already be used to privately annotate Bookstack pages with an account and browser extension. Perhaps with a self-hosted "h" server (https://github.com/hypothesis/h) and using the JS client (https://github.com/hypothesis/client) configured to use the self-hosted server then this could be more native. I've not tried to host my own "h" server.

@sjimellor-jr commented on GitHub (Feb 18, 2025): Is Hypothes.is (https://web.hypothes.is/) an option? It can already be used to privately annotate Bookstack pages with an account and browser extension. Perhaps with a self-hosted "h" server (https://github.com/hypothesis/h) and using the JS client (https://github.com/hypothesis/client) configured to use the self-hosted server then this could be more native. I've not tried to host my own "h" server.

OVERLORD commented

2026-02-04 23:30:39 +03:00

@Yarrax commented on GitHub (Feb 19, 2025):

Is Hypothes.is (https://web.hypothes.is/) an option?

Hmm... may be, thanks i'll try it. but anyway it will be a one more service for manual install. It will be great if bookstack will have inline commenting onboard

@Yarrax commented on GitHub (Feb 19, 2025): > Is Hypothes.is (https://web.hypothes.is/) an option? Hmm... may be, thanks i'll try it. but anyway it will be a one more service for manual install. It will be great if bookstack will have inline commenting onboard

OVERLORD commented

2026-02-04 23:30:46 +03:00

@ssddanbrown commented on GitHub (May 22, 2025):

I've now added an initial implementation for in-content comments via PR #5584.
This is due to be part of the next feature release.
Therefore I'm going to close this off. Further related requests, or issues upon the implementation, can be raised in future requests if needed (once there's been opportunity to test after the next feature release).

This implementation is (relatively) minimal so may have some limitations in the view of some, but otherwise it should achieve the general functional goals for most. This implementation includes:

Ability to start a content-connected comment thread from the content popover when viewing a page.
The comment references a specific block of content, along with an optional text range within that to highlight a range of text.
Comment threads will show as highlighted ranges when viewing a page (as long as the referenced sections exist).
- You can click the comment icon within a highlight range to open up the comment thread inline.
- There's a button to jump to the full thread for interaction (reply, edit, delete etc...).
Comments will also show inline within the new (in-alpha) WYSIWYG editor when the comments sidebar is opened in the editor view.
To support this functionality, I've also added the ability to archive (and unarchive) comments, so that these kind of comments can be treated as a kind of todo-list, and archived when addressed.
- Active/Archived threads are listed under separate tabs.
- Inline comments will only be shown for the active comments tab.
Comments are marked if they have a reference.
- This can be clicked to jump the the referenced section.
- This will update to show as outdated if the reference section has changed.
  - This is based upon a hash of the text for that block section.
- This will turn orange if the section no longer exists at all.
- This will be gray in scenarios where we can't provide an interactive link or check the reference (in MD/old-wyswiyg editors)

Limitations

Only the top-level comment in a thread can include a reference (and also be archived/unarchived).
Only the new WYSIWYG editor receives inline support.
The inline comments are not interactive (no reply or other controls) but they do have the ability to jump to the full comment.
There's no display options/controls for these comments. Could be something that's needed but I thought we'd get the feature out there first to understand what level of control is actually needed (if at all).
The outdated/change detection is currently done browser-side, and is done block level (not just the text range if set).
- I've tried to do this in a way we should be able to replicate on the PHP side if needed in the future.

Screenshots

Inline Display

Inline Display - Opened

Page View Comments List

In Editor

@ssddanbrown commented on GitHub (May 22, 2025): I've now added an initial implementation for in-content comments via PR #5584. This is due to be part of the next feature release. Therefore I'm going to close this off. Further related requests, or issues upon the implementation, can be raised in future requests if needed (once there's been opportunity to test after the next feature release). This implementation is (relatively) minimal so may have some limitations in the view of some, but otherwise it should achieve the general functional goals for most. This implementation includes: - Ability to start a content-connected comment thread from the content popover when viewing a page. - The comment references a specific block of content, along with an optional text range within that to highlight a range of text. - Comment threads will show as highlighted ranges when viewing a page (as long as the referenced sections exist). - You can click the comment icon within a highlight range to open up the comment thread inline. - There's a button to jump to the full thread for interaction (reply, edit, delete etc...). - Comments will also show inline within the new (in-alpha) WYSIWYG editor when the comments sidebar is opened in the editor view. - To support this functionality, I've also added the ability to archive (and unarchive) comments, so that these kind of comments can be treated as a kind of todo-list, and archived when addressed. - Active/Archived threads are listed under separate tabs. - Inline comments will only be shown for the active comments tab. - Comments are marked if they have a reference. - This can be clicked to jump the the referenced section. - This will update to show as outdated if the reference section has changed. - This is based upon a hash of the text for that block section. - This will turn orange if the section no longer exists at all. - This will be gray in scenarios where we can't provide an interactive link or check the reference (in MD/old-wyswiyg editors) **Limitations** - Only the top-level comment in a thread can include a reference (and also be archived/unarchived). - Only the new WYSIWYG editor receives inline support. - The inline comments are not interactive (no reply or other controls) but they do have the ability to jump to the full comment. - There's no display options/controls for these comments. Could be something that's needed but I thought we'd get the feature out there first to understand what level of control is actually needed (if at all). - The outdated/change detection is currently done browser-side, and is done block level (not just the text range if set). - I've tried to do this in a way we should be able to replicate on the PHP side if needed in the future. ### Screenshots <details><summary>Inline Display</summary> ![Image](https://github.com/user-attachments/assets/f1bb78dc-f636-4a10-a081-9b346ce5c30f) </details> <details><summary>Inline Display - Opened</summary> ![Image](https://github.com/user-attachments/assets/e6778242-588c-4a8b-ad76-3dd9a95fb4bb) </details> <details><summary>Page View Comments List</summary> ![Image](https://github.com/user-attachments/assets/7b2c0945-53a8-44a1-b611-d3e359e0a9d4) </details> <details><summary>In Editor</summary> ![Image](https://github.com/user-attachments/assets/528d4697-d249-48b9-8613-242a765258a2) </details>

OVERLORD commented

2026-02-04 23:30:51 +03:00

@pabalven commented on GitHub (Nov 14, 2025):

Thank you so much @ssddanbrown for releasing this. I just saw that in the demo site. Great implementation, and so useful!

Thanks, thanks, thanks!!!

@pabalven commented on GitHub (Nov 14, 2025): Thank you so much @ssddanbrown for releasing this. I just saw that in the demo site. Great implementation, and so useful! Thanks, thanks, thanks!!!

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: starred/BookStack#1031