Writing

Mentions & hashtags

Smart tags are how Nomima understands who and what your notes are about. Tag once while writing — every view, lens and graph updates automatically.

What smart tags are

A smart tag is a small colored pill embedded in your text. There are two families:

Every tag becomes an entity in your Knowledge Graph. Tag @Sara in five different notes and Nomima knows they’re all about the same person — her Smart View lens, graph node and entity card collect everything in one place.

👤 @Sara Chen owns the 💼 #launch — kickoff review lands Fri 5pm.
Every tag is a small coloured pill embedded right in your text.

Creating a tag

  1. Type @ or # followed by a name. A suggestion menu appears with matching entities you’ve used before.
  2. Press Enter or Tab to accept the highlighted suggestion — Tab always accepts the suggested tag, so you can type two letters and let Nomima finish the name.
  3. If the name is new, the menu offers a Create new row for each type — pick the type right there and press Enter. That’s the whole decision: there’s no follow-up “which one did you mean?” picker afterwards.
  4. Press Esc to dismiss the menu and keep the text plain.

The menu suggests the type for you. For a brand-new @mention whose name Nomima’s offline gazetteer recognizes, the Create new rows lead with the predicted type as the Enter default — @MicrosoftCompany, @LondonLocation, @SarahPerson. A name it doesn’t recognize leads with No type, and No type plus every other type always follow so you can override in one keystroke. Hashtags get no predicted type — they lead with No type.

Met with @Microsoft yesterday
Create “Microsoft” as
🏢 Company predicted
📦 Product
👤 Person
📄 Document
No type
Pick the type right in the menu — the predicted one is the Enter default.

Identity is name + type. An entity is unique per name and type, so @Apple the Company and @Apple the Product happily coexist as two entities — but you can’t pile up two Companies both called Apple. Got the type wrong? Change it from the pill’s entity card and just that pill re-points to the right entity.

Ghost suggestions: as you type ordinary text, Nomima may show a faint dashed preview of a tag it recognizes (type “Mo” and see @Moe ghosted ahead) with a small hint. Press Tab or click it to convert; Esc dismisses it for that spot. You can turn this off with Settings → Smart Tag Types → “Suggest Smart Tags as I type”.

Built-in types

Each tag has a type that controls its icon, its color everywhere (pill, graph node, minimap dash), and which Smart View lens it appears under.

FamilyTypeIconUse for
@ mentionPersonuserIndividual people
@ mentionTeamusersGroups, squads, departments
@ mentionCompanybuildingOrganizations, clients, vendors
@ mentionLocationmap pinPlaces, offices, cities
@ mentionProductpackageProducts and services
@ mentionTechnologycpuTools, languages, platforms
@ mentionEventstarConferences, launches, occasions
@ mentionDocumentbookPapers, specs, reports, files
# hashtagProjectbriefcaseInitiatives with a beginning and end
# hashtagIdealightbulbThings you might do someday
# hashtagTopicbookSubjects and themes
# hashtagAreafolderOngoing areas of responsibility
# hashtagMeetingusersStandups, 1:1s, reviews
# hashtagStatusflagStates like #complete, #blocked, #in-review

Status is special: the Status type powers Nomima’s universal completion system. Stamping #complete on any block marks it done everywhere — see Complete & incomplete. Status tags also drive Kanban columns.

Select (option) tags

Some tags hold a single chosen value instead of acting as a free-form label. Select tags — like Priority or Severity — let you pick one value from a dropdown rather than typing a new one each time. They behave like a fixed set of options, so in a Database you can sort and filter rows by them cleanly. (This is distinct from a normal multi-value #hashtag, where you’re free to coin new tags as you go.)

Custom types

You’re not limited to the built-ins. In Settings → Smart Tag Types you can:

Custom types get their own color in the Knowledge Graph legend and their own grouping in search — they’re first-class citizens.

Settings · Smart Tag Types
@ Mention types
👤 Person
🏢 Company
📍 Location
📦 Product
🤝 Client custom
Add type
# Hashtag types
💼 Project
💡 Idea
🚩 Status 🔒
📁 Area
Add your own types or restyle the built-ins — each keeps its own colour and icon.

Entity cards & attributes

Click any pill to open its entity card — the hub for that person, project or thing:

SC
Sara Chen
👤 Person
👤👥🏢📍📦
Edit Profile Appears in
Emailsara@acme.co
RoleHead of Design
Team👥 @Design
Click any pill to open its hub — attributes, a custom photo, and everywhere it appears.
Entity · Sara Chen
SC
Sara Chen
👤 Person
Overview Mentions Tasks Profile
12
Mentions
4
Open tasks
5
Notebooks
Appears with
@Sam Ortiz #launch @Acme Co #research
Connections by type
Person7
Project4
Company2
Expand a card into a full page — computed stats, who it appears with, and its connections.

Auto-photo from email. Type a person’s email and Nomima quietly fetches their Gravatar photo if they have one. The address is hashed before any lookup and never sent in the clear; if there’s no match, nothing is stored — and it never overwrites a photo you uploaded yourself.

Profile tab. When an entity has an email, its card gains a Profile tab with public info looked up on demand by hash — name, location, bio, the organization inferred from the email domain, and any public social accounts. It’s fetched only when you open the tab.

Entity relationships

Attributes describe an entity on its own. A relationship is a durable, typed link between two entities@Sara member of @Design team, or #Launch owned by @Sara. Because it’s stored against each entity’s stable identity, a relationship survives graph rebuilds and shows up from both sides automatically.

Creating a relationship

You don’t draw links by hand — you add a relation field to an entity, and every value you put in it becomes a link:

  1. Open an entity card and choose Add field → Relationship.
  2. Under Links to, optionally restrict the field to one type (a Person, a Team…) so the picker only offers the right kind of entity.
  3. Nomima shows a live “How it reads” sentence spelling the link out from each side. Two chips (this entity and the other) sit around an editable verb — type your own forward wording (manages, owned by) and the reverse wording for the other side. Leave them blank to accept the sensible defaults (contains / belongs to).
  4. Save the field, then pick the target entities. Each one you add creates the link and mirrors it onto the other entity’s card.
Add relationship field
How it reads
👥 @Design manages ⌶ a Person
a Person member of ⌶ 👥 @Design
@Design is the container (members inherit it)
A relationship is authored as a field: name the verb on each side, then pick who it links to.

Direction, cardinality & the container

Inherited relationships

Containers chain. If @Sara is in @Design, and @Design is in @Acme, then Sara’s card also shows @Acme as an inherited relationship — rendered muted, labelled via @Design. Nomima walks the containment chain up at query time, so inherited links are never stored: delete the Design → Acme link and Sara’s inherited Acme quietly disappears. Only container (membership) links propagate — an ordinary link like partners with stays put.

Where relationships show up

On an entity card, relationships are read-only and grouped one row per label and direction — a team shows Members: @Sara, @Moe on a single row rather than one row each. Each target is a real pill in its own type colour, and clicking it jumps to that entity. The Knowledge Graph folds these authored links straight in as labelled edges between nodes.

SC
Sara Chen
👤 Person
Relationships
Member of 👥 @Design
Reports to 👤 @Moe Diaz
Member of 🏢 @Acme Coinherited · via @Design
Relationships read as sentences on the card; inherited ones appear muted with their “via” path.

Read it like a sentence. The verbs you type are the whole point — pick wording that reads naturally out loud (“@Sara reports to @Moe”, “@Moe manages @Sara”) and every card and graph edge stays legible.

Pill behavior in the editor

Why bother tagging?

Tags are the fuel for everything downstream: