How people use EasyMD

EasyMD is a Markdown editor that runs in your browser with nothing to install and no account. These are the five things people most often use it for.

💼 Common uses

🛠️ Step by step

Here is what three of those actually look like in practice, in order. Follow along.

Meeting notes: shared the moment the meeting ends

Notes you plan to tidy up after the meeting mostly never get written. The trick is to finish them during the meeting, which means setting up the structure first and filling in blanks.

1. Thirty seconds before it starts. New document, then # followed by the meeting name and date. Under it, four ## headings: Attendees, Agenda, Decisions, Action items.
2. During. Type under the relevant heading, nothing fancy. When the topic changes, drop in a --- divider to break it up visually. If something is shared on screen, capture it and paste with Ctrl+V right where you are.
3. Action items as a checklist. Pick Checklist from the slash menu and put who, what, and by when on one line. Leading with the owner's name means everyone can find their own items at a glance later.
4. Right after it ends. Export from the File menu as Word (.docx) or PDF and send it. If it is going into an internal wiki, Markdown survives the move better.

You never need to press save. Stop typing and it saves itself, and a restorable point is kept every five minutes — so a paragraph deleted by accident mid-meeting comes back from the history tab.

READMEs: never start from a blank page

What makes a README hard is not the syntax but knowing what to write first. With an order to follow, it takes about twenty minutes.

1. One line first. The sentence under the title should answer what this is and who it is for. Go longer than that and nobody reads on.
2. Install and run in code blocks. Add bash after the three backticks and the commands get coloured, which makes them easier to copy.
3. Options and environment variables in a table. Use the slash menu's table picker and make three columns: name, default, description. Drag the borders to set the widths.
4. Screenshots by paste. Capture the running app and paste it in — it is compressed automatically.
5. Rename to README.md and export. Click the file name in the header, change it, download as Markdown, and drop it at the root of the repository.

One caveat. GitHub strips the style attribute for security, so text colour set in the editor will not apply there. Use bold or a blockquote for emphasis instead.

Blog drafts: moving them without breaking the formatting

Write the draft here, then move it to Medium, Dev.to, Ghost, or WordPress. Formatting often breaks during that move, and the reasons are usually the same few.

1. Structure first, then fill it in. Lay out five or six ## subheadings, write a one-line summary under each, then expand those summaries into paragraphs. The piece tangles far less that way.
2. Export as Markdown when done. Copying from the rendered screen drags HTML along with it, which is what breaks on the other end. Open the .md file and paste the raw source instead.
3. Then fix only what that platform does differently. Some accept Markdown almost verbatim; others need you to switch the editor into Markdown mode before pasting. Images are safest re-uploaded in the destination editor whatever the platform.

Which platform does what is worth checking before you paste — every one of them handles tables and line breaks slightly differently.

📚 Related pages

• Markdown syntax guide — headings, lists, tables, and links
• Keyboard shortcuts — the combinations worth learning
• Frequently asked questions
• Compared with other editors — including when EasyMD is the wrong choice