I am writing this post directly in Obsidian. A git clone of my blog sits on my laptop, and obsidian works with plain .md files. Everything gets written to a WordPress database on push.
Introducing PushMD
This workflow is possible thanks to the PushMD plugin we wrote with Adam. The plugin exposes a git remote url via wp-rest. This allows you to commit, push and pull to sync entire blog content.
All workflows including git will have some sort of script or Github action to sync with an external repository. In PushMD, your website is the repository.
- Your entire content will be checked out locally as .md files (and more)
- Your agents can see your entire website at once, use file operations to edit and read content and resolve conflicts in a git way
- WP-Admin users can work together with multiple other clients
- You can sync arbitrary private markdown content (like your obsidian vault)
I checked out my entire website with this one-liner:
git clone https://arturpiszek@piszek.com/wp-json/git/v1/md.git
Guidelines
The upcoming changes in WordPress Core will introduce Guidelines: a predefined storage for Instructions, Skills, Memory and Artifacts.
PushMD is already compatible, which means AGENTS.md or Skills in WordPress end up in your agent configuration.
Artifacts
Artifacts is a special type for arbitrary content – this is where you can store your private notes that you never intend to publish (like your obsidian vault.)
WordPress as your personal cloud
WordPress is your home on the web – and not everything in your home needs to be public. PushMD is another way to connect it to everything everywhere.