# ✱ Tags

✱ **Tags** are labels that help you categorize and organize your notes. By assigning tags to notes, you can easily group related content and retrieve it quickly when needed. Tags are especially useful for filtering notes across different ✱ **Collections**, making it easy to search for information without having to manually link notes. They are simple and flexible, allowing you to quickly categorize your notes based on topics, people, projects, or any other relevant criteria.

<figure><img src="https://cdn.prod.website-files.com/66d94b8cef94f6af748a1af1/67436e6d4d7c0d90e9b6a27a_66f04058fb8b942ee157ea65_66f040270a2e7a1065e06974_tags.jpeg" alt="Three iPhones display the Forever ✱ Notes system, showing tagged recipes, search results, and a detailed recipe for Spicy Thai Peanut Noodles."><figcaption></figcaption></figure>

Here’s a lots for you to get you started. Only use tags that are relevant to you.

**Note Types:**

* \#hub
* \#document
* \#idea
* \#person
* \#quote
* \#recipe
* \#reference
* \#trip
* \#tutorial

**Life Areas:**

* \#family
* \#finance
* \#goals
* \#health
* \#home
* \#education
* \#personal
* \#travel
* \#work

**Details:**

* \#cold
* \#hot
* \#italian
* \#asian

**System:**

* \#toDo
* \#inProgress
* \#done

### Setup

1. ‍**Open the Notes app** and start or open a note.
2. Type a **#** symbol followed by the tag name (e.g., #Project) anywhere in the note.
3. Once you finish typing, the tag will turn into a clickable link, indicating it’s been created.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://yuanxi-tseng.gitbook.io/forever-note-tw/components/tags.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.