How to Edit Markdown on a Mac
Without a Preview Pane

What does editing without a preview pane mean?

A split Markdown editor shows source text in one pane and a rendered preview in another. A single-pane editor brings editing and live formatting into the same document, so you can work on a heading, paragraph or table where you read it.

MarkdownEasy is a native Markdown editor with that single-pane approach. It supports headings, bold, italic, lists, links and blockquotes, along with images, fenced code blocks and editable tables. You still work with Markdown files; the presentation helps you focus on the writing.

This can suit meeting notes, a project outline or a first draft when you want more room for the document. If you need to check exactly how a README or article will look on another platform, review it on that platform too: Markdown features and styling can differ between renderers.

1. Get ready to write

Download the Mac edition from kubuzz.us, open the disk image and drag MarkdownEasy (MDE) to Applications. This edition requires macOS 12 Monterey or later on Apple silicon. It includes a 30-day free trial with no account, activation key or card.

Start with a short document or a copy of an existing Markdown file. Choose a familiar task, such as writing a meeting agenda, rather than testing every formatting feature at once. Keep the original file if you are trying the editor with an important document.

Your notes are ordinary text files stored where you choose, including a folder or cloud service selected through the system file picker. For details about note storage, remote images and license activation, see the MarkdownEasy privacy policy.

2. Give the document structure

Begin with a title, add a few section headings, then write short paragraphs and lists. MarkdownEasy’s live formatting keeps that structure visible in the editing document.

The example below shows Markdown syntax for a simple agenda. It is sample source text, not a screenshot or an exact representation of the editor’s appearance.

# Weekly project notes

## What changed

We finished the **first draft** and collected feedback.

## Next steps

- Review the introduction
- Check the examples
- Share the revised draft

> Keep the next revision focused on clarity.

Use heading levels to show the relationship between sections: one main title, then smaller headings for the sections beneath it. Use bold for a short emphasis, rather than making whole paragraphs bold. The CommonMark reference is a useful syntax reminder.

3. Add links and images

Use descriptive link text so the document makes sense without reading a long URL. In Markdown source, an inline link looks like this:

[Project website](https://kubuzz.us/)

MarkdownEasy supports local and remote images. Before sharing a file, check that its images will be available to the recipient: a reference to a file on your Mac does not automatically give someone else that file. A remote image requires access to its host and makes a network request when loaded.

Keep essential instructions in text as well as in images. That helps readers understand the document when an image is unavailable.

4. Work with code blocks and tables

For a command or code example, use a fenced code block to keep the sample separate from the surrounding prose. MarkdownEasy supports fenced code blocks with syntax highlighting. This sample shows the Markdown source for a small JavaScript block:

```javascript
const message = "Draft ready";
console.log(message);
```

For information that readers need to compare, MarkdownEasy supports editable GitHub-flavored Markdown tables. You can edit cells, add or remove rows and columns, and resize them. Start with a small table, such as this source example:

| Task | Status |
| --- | --- |
| Draft | Ready |
| Review | Next |

Tables are an extension to basic Markdown. If your document will be published elsewhere, check that the destination supports them. GitHub’s table guide explains its syntax. Use a list instead when you only have one piece of information per item.

5. Review the document and save your work

Read through the same pane you used for writing. Check the heading order, list items, link destinations, code examples and table cells. Save your work in the location you intend to keep it, and reopen the file to confirm the content you need is there.

For documents going to GitHub, a website or another editor, do a final check in that destination. Live formatting is helpful while drafting, but it is not a promise that every platform will display the file identically.