Links, backlinks, and nodes#

A Markdown file becomes a graph node. A saved link from one file to another becomes a directed edge.

Each saved Markdown link becomes a directed edge. The target note receives a backlink automatically.

Standard Markdown link#

See the [API contract](../api/customer-api.md).

This is the portable form used by OKF and standard Markdown tools.

Wiki-style link#

See [[Customer API]].

DevDesk can recognize wiki-style links in supported knowledge workflows. A wiki link depends on title/path resolution and can become ambiguous when multiple notes have the same name.

Absolute bundle-relative link#

See the [Customer API](/api/customer-api.md).

For OKF bundles, a leading / means “from the bundle root.” It is often more stable when a file moves inside its current directory.

Backlinks#

If architecture.md links to api.md:

architecture.md has an outgoing link to api.md.
api.md automatically shows an incoming backlink from architecture.md.
You do not manually write a second reverse link unless the content truly needs one.

Create a connection manually#

Open the source note.
Place the cursor where the relationship is explained.
Insert a normal Markdown link or wiki-style link.
Save the file.
Rebuild or refresh the graph if it does not update immediately.

Avoid meaningless links#

The link text and surrounding sentence should explain the relationship:

The mobile client sends validated requests using the
[Customer API contract](../api/customer-api.md).

A graph edge is intentionally untyped; the prose gives it meaning.