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 #5912] [FR] Tags #2627

New issue

Open

opened 2026-03-23 21:23:53 +00:00 by mirror · 10 comments

mirror commented

2026-03-23 21:23:53 +00:00

Owner

Originally created by @adnan-usman on GitHub (Aug 9, 2024).
Original GitHub issue: https://github.com/AppFlowy-IO/AppFlowy/issues/5912

Description

It will be graet if there is a tag system to add docs in specific tag etc

Impact

All type of Users

Additional Context

No response

Originally created by @adnan-usman on GitHub (Aug 9, 2024). Original GitHub issue: https://github.com/AppFlowy-IO/AppFlowy/issues/5912 ### Description It will be graet if there is a tag system to add docs in specific tag etc ### Impact All type of Users ### Additional Context _No response_

mirror added the

organization

2026

labels

2026-03-23 21:23:53 +00:00

mirror commented

2026-03-23 21:23:53 +00:00

Author

Owner

@Xazin commented on GitHub (Aug 9, 2024):

I wonder how you would use the tags?

I can imagine it would be quite easy to add tags to a Document (view) as a new optional attribute, but I'm not sure what features would have to follow to accommodate this new attribute to make it worthwhile?

@Xazin commented on GitHub (Aug 9, 2024): I wonder how you would use the tags? I can imagine it would be quite easy to add tags to a Document (view) as a new optional attribute, but I'm not sure what features would have to follow to accommodate this new attribute to make it worthwhile?

mirror commented

2026-03-23 21:23:53 +00:00

Author

Owner

@adnan-usman commented on GitHub (Aug 12, 2024):

This is How tags can help us -

Improved Organization: Tags allow for flexible categorization beyond
traditional folders.
Enhanced Searchability: Quickly find documents by filtering or
searching with tags.
User-Friendly: Tags offer intuitive ways to group related content.
Efficient Management: Bulk tagging and tag suggestions streamline
document handling.
Better Insights: Tag analytics provide valuable data on content
trends.
Increased Flexibility: Tags can complement or replace folders,
offering more ways to organize.

On Fri, 9 Aug 2024 at 20:35, Mathias Mogensen @.***>
wrote:

I wonder how you would use the tags?

I can imagine it would be quite easy to add tags to a Document (view) as a
new optional attribute, but I'm not sure what features would have to
accommodate this new attribute to make it worthwhile?

—
Reply to this email directly, view it on GitHub
https://github.com/AppFlowy-IO/AppFlowy/issues/5912#issuecomment-2278221684,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AZAT3S4M4VXLF7ZC22LYVNTZQTOVBAVCNFSM6AAAAABMIMDEHCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENZYGIZDCNRYGQ
.
You are receiving this because you authored the thread.Message ID:
@.***>

@adnan-usman commented on GitHub (Aug 12, 2024): This is How tags can help us - 1. **Improved Organization:** Tags allow for flexible categorization beyond traditional folders. 2. **Enhanced Searchability:** Quickly find documents by filtering or searching with tags. 3. **User-Friendly:** Tags offer intuitive ways to group related content. 4. **Efficient Management:** Bulk tagging and tag suggestions streamline document handling. 5. **Better Insights:** Tag analytics provide valuable data on content trends. 6. **Increased Flexibility:** Tags can complement or replace folders, offering more ways to organize. On Fri, 9 Aug 2024 at 20:35, Mathias Mogensen ***@***.***> wrote: > I wonder how you would use the tags? > > I can imagine it would be quite easy to add tags to a Document (view) as a > new optional attribute, but I'm not sure what features would have to > accommodate this new attribute to make it worthwhile? > > — > Reply to this email directly, view it on GitHub > <https://github.com/AppFlowy-IO/AppFlowy/issues/5912#issuecomment-2278221684>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AZAT3S4M4VXLF7ZC22LYVNTZQTOVBAVCNFSM6AAAAABMIMDEHCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENZYGIZDCNRYGQ> > . > You are receiving this because you authored the thread.Message ID: > ***@***.***> >

mirror commented

2026-03-23 21:23:54 +00:00

Author

Owner

@Xazin commented on GitHub (Aug 13, 2024):

The benefits are too generalized, I was asking for actual features that would follow "tags" so that it would be easier to point out whether it'd be worthwhile to implement.

Eg. Do we need to be able to search for documents by one or more tags? Are tags for a document managed per space (eg. Shared, Private), or one list of available Tags per Workspace, and so forth.

