Practical Markdown guide
Markdown Starter Guide
By KenRich ยท Last updated: July 19, 2026
This guide is written for people who want a usable Markdown workflow, not a wall of theory. Start with the web editor, try the examples, then move to desktop when local files and offline work matter.
Start with a simple draft
Open the web editor if you want the fastest path from blank page to rendered output. You can write without signing in, preview instantly, and download Markdown or HTML when you are done.
A useful first draft usually needs only a title, a short summary, and one or two structured sections. That is enough for notes, docs, blog posts, and release summaries.
# Project Notes
## Summary
Write a short paragraph.
- Keep it readable
- Keep it local
- Export when readyProject Notes
Summary
Write a short paragraph.
- Keep it readable
- Keep it local
- Export when ready
NoteUse short headings and short lists first. Structure beats decoration.
Use the parts Markdown is good at
Headings help readers skim. Lists help them scan actions. Tables help compare options. Code blocks help explain commands. Math helps when you write formulas or technical notes.
VeloWrite also supports tabbed code examples, so you can show Python, Bash, JavaScript, or Java in one place without turning the page into a long stack of blocks.
| Field | Value |
| --- | --- |
| Status | Preview |
| Export | Markdown / HTML |
```bash
npm run build
```
$$E = mc^2$$| Field | Value |
|---|---|
| Status | Preview |
| Export | Markdown / HTML |
npm run build
$$E = mc^2$$
NoteTables, code fences, and math are often enough for technical writing.
Move to desktop when the file matters
The browser is best for quick drafts and public sharing. The desktop app is the better home for real files, local folders, offline work, recent files, and local history snapshots.
If you care about keeping a Markdown vault on your own machine, the desktop app is the one that fits that workflow better than a browser tab.