For a long time my "blogging setup" was VS Code, a terminal, and a lot of patience.
I'd open my site's repo, find the posts folder, copy the frontmatter from an older post, fix the date, forget a tag, drag an image into the wrong folder, run git add, write a commit message I'd regret later, push, and then notice a typo on the live site. Every single time.
And because I write in both Arabic and English, there was an extra layer of pain. Most editors handle right-to-left text badly. Mix an Arabic sentence with a code snippet or an English term and the cursor starts jumping around like it's trying to escape.
So I built Mditoor. It's a desktop app for writing Markdown and MDX content, and it's free and open source (MIT). This post is a tour of what it does, because the feature list has grown a lot more than I planned.
What it is, in one paragraph
Mditoor is a local-first desktop studio (Tauri + React + Rust) where you can:
- Write posts directly inside your static site's repo (Next.js, Astro, Hugo, Jekyll and friends),
- Keep personal or study notes in plain Markdown folders, or
- Write and publish straight to DEV, even if you don't have a site at all.
Your files stay plain .md / .mdx on your disk. No database, no account, no cloud lock-in.
The editor
This is where I spend most of my time, so it got the most love.
- Block editor or raw Markdown. Write in a clean block-based editor, or switch to plain Markdown when you want full control. Same file either way.
- Edit, Split, and Preview modes. Write, see both side by side, or just read.
- Slash commands. Type
/and start filtering./imgets you an image,/h2a heading. Faster than reaching for the mouse. - Block menus. Right-click a block, or hit the
...button, to turn it into a heading, list, quote, callout or code block. There's a drag handle to reorder blocks too. - Floating selection toolbar. Select text and the formatting options show up right there, plus a context menu for text.
- Keyboard shortcuts for the usual formatting stuff.
- Auto-save with an interval you choose, and a clear saved / unsaved indicator so you always know where you stand.
- Word count on every post.
You can tune how it looks: light, dark, or follow the system theme, a choice of sans-serif or monospace for the writing surface, several font sizes, and line height (compact, comfortable, relaxed).
Built for Arabic and English (RTL + LTR)
This is the reason the app exists, honestly.
Mditoor detects text direction per block. An Arabic paragraph is right-to-left, the English one under it is left-to-right, and the code block stays where code belongs. It works the same in the editor and in the preview. You don't toggle anything.
You also get a separate Arabic font setting (Cairo, Noto Sans Arabic, Readex Pro are bundled), and the whole UI is available in English, Arabic and French.
If you write in Hebrew, Persian or Urdu, this should help you too. I'd love to hear how it goes.
Frontmatter without the YAML headaches
I don't know anyone who enjoys hand-editing frontmatter.
In Mditoor you define your metadata fields once per workspace, and every post gets a form instead of raw YAML or TOML. Supported field types:
-
text,number,boolean -
date(with a date picker) -
select(likedraft/published) tagsimage
Fields can be required, and the sidebar tells you when something is missing ("2 required missing") before you ship a post with no title. There's also a frontmatter preview if you want to see what's actually being written to the file.
The config lives in a .mditoor.json file in your posts folder, so you can commit it and your teammates get the same fields.
Framework presets
When you create a workspace, Mditoor tries to detect your framework and suggests the posts folder. Each preset sets the post layout, file extension, frontmatter format and where images go:
| Preset | Post file | Frontmatter |
|---|---|---|
| Next.js | <slug>/index.mdx | YAML |
| Astro | <slug>.md | YAML |
| Hugo | <slug>/index.md | TOML |
| Jekyll | YYYY-MM-DD-<slug>.md | YAML |
| Docusaurus | <slug>/index.md | YAML |
| Eleventy | <slug>.md | YAML |
| Nuxt Content | <slug>.md | YAML |
| Generic | <slug>/index.mdx | YAML |
Everything can be changed afterwards. Next.js is the one I test the most (it's what my own blog runs on), so if your setup doesn't fit, please open an issue with an example layout.
Git, without leaving the app
This was the second big reason. I wanted "write, commit, push" without opening a terminal.
The Git panel shows status and a diff view, and lets you stage, commit, pull and push. Nothing fancy, just the 95% of git I actually use while writing.
Images that go where they should
- Drag images straight into the editor.
- Optionally resize and compress them on import, so you stop shipping 6 MB screenshots.
- Store them next to the post, in a
public/folder, or upload them to any S3-compatible bucket. - The asset gallery shows every image in the workspace and, my favorite part, which ones aren't used anywhere anymore.
S3 credentials are encrypted in the config file with a key that never leaves your machine, so it's safe to commit .mditoor.json.
A small SEO check before you publish
Each post has an SEO panel with a search result preview and a short checklist:
- Title length
- Meta description length
- Clean URL slug
- A single main heading
- Uses subheadings (H2)
- Enough content (300+ words)
- Images have alt text
- Contains links
It gives you a simple score ("Looking great", "Almost there", "Needs attention"). It's not trying to be an SEO tool, it's just the stuff I kept forgetting.
Ideas board
Half my posts start as a random thought at 1am. The ideas board is a place to dump those, move them through stages, search them, and turn one into a real draft when you're ready. Ideas are saved in a .mditoor-ideas.json next to your posts.
DEV workspaces (yes, like this one)
Not everyone has a personal blog, and that's fine. Plenty of people use their DEV profile as their blog.
So you can create a DEV workspace, paste an API key from your DEV settings, and Mditoor will:
- Verify the account and store the key encrypted locally
- Import your existing articles
- Let you write drafts offline, saved locally first
- Sync with explicit Save to DEV and Publish on DEV buttons. Nothing goes out unless you click.
- Ask you which version to keep if the local and remote copies both changed
- Upload cover and inline images through your own S3 bucket, since DEV's API needs public image URLs
And if you do have your own site, there's cross-posting: send a post from your local project to DEV, with an optional canonical URL pointing back to the original. Good for SEO, good for not having to copy-paste.
Notes workspaces
The newest addition. Not everything I write is a blog post. Lecture notes, research, a journal, random wiki pages for myself.
A Notes workspace is just a folder of Markdown files, nested as deep as you want. You can start from a template:
- Empty: just the folder
- Study:
inbox/and a sample course folder - Journal: a folder per year with today's note ready
- Research:
papers/,ideas/,reading-list/
Notes get a lighter frontmatter form (title, tags, created date, status like todo / learning / done) instead of the SEO panel. There's a folder tree with breadcrumbs, search across every folder, and you can move a note just by editing its path. Folders can only be deleted when they're empty, so you can't nuke your notes by accident.
Want backup or sync between machines? Leave "Track with Git" on, paste a remote, and commit and push from the Git tab. Since it's all plain files, the folder also works fine with any other Markdown tool.
The small stuff
- Command palette with
Ctrl/Cmd + Kto jump anywhere - Auto-updates so you don't have to keep checking the releases page
- Resizable sidebar (double-click to reset)
- No tracking. The app makes no network requests of its own, except the git operations, DEV syncs and S3 uploads you trigger.
Where it runs
- Windows: prebuilt installer. This is my main platform.
- macOS: universal
.dmgfor Intel and Apple Silicon. Alpha, not tested as much. - Linux:
.AppImageand.deb. Also alpha.
Full disclosure: the builds aren't code-signed yet, so Windows SmartScreen and macOS will complain the first time. The README explains how to get past that, or you can build it from source.
Try it, break it, tell me
It's still early and I'm building it in my free time, so there are rough edges. That's exactly why I'm posting this.
- Website and downloads: mditoor.com
- Source code: github.com/ezzdin-atef/mditoor
If you try it, I'd really like to know what annoyed you. Bug reports, feature ideas, and especially help testing on macOS and Linux would mean a lot. And if you write in a right-to-left language, I want to hear from you most of all.
Thanks for reading.
