DunneNote documentation
DocsDunneNoteWorking in DunneNote

Links and templates

Shipped

Linking within and between notebooks, wiki-links, link safety, and making a page a template.

Within a notebook. Link from any rich text, or from a picture hotspot, to another page.

Between notebooks. DunneNote keeps a catalog of notebooks you have opened. A link can target a page in any notebook in that catalog; following it opens that notebook and switches to the page. Because notebooks carry a stable identity in their manifest, such a link survives the target notebook being moved or renamed.

To the web. Ordinary external links, opened in your browser.

Type [[Page Name]] and it becomes a link to that page. If the page does not exist yet, the link records the intent — the same convention as a wiki, where writing the link comes before writing the page.

Links are the one place a note-taking application invites content from outside, so they get explicit handling.

The true destination is revealed on paste. When you paste a link whose visible text disagrees with where it actually goes, DunneNote shows you the real destination rather than the label.

Suspicious destinations are flagged against a blocklist and a set of heuristics that ship with the application.

Both checks run entirely offline. There is no HTTP client involved in checking a link, no lookup service, and nothing about your links leaves your machine to be checked. The blocklist is bundled and updated with the application, which is a deliberate trade: a bundled list goes stale between releases, but a live one would mean sending every link you paste to somebody else.

Templates

Any page can be made a template. Creating a new page from it copies its structure — its canvases, their arrangement, their settings — without copying the content. A weekly report layout, a meeting-note skeleton, or a lab-book page gets set up once.