Tag types
Allow users to define different types of tags, adding an optional semantic layer to Capacities' existing tagging system.
A tag type describes what a tag represents. For example, a user could create tag types such as Topic, Area, Technology, or Context, with tags such as:
- Topic → AI, Psychology, Design
- Area → Work, Personal, Health
- Technology → React, Python, PostgreSQL
Tags would remain global and work across object types as they do today, but each tag could belong to a specific tag type.
Object type constraints
Object types could specify which tag types are allowed in their Tags property. For example:
- Project → Area, Topic, Technology
- Book → Topic
- Weblink → Topic, Technology, Source
When adding tags to an object, the tag picker would only suggest tags belonging to the allowed types. Creating a new tag could automatically assign it to the relevant type.
This would let users introduce structure and guardrails to tagging without losing the cross-object flexibility that makes tags useful.
Grouped tag UI
Tags on an object could optionally be grouped by their type:
AreaWork
TopicsAI, Knowledge Management
TechnologyPython
The tag view could similarly group or filter tags by type, making large tag libraries easier to navigate.
Namespaced tags
Tag identity could be scoped by tag type, allowing similarly named tags to represent different concepts.
For example:
- Topic → Design
- Area → Design
These would be separate tags despite sharing the same display name.
Why this is useful
As a space grows, a flat collection of tags can mix several different semantic dimensions: topics, contexts, areas, technologies, workflows, and other concepts.
Tag Types would preserve the lightweight and cross-object nature of tags while making their meaning explicit.
They would sit between labels and ordinary tags:
- Labels structure one object type.
- Tags freely connect content across object types.
- Typed tags connect content across object types while also expressing what kind of connection the tag represents.
3 Comments
Sign in to comment
You can approximate this by organizing your tags into Collections
It is urgently needed, as the current tags are quite disorganized. Just two layers of tags would suffice to meet the vast majority of needs.

Oh, I like this idea better than sub-tags. I like the idea that a set of tags could be restricted to a particular object type.