AppFlowy-IO/AppFlowy

Fork 0

mirror of https://github.com/AppFlowy-IO/AppFlowy.git synced 2026-03-24 04:46:56 +00:00

[GH-ISSUE #3899] [FR] support comment feature #1769

New issue

Open

opened 2026-03-23 21:16:56 +00:00 by mirror · 7 comments

mirror commented

2026-03-23 21:16:56 +00:00

Owner

Originally created by @f-kawamura on GitHub (Nov 8, 2023).
Original GitHub issue: https://github.com/AppFlowy-IO/AppFlowy/issues/3899

Description

Please implement the commenting feature as requested below.
https://forum.appflowy.io/t/fr-commenting/24/1

Add the ability for users to comment on text blocks.

Impact

The quality of documentation is extremely important in managing documents. If a document is managed by a team, it is natural to have the ability to comment on it.

I request the implementation of a commenting feature for frequent document review and flexible communication.

Additional Context

No response

Originally created by @f-kawamura on GitHub (Nov 8, 2023). Original GitHub issue: https://github.com/AppFlowy-IO/AppFlowy/issues/3899 ### Description Please implement the commenting feature as requested below. https://forum.appflowy.io/t/fr-commenting/24/1 Add the ability for users to comment on text blocks. ### Impact The quality of documentation is extremely important in managing documents. If a document is managed by a team, it is natural to have the ability to comment on it. I request the implementation of a commenting feature for frequent document review and flexible communication. ### Additional Context _No response_

mirror added the

labels

2026-03-23 21:16:56 +00:00

mirror commented

2026-03-23 21:16:57 +00:00

Author

Owner

@jpenna commented on GitHub (Jan 16, 2024):

I'd like to add up some nice features comments could have that are overlooked by other editing tools.

1. Full-featured comments. This means one can add images, bold/italic/underline, font color... But also that other people can highlight a section of the comment and even comment the comment. "Commenting comments" isn't just posting to the thread, but selecting a section of the comment and starting a new thread. This isn't straightforward as it seems if we want a good UX. I have some ideas for how this feature should work if you want to hear.
2. Semantic comments. Is this comment a question? Is it a suggestion? Is it adding more information to the highlighted argument? Having this data, a user can see a ? when it is a question, ! for pointing out errors, + for more information on the topic... This makes it easier to navigate the comments when there are many and to make sense of them. Again, it is worth discussing the UX. (I think the same idea of semantics should be used for highlights as well, so "green" have a meaning and "yellow" another one...)
3. Support for audio + transcript. This is a later addition, specially for when this is working on smartphones.

@jpenna commented on GitHub (Jan 16, 2024): I'd like to add up some nice features comments could have that are overlooked by other editing tools. **1. Full-featured comments.** This means one can add images, bold/italic/underline, font color... But also that other people can highlight a section of the comment and even comment the comment. "Commenting comments" isn't just posting to the thread, but selecting a section of the comment and starting a new thread. This isn't straightforward as it seems if we want a good UX. I have some ideas for how this feature should work if you want to hear. **2. Semantic comments.** Is this comment a question? Is it a suggestion? Is it adding more information to the highlighted argument? Having this data, a user can see a `?` when it is a question, `!` for pointing out errors, `+` for more information on the topic... This makes it easier to navigate the comments when there are many and to make sense of them. Again, it is worth discussing the UX. (I think the same idea of semantics should be used for highlights as well, so "green" have a meaning and "yellow" another one...) **3. Support for audio + transcript.** This is a later addition, specially for when this is working on smartphones.

mirror commented

2026-03-23 21:16:58 +00:00

Author

Owner

@almereyda commented on GitHub (Feb 8, 2025):

After trying to provide line comments, I was surprised to find they do not exist.

There are comments now on published pages. Surprisingly, these are not visible near the origin document itself. Maybe something is coming?

@almereyda commented on GitHub (Feb 8, 2025): After trying to provide line comments, I was surprised to find they do not exist. There are comments now on published pages. Surprisingly, these are not visible near the origin document itself. Maybe something is coming?

mirror commented

2026-03-23 21:16:58 +00:00

Author

Owner

@khorshuheng commented on GitHub (Feb 9, 2025):

Comments on published page have existed for quite some time, and is basically a simple CRUD rest API to add and remove comments.

Comments on documents, though, might be more involved, as we may need to consider real time updates. It is planned, though not coming that soon.

@khorshuheng commented on GitHub (Feb 9, 2025): Comments on published page have existed for quite some time, and is basically a simple CRUD rest API to add and remove comments. Comments on documents, though, might be more involved, as we may need to consider real time updates. It is planned, though not coming that soon.

mirror commented

2026-03-23 21:16:58 +00:00

Author

Owner

@almereyda commented on GitHub (Feb 9, 2025):

Please note that coming from the experience in the Outline community, people will quickly raise this to inline comments on annotated parts of the text, from which will also come a requirement to implement review workflows for merging different forks/branches of a document, which is a completely different issue, but for which annotated discussions will be used.

@almereyda commented on GitHub (Feb 9, 2025): Please note that coming from the experience in the Outline community, people will quickly raise this to inline comments on annotated parts of the text, from which will also come a requirement to implement review workflows for merging different forks/branches of a document, which is a completely different issue, but for which annotated discussions will be used.

mirror commented

2026-03-23 21:16:58 +00:00

Author

Owner

@bennidhamma commented on GitHub (Mar 6, 2025):

+1 - loving AppFlowy so far, ambitious project.

Comments in Google docs, quip, notion are table stakes for teams.

Hard to understate the impact they have to collaboration. Truly can transform AppFlowy into killer app territory.

(I'm sure it's not an easy lift. But I wanted to impress the power / value of this further)

@bennidhamma commented on GitHub (Mar 6, 2025): +1 - loving AppFlowy so far, ambitious project. Comments in Google docs, quip, notion are table stakes for teams. Hard to understate the impact they have to collaboration. Truly can transform AppFlowy into killer app territory. (I'm sure it's not an easy lift. But I wanted to impress the power / value of this further)

mirror commented

2026-03-23 21:16:59 +00:00

Author

Owner

@CodeShakingSheep commented on GitHub (Apr 16, 2025):

Much needed feature from my side as well. Love AppFlowy 😍

@CodeShakingSheep commented on GitHub (Apr 16, 2025): Much needed feature from my side as well. Love AppFlowy 😍

mirror commented

2026-03-23 21:16:59 +00:00

Author

Owner

@annieappflowy commented on GitHub (May 30, 2025):

Being able to comment on tasks, we used to make quick comments on tasks
https://discord.com/channels/903549834160635914/903553722804748309/1377283256742973630

@annieappflowy commented on GitHub (May 30, 2025): Being able to comment on tasks, we used to make quick comments on tasks https://discord.com/channels/903549834160635914/903553722804748309/1377283256742973630