A cloud wiki wraps the page in a service
A cloud wiki promises that every note is available from any browser. The page that holds the note is rarely the only thing on the screen. Before the first paragraph, the wiki asks for an account. Beside the words it places a navigation tree, a comment thread, a share control, and a stack of notifications. The document becomes one panel inside a product that also wants you to manage people, permissions, and a workspace on someone else's computer. Reading turns into a small part of operating the service.
A local folder keeps the file as the document
Local documentation works in the opposite direction. The file is the document. It sits in a folder you already keep. You open that folder and you read. No sign-in stands between you and the paragraph, because no account stands in the way. The words do not wait on a network round trip, and they do not move when a service changes its layout. The folder is the library. When the work is to understand a design, a runbook, or a chapter, that plain arrangement is what keeps the hour intact.
Focus is easy to spend and hard to get back. A heavy wiki spends it on chrome. A click can open a page history, a suggested page, a person to notify, or a permission you do not hold. Those surfaces help when a group is coordinating. They get in the way when one person is following an argument from the first heading to the last. Local files drop that bargain. The page you opened is the page. The next page is another file in the same folder, not a node in a hosted graph you have to keep in your head while you think.
A folder of Markdown also keeps the work in a form you can carry. You can copy the folder, put it on a drive, or leave it where the rest of the project already lives. You are not borrowing the right to see your own sentences. The user owns the data. If the laptop is offline, the documents are still there, because they never left the machine. A cloud wiki treats the network as part of the document. A local folder treats the disk as enough.
There is a difference in pace, too. A hosted page often redraws itself to show what changed for other people: a new badge, a rearranged sidebar, a prompt to try another surface. Each of those changes asks for a glance. A local file does not do that. It waits. You can stop in the middle of a section, look away, and come back to the same sentence in the same place. The document is not competing with the tool for your attention, because the tool is mostly absent.
Aero Markdown is a native macOS Markdown reader for a folder that already lives on the Mac: fully offline, no account, and no cloud. You open a file or a folder on macOS 14 or later, and the files stay on the Mac. The window has three columns: a file tree, a rendered document, and a heading outline. The tree is the folder you opened. The document is the page, set so a paragraph can be read at length. The outline is the headings in that page, so a long file still has a map that belongs to the file itself.
Images in that folder render on the Mac. Code highlighting runs locally. Mermaid diagrams render locally. The reading path does not ask a server to draw the page. Opening a document does not upload it. Nothing in the document is sent to a service. Save writes the open file when you choose Save. When you close the window, the folder is still the folder on the Mac.
Aero Markdown is a native macOS Markdown reader that keeps a folder of documents on the Mac, fully offline, with no account and no cloud in the app. That is the smaller job local documentation is for: the page holds still, the files stay where you left them, and Save writes the open file when you choose Save. The offer is $14.99 USD one-time for a lifetime Aero Markdown 1.x license for 1 Mac on macOS 14 or later, with no hidden costs. Download and checkout are not available yet.
Links respect the same boundary. A relative link to another Markdown file in the opened folder opens in Aero Markdown, and back and forward keep the history of that reading. You can move from a chapter to a note and return without leaving the window. A link that leaves the folder does not open inside the app. That limit is part of the focus. The folder you chose is the set of pages you meant to read. The app does not wander into the rest of the disk, and it does not turn an outside address into another document in the window.
A heavy cloud wiki is built so many people can change one shared space at the same time. That design adds accounts, permissions, comment threads, and a constant sense that the page might shift under you. Local documentation is built for the person who needs the page to hold still. The file stays on the Mac after you finish reading it. You can close the laptop, open the folder tomorrow, and find the headings in that file. Nothing in that loop requires a connection, a session, or a seat in someone else's workspace.
The limit of a local reader
There is an honest limit. A local reader does not host a team workspace, and it does not sync a library into the cloud. If the job is a multi-person wiki with permissions and a comment thread, a cloud product is a different tool. If the job is to read the Markdown you already keep beside the work, a local folder is the lighter way to do it. Attention stays on the document, not on the service wrapped around it.
Aero Markdown stays inside that smaller job. The offer is $14.99 USD, one-time, for a lifetime Aero Markdown 1.x license for 1 Mac, with no hidden costs. Download and checkout are not available yet. There is a 14-day refund on the software license key, requested only through support@aeromarkdown.app. The site and the app use zero background analytics or tracking. Those are the terms of a reader that keeps the files on the Mac, so the time you set aside for the document can stay on the document.