track

track

track is a linked Markdown knowledge base. Notes are plain Markdown files; you connect them with explicit [[Title]] wiki links, and a Go engine indexes the vault for search, link resolution, and a local web workspace.

This help site is itself produced by track export-site, so it doubles as a working example of the static-site export.

Your workspace at a glance

The block below is a live Home dashboard widget — a dashboard fence the engine resolved into recent notes and pinned links, the same way it renders in the local web workspace:

Recent notes

• Babel
• Block links
• Charts
• CLI

Pinned

• Syntax
• Web workspace

Where to go next

• Syntax — the Markdown a note is written in: bold, math, tables, footnotes, and the Obsidian-style constructs.
• CLI — the command-line interface that owns parsing, indexing, and search.
• Searching notes — title, tag, and full-text body search, with ranking and CJK support.
• Linking notes — how [[...]] links, backlinks, and the note graph work.
• Block links — mark a paragraph or list item with ^id, then link to it or transclude it.
• Tasks — checkbox lines with named states, priorities, deadlines, progress cookies, and a kanban board.
• Calendar events — register all-day or timed events, edit them later, and restore deleted events.
• Properties — typed key-value metadata on a note: sidecar props, inline key:: value fields, and an optional schema.
• Hierarchy — breadcrumbs and children from the up:: [[Parent]] relation property.
• Query — table queries over notes by tag and property, embeddable in a note as a live track-query block with a table, board, gallery, or calendar layout; plus hierarchical tags and per-tag pages.
• Web workspace — the local browser UI for reading, previewing, and navigating notes.
• Markdown viewer — read local Markdown files and folders without importing them into a vault.
• Static apps — build a small browser app in apps/<name>/ and open it as a top-level page.
• Home dashboard — a configurable landing note, embeddable dashboard widgets, and per-note icons.
• Visualization — how notes render as visuals: Diagrams (Mermaid, Graphviz, D2, and draw.io), Mindmaps of a note's structure, Charts from a View Spec, and Embeds for YouTube, PDFs, tweets, and other rich media.
• Babel — run a note's fenced code blocks and keep their results in the sidecar; compose blocks with noweb references, call them with variables, and tangle them out to files.
• Web clipper — clip a web page's readable content into a note with track-fetch-web.

How the pieces fit

The Go CLI is the source of truth: the Neovim plugin and the web workspace are thin frontends that shell out to it. Reusable engine code lives under internal/track/* so other integrations can build on it without depending on the command layer.