內容簡介
Push MD 將 WordPress 內容轉換為 Git 遠端，允許使用者以 Markdown 格式編輯文章和頁面，並透過 Git 工作流程進行版本控制，保持 WordPress 的主控權。
【主要功能】
• 支援將 WordPress 內容克隆為 Markdown
• 允許在本地編輯文章和頁面
• 提供標準 Git diffs 進行變更檢查
• 支援拉取 WP-Admin 編輯內容
• 維持 WordPress 角色和修訂歷史
• 兼容區塊主題檔案和 Gutenberg 指導方針
外掛標籤
開發者團隊
② 後台搜尋「Push MD – Git Sync for WordPress Content」→ 直接安裝（推薦）
原文外掛簡介
Push MD makes WordPress available as a Git remote for supported content. Posts and pages can be cloned as readable Markdown, edited in a local editor or coding-agent workspace, committed, and pushed back through WordPress.
WordPress stays in charge. Push MD reads and writes through WordPress APIs, checks the current user’s capabilities, creates WordPress revisions for accepted content changes, and rejects stale pushes before they can overwrite newer WP-Admin edits.
This gives Markdown-first teams and coding agents a Git-shaped workflow without moving the source of truth out of WordPress.
Beta: Push MD is an early release for experimentation. Try it on a staging site first and keep your normal WordPress backups in place.
What you can do
Clone supported WordPress content with a normal Git client.
Edit posts and pages as Markdown.
Review changes with standard Git diffs before pushing.
Pull WP-Admin edits before continuing local work.
Let authenticated coding agents work in an ordinary checkout.
Keep WordPress roles, revisions, previews, publishing, and rendering in the loop.
Work with block theme files, Global Styles, and Gutenberg Guidelines when available.
How it works
The Git endpoint on a site with Push MD active is:
/wp-json/git/v1/md.git
The repository branch is trunk. Push MD accepts pushes to trunk only.
Users authenticate through WordPress REST authentication. The built-in WordPress Application Passwords feature is the usual Git-over-HTTPS option, and other REST authentication plugins can work when they authenticate the request as a WordPress user before Push MD’s permission checks run.
A checkout can include:
post/{slug}.md for posts.
page/{slug}.md and page/{parent}/{child}.md for pages.
wp_template/{slug}.html and wp_template/{theme}/{slug}.html for templates.
wp_template_part/{theme}/{slug}.html for template parts.
wp_navigation/{slug}.html for navigation posts.
wp_theme/{theme}/theme.json as read-only context.
wp_global_styles/{theme}.json for editable Global Styles overlays.
wp_guideline/skills/{slug}/SKILL.md for Gutenberg Guidelines skills and Push MD’s built-in agent skills.
AGENTS.md, CLAUDE.md, .agents/skills, and .claude/skills for agent guidance when available.
Markdown files use a small front matter contract: title, date, status, and optional description. File paths identify content.
Structural block files use raw Gutenberg block markup with no front matter so they can round-trip through WordPress without being forced into Markdown.
Safety model
Push MD is designed to fail closed. Before applying a push, it validates the changed files across the pushed range. If any file or later commit is unsafe, the whole push is rejected before WordPress content is changed.
Push validation rejects stale remote state, unsupported paths, path traversal, malformed front matter, invalid block markup, invalid Global Styles JSON, and edits to read-only theme JSON.
Deleted post and page files move the matching WordPress content to trash instead of permanently deleting it. Re-adding the same path restores the trashed object instead of creating a duplicate.
Template, template part, navigation, and Global Styles deletes or renames are rejected until reset semantics are explicit.
Try a read-only demo
You can clone the public read-only demo remote before installing Push MD:
git clone https://pushmd.blog/wp-json/git/v1/md.git my-site
That demo lets you inspect the file tree and Markdown shape. Pushes require Push MD on your own authenticated WordPress site.
