How Artur Piszek Uses Obsidian to Write for WordPress

Artur Piszek writes his WordPress posts directly in Obsidian, using a plugin called PushMD. The setup works like this: PushMD lets him git clone his blog content to his local machine as plain Markdown files, he edits those .md files in Obsidian, and when he pushes, the content is written into the WordPress database. Piszek describes this in his post "WordPress as Obsidian Sync" and says the post itself was written this way, with a setup guide included for anyone who wants to replicate it.

The three-part workflow

The process separates writing from publishing, with each tool doing one job:

1. Local copy via git clone

PushMD exposes the blog's content as a Git repository. Cloning it gives you a local folder of Markdown files — one per post, in plain .md format. This is the step that removes the need to draft inside the WordPress editor.

2. Editing in Obsidian

Because Obsidian works natively with plain .md files, the cloned folder can be opened as a vault and edited like any other note. You get Obsidian's linking, search, and editing environment while the files remain ordinary Markdown on disk.

3. Push to WordPress

When you push, the changes are written to the WordPress database. Piszek's summary is that "everything gets written to a WordPress database on push" — so WordPress remains the system of record even though the writing happened elsewhere.

What you need before starting

• A WordPress site where you can install the PushMD plugin.
• Git installed locally, and comfort with basic clone / commit / push commands.
• Obsidian installed, if you want the same editing experience Piszek uses (the files are plain Markdown, so other editors would also open them).

Piszek's post states that a full setup walkthrough is included; the exact menu locations and configuration fields are best taken from that guide rather than assumed.

How to verify it worked

After your first push, check two things: that the post appears in WordPress with your intended content, and that a subsequent git clone (or pull) returns the same Markdown you wrote. If both hold, the round trip between Obsidian and the WordPress database is functioning.

Common sticking points

• Git familiarity is the real prerequisite. The workflow is Git-centric; if cloning and pushing are unfamiliar, that is the part to learn first.
• Markdown fidelity. Since content lives as .md files, expect to confirm how your formatting renders once it lands in WordPress.
• Plugin dependency. The sync depends on PushMD being installed and working on the WordPress side.

Is this approach for you?

This setup suits writers who already keep notes in Obsidian, want their posts as portable plain-text files under version control, and are comfortable with Git. It is a poorer fit if you prefer drafting in the WordPress block editor, are not using Git, or cannot install the plugin on your site. For those cases, WordPress's own editor remains the simpler path.