Build a personal wiki, one link at a time
Wrap any phrase in [[double brackets]] to link notes together — following a link to a note that doesn’t exist yet creates it, and every link becomes an edge in your graph.
Wiki links are the connective tissue of a Dexi workspace. While writing, wrap a concept in [[double brackets]] — [[spaced repetition]], [[Q3 pricing review]], [[the maintenance trap]] — and it becomes a link to the note by that name. If that note doesn’t exist yet, following the link creates it, so you can sketch the shape of an idea before filling it in.
Links work in both directions: each one is an edge in your knowledge graph, which means the connections you make while writing are the same ones the graph view and related-concepts traversal explore later.
Why it matters
Linking while writing captures something tags can’t: the specific, directional claim that this idea relates to that one. A tag says “this is about pricing”; a link says “this argument depends on [[willingness to pay]]”. Over time those little claims accumulate into a personal wiki — your own encyclopedia of the concepts you work with, written in your own words.
The create-on-first-reference behavior also changes how you plan. You can write an outline whose bracketed sections don’t exist yet, and the empty links become a visible to-do list for your thinking.
Who gets the most out of it
- Zettelkasten and evergreen-notes practitioners — Concept notes linked at the moment of writing are the method, with no plugin required.
- Novelists and worldbuilders — Characters, places and plot threads become a story bible that cross-references itself.
- Engineers keeping decision logs — Each design decision links to the constraints and prior decisions it rests on — an audit trail of reasoning.
- Students building durable understanding — Linking new concepts to known ones is the encoding step that makes material stick.
Example: An engineer writing a design doc
You’re writing up a decision to move billing to event-driven processing. As you draft the note, you link the load-bearing concepts:
- “We’ll adopt [[event-driven billing]] despite the complexity cost, because [[invoice latency]] is now our top enterprise complaint. This reverses [[2024 billing simplification]].”
- [[invoice latency]] and [[2024 billing simplification]] already exist — the new note is now wired into their histories, and each of them links back here.
- [[event-driven billing]] doesn’t exist yet. You follow the link, and the empty note is created — you drop in two bookmarked articles and a paragraph of context while it’s fresh.
- A year later, a new teammate asks why billing is event-driven. You send one link; the backlinks walk them through the entire decision lineage.
Try it in your own workspace — free, no credit card required.
Get started