A Markdown reader and an editor have different jobs

Choose a source view for changing Markdown and a rendered page for reading it. A practical distinction for READMEs, reports, and linked documentation.

Two views of the same file

Markdown is plain text with structure. A heading begins with #; a link includes a label and a path; a table uses pipes to separate cells. Those characters are useful when you are changing the document.

A rendered page presents the result: headings, readable paragraphs, linked text, tables, code, and diagrams. That view is useful when your task is to understand the document rather than work on its syntax.

The file can be the same in both cases. Choosing a reading view does not require converting it to a new format or moving it into another library.

When the source view helps

Use the source when you need to change a sentence, check the path in a relative link, fix a table, or revise a fenced Mermaid block. You can see the structure explicitly and decide exactly what to save.

Aero Markdown includes editing for the open document, with find and replace and a preview beside the source while editing. Save writes that file. The availability of those controls does not mean that opening a document changes it.

When the rendered page helps

A long README may mix explanation, code samples, a task list, and links to supporting documents. In a rendered view, you can read the explanation without tracking every formatting character.

A heading outline shows the shape of the page. A file tree shows the shape of the folder. Relative links let the document itself lead you to the next piece of context.

Try the downloadable example folder to see a table, a Mermaid diagram, and connected documents in one small project.

Let the reading settings serve the document

Aero Markdown lets you choose Serif, Sans, or Mono and adjust type size, column width, line spacing, and zoom. A code-heavy reference and a long explanation may need different settings.

The purpose of those controls is to let you set the page for the text in front of you. Your source stays on disk as Markdown. See the reading guide for formats, appearance, printing, and export.

Keep a clear boundary around changes

Reading and rendering do not rewrite the source. Editing and choosing Save do. When another tool changes the open file and you have no unsaved edits, automatic reload can refresh the rendered page at the current heading.

If both you and another tool have changed the document, your unsaved text is kept and the app reports the disk change. See how file reload works with coding agents for details.

A reader and an editor can sit beside the same project. Choose the view that fits what you are doing with the file now.