A link is a path, not a library
A relative Markdown link points from one file to another location in the folder structure. It can connect ordinary .md files without a cloud workspace. To follow it, a reader needs the target file and appropriate access to its location. If you read in Aero Markdown, Follow links and find your way back covers its back and forward history.
Download the Project Reading Kit. It is a fictional project made of six linked Markdown files. Open the complete folder, rather than extracting only its README.
Walk from a requirement to its reason
Start at README.md, open Specification, then Architecture, then the local-file decision. Each step answers a different question: what is required, how the parts connect, and why the proposed storage choice was made.
A link from the specification to architecture uses:
[Architecture](architecture.md)
The path is resolved from the document containing that link. Because both files are in the same directory, the filename is enough.
Link to a heading inside another document
The architecture links back to acceptance criteria:
[Acceptance criteria](specification.md#acceptance-criteria)
The filename identifies the document; the part after # identifies its heading. Heading identifiers are renderer-dependent, particularly for punctuation or duplicate headings. Check the target in the reader you use rather than assuming every renderer creates identical anchors.
In Aero Markdown, Copy Link to Heading can help produce a link for a section. Back and Forward return through documents you visited; a heading outline navigates within the current document.
Three useful failure checks
Missing file: a link still says architecture.md after that file was renamed. Check the target filename, including case when moving between file systems.
Wrong base folder: a file moved into notes/ still links to architecture.md, which now means notes/architecture.md. The relative path must match the new location.
Missing heading: a document opens but the requested section was renamed. Check the heading and the anchor created by the renderer.
Try these changes on a copy of the kit, not on important documentation. A reader can show where a link leads; this guide does not claim that Aero automatically audits every link in a folder.
Keep navigation and editing distinct
Opening a link in a supported folder reads the target. Saving an edit changes the open file. If another editor or agent rewrites that already open file, Aero's automatic reload can follow it when there are no unsaved edits. It does not automatically open every new document in the folder.
See the agent-document guide for the complete distinction. For a first folder, use open a local folder; for the reasoning behind this kit, read the project walkthrough.