Skip to content
Features/Writing and organization

Markdown and files

Markdown is the source of truth for document content in Tano. Ordinary .md files can still be opened and managed with other text tools.

Behind the formatted page is an ordinary Markdown file you can keep using with other tools.

Document format

Headings, paragraphs, lists, quotes, code, tables, and links are stored in Markdown. Visual mode provides an editing interface; source mode shows the underlying text. Tano also supports some extended syntax, which other readers may display only as source.

# Project notes

Things to do today:

- [x] Gather materials
- [ ] Write a conclusion

> Give every idea a place to start.

Supported formats and extensions

Type Available content
Basic Markdown Headings, lists, checklists, quotes, fenced code, GFM tables, links, and images
Math and diagrams Inline and block math, Mermaid, and footnotes
Notes and layouts NOTE, TIP, IMPORTANT, WARNING, and CAUTION callouts; toggles, tabs, and columns
References Wiki links, heading links, document and workspace-object references
Properties and resources YAML frontmatter, file cards, images, and media embeds

For example, a callout can be written as:

> [!TIP]
> Check references before accepting a suggested edit.

Enable or disable extensions in document capabilities. Other Markdown readers may not render Tano extensions; check syntax support when exchanging files.

Math recognition and object references

Inline math accepts $...$ and \(...\); display math accepts $...$ and \[...\]. Document capabilities can recognize all, dollar-only, or LaTeX-only delimiters. Unrecognized forms retain their source. Recognition is separate from the syntax selected for saving. Formula markers inside code stay literal.

[[object://type/six-digit-ID]] stores identity and displays the object's current name; a standalone ![[object://type/six-digit-ID]] displays a card. Generate real references with the picker. Ordinary [[document/path]] remains a path link, and legacy [name](object://...) references remain readable.

Preserved source is not rendered support

Unknown directives, ordinary document Wiki embeds such as ![[document/path]] (distinct from supported object cards), code-fence metadata, and TOML frontmatter are conservatively preserved. Use source mode when prompted. Preserving text does not mean every syntax can be visually edited or used in real-time collaboration.

The browser demo includes examples for comparing rendered and source views.

Local folders

A local desktop workspace reads and writes the folder you choose. The body is ordinary Markdown, and attachments are ordinary files. Tano's portable workspace data stays under .tano/. Cache and personal interface state remain in application data, outside the workspace root.

You can keep using Git, other editors, or your configured agent with these files. External changes are never overwritten silently: independent changes are merged when possible, and conflicting content is preserved for review.

Online workspaces

An online workspace also stores Markdown, but the workspace service manages its files. The service manages files and folders; creating and organizing them requires the corresponding permissions. A local desktop folder is not connected automatically; you can explicitly configure file sync.

See Organize documents for ways to manage documents in the app.