Adding a tag to a document achieves nothing by itself, there most likely needs to be some other features as well, my question was what features do you think would be needed along with adding tags to documents, to make it a worthwhile?

@Xazin commented on GitHub (Aug 13, 2024): The benefits are too generalized, I was asking for actual features that would follow "tags" so that it would be easier to point out whether it'd be worthwhile to implement. Eg. Do we need to be able to search for documents by one or more tags? Are tags for a document managed per space (eg. Shared, Private), or one list of available Tags per Workspace, and so forth. Adding a tag to a document achieves nothing by itself, there most likely needs to be some other features as well, my question was what features do you think would be needed along with adding tags to documents, to make it a worthwhile?

mirror commented

2026-03-23 21:23:54 +00:00

Author

Owner

@zetashift commented on GitHub (Aug 13, 2024):

Adding a tag to a document achieves nothing by itself

I agree with this, however one can already add tags through the calendar:

So there is one form of it already available, I think it's worth it to give a bit more oomph to it:

The usecase is here is, to have more fine-grained categorization than folders/pages.
Say I have a big note:

# Work Log
...stuff...

[[2024-01-01]] Discussed plan A during #meeting

Now I could potentially filter blocks through meeting if I want to check some meetings stuff.

There is a way to do it already if your meeting tag would be a link to a page instead of a tag. LogSeq does this, it treats pages/docs the same as tags.
I think it's worth discussing if AppFlowy could do the same. You'll treat a tag as a doc, but visually #tag still remains with some special coloring.

This way you can even add information to the tag/doc itself!
The search rules would then apply the same rules as a doc, but maybe with a different indicator.

It would make linking data in a database/calendar/kanban with docs, that much easier to find. Because in the end tagging things is a great way to quickly re-discover old content.

I do want to note, these benefits mostly come when working mostly on your personal knowledge base. The advantages are less effective in the context of teams working on docs, because well, they probably don't know all the tags or they just want to write rather than organize.

