Tags

A folder can only put a document in one place, but most documents belong to more than one category at once, a meeting note that's also a project artifact, a draft that's also a todo. Tags let you label a document by topic, status, or workflow without moving it, and a single document can carry as many tags as it needs.

Inline tags

Type a # directly before a word anywhere in the body of a document to turn it into a tag. Simple ASCII tags are the most predictable current editor form. Nested slash tags such as #project/roadmap are part of the target shared tag contract, but editor highlighting and every derived consumer are not yet guaranteed to agree on the full dialect.

#productivity #notes #project/roadmap

Front matter tags

If you'd rather keep tags out of the body text, list them under a tags key in front matter instead. Front matter tags use the bounded property grammar. Nested slash tags may be preserved as metadata, but do not assume identical editor, search, graph, and export behavior until the shared tag contract is implemented.

---
tags:
  - docs
  - project/roadmap
---

Current limits

Tags inside code, fenced code, comments, and other owned Markdown ranges should remain literal. Unicode tag expansion and complete parity across every tag-derived view are not part of the current Help guarantee.

Using tags

Wherever they're written, tags surface in your project's tag tools so you can browse every document under a given tag at once, and they appear as connected tag nodes in Graph View, making it easy to spot which documents share a label even if they never link to each other directly.

Related pages

To attach a tag list alongside other structured metadata, see Front Matter. To see how tagged documents relate to each other visually, see Graph View.