@zetashift commented on GitHub (Aug 13, 2024): > Adding a tag to a document achieves nothing by itself I agree with this, however one can already add tags through the calendar: ![image](https://github.com/user-attachments/assets/bdce6904-65f6-40e6-8eda-5c80bd9ca1f2) So there is one form of it already available, I think it's worth it to give a bit more oomph to it: The usecase is here is, to have more fine-grained categorization than folders/pages. Say I have a big note: ``` # Work Log ...stuff... [[2024-01-01]] Discussed plan A during #meeting ``` Now I could potentially filter blocks through `meeting` if I want to check some meetings stuff. There is a way to do it already if your `meeting` tag would be a link to a page instead of a tag. LogSeq does this, it treats pages/docs the same as tags. I think it's worth discussing if AppFlowy could do the same. You'll treat a tag as a doc, but visually `#tag` still remains with some special coloring. This way you can even add information to the tag/doc itself! The search rules would then apply the same rules as a doc, but maybe with a different indicator. It would make linking data in a database/calendar/kanban with docs, that much easier to find. Because in the end tagging things is a great way to quickly re-discover old content. I do want to note, these benefits mostly come when working mostly on your personal knowledge base. The advantages are less effective in the context of teams working on docs, because well, they probably don't know all the tags or they just want to write rather than organize.

mirror commented

2026-03-23 21:23:54 +00:00

Author

Owner

@CeJienAJPC commented on GitHub (Dec 2, 2024):

The benefits are too generalized, I was asking for actual features that would follow "tags" so that it would be easier to point out whether it'd be worthwhile to implement.

Eg. Do we need to be able to search for documents by one or more tags? Are tags for a document managed per space (eg. Shared, Private), or one list of available Tags per Workspace, and so forth.

Adding a tag to a document achieves nothing by itself, there most likely needs to be some other features as well, my question was what features do you think would be needed along with adding tags to documents, to make it a worthwhile?

The Need for Tags

When there are 100+ documents, it would be easier & faster to search by Tags (unless one remembers the file name).
Tags can help in building a Graph View (like used in Obsidian, Logseq) if Appflowy plans one in the future (highly recommended).
Tags can make the search for a file easier across Spaces.
Tags can be used to look for Documents sharing similar/same Tags.
Tags when used inside the Document (say a specific para), can be used to reference this specific section inside the Document and all the referenced sections from multiple Documents can be viewed.

Hence, using Tags is highly recommended and organises the entire data over time, as it grows. I hope this answers your question. Regards

@CeJienAJPC commented on GitHub (Dec 2, 2024): > The benefits are too generalized, I was asking for actual features that would follow "tags" so that it would be easier to point out whether it'd be worthwhile to implement. > > Eg. Do we need to be able to search for documents by one or more tags? Are tags for a document managed per space (eg. Shared, Private), or one list of available Tags per Workspace, and so forth. > > Adding a tag to a document achieves nothing by itself, there most likely needs to be some other features as well, my question was what features do you think would be needed along with adding tags to documents, to make it a worthwhile? **The Need for Tags** - When there are 100+ documents, it would be easier & faster to search by Tags (unless one remembers the file name). - Tags can help in building a Graph View (like used in Obsidian, Logseq) if Appflowy plans one in the future (highly recommended). - Tags can make the search for a file easier across Spaces. - Tags can be used to look for Documents sharing similar/same Tags. - Tags when used inside the Document (say a specific para), can be used to reference this specific section inside the Document and all the referenced sections from multiple Documents can be viewed. Hence, using Tags is highly recommended and organises the entire data over time, as it grows. I hope this answers your question. Regards

mirror commented

2026-03-23 21:23:54 +00:00

Author

Owner

@poelzi commented on GitHub (Mar 17, 2025):

This is what logseq is known for and what is definitive missing. Writing '#tag' should automatically generate a tag, pages should have tags.
Tag pages should collect all backlinks and allow customization on the upper part. Without tags, the whole note taking becomes useless, since cross linking is a burden.
I can't understand why this is missing.

@poelzi commented on GitHub (Mar 17, 2025): This is what logseq is known for and what is definitive missing. Writing '#tag' should automatically generate a tag, pages should have tags. Tag pages should collect all backlinks and allow customization on the upper part. Without tags, the whole note taking becomes useless, since cross linking is a burden. I can't understand why this is missing.

mirror commented

2026-03-23 21:23:54 +00:00

Author

Owner

@laurensalmekinders commented on GitHub (Jul 15, 2025):

I really dig AppFlowy, and would love to migrate and enhance possibilities but the lack of tags is unfortunately a massive showstopper for me, I've got too many articles and notes with cross-references (multiple tags) to throw away.

In my mind after, lets say, a hash ('#') a tag should be written to create a tag.
When typed first character all existing tags with that character should show to be able to select (just like the '/' functions).
This should also work in search, rendering the remark regarding teams not knowing all tags obsolete.

Is there no way to up-vote this feature request?

@laurensalmekinders commented on GitHub (Jul 15, 2025): I really dig AppFlowy, and would love to migrate and enhance possibilities but the lack of tags is unfortunately a massive showstopper for me, I've got too many articles and notes with cross-references (multiple tags) to throw away. In my mind after, lets say, a hash ('#') a tag should be written to create a tag. When typed first character all existing tags with that character should show to be able to select (just like the '/' functions). This should also work in search, rendering the remark regarding teams not knowing all tags obsolete. Is there no way to up-vote this feature request?

mirror commented

2026-03-23 21:23:54 +00:00

Author

Owner

@arigit commented on GitHub (Sep 7, 2025):

+1 vote on tag support. It's a basic migration blocker. together with diagram embedding (mermaid, draw.io), journal mode, templates. On the plus side, this is the best MD editor I've seen.

@arigit commented on GitHub (Sep 7, 2025): +1 vote on tag support. It's a basic migration blocker. together with diagram embedding (mermaid, draw.io), journal mode, templates. On the plus side, this is the best MD editor I've seen.

mirror commented

2026-03-23 21:23:55 +00:00

Author

Owner

@LucasXu0 commented on GitHub (Oct 3, 2025):

If there was an option to add tags it would be perfect.

Similar request from the Google Play Console.

@LucasXu0 commented on GitHub (Oct 3, 2025): > If there was an option to add tags it would be perfect. Similar request from the Google Play Console.

mirror commented

2026-03-23 21:23:55 +00:00

Author

Owner

@poelzi commented on GitHub (Nov 26, 2025):

I don't get it. This is a blocker for what 1/3 of people using other programs, because this is so basic functionality for any such program since the last 10 years ?

@poelzi commented on GitHub (Nov 26, 2025): I don't get it. This is a blocker for what 1/3 of people using other programs, because this is so basic functionality for any such program since the last 10 years ?