Contents
Three pages merged: the REST API, the staging and publishing route, and what to use instead.
REST API
WordPress exposes a REST API that can be driven from PHP, Node.js, Go, Java, Swift, Kotlin, and most other languages.
- Using the REST API
- Posting methods: the REST API itself, the miniOrange REST API plugin, or the older XML-RPC endpoint
- A site's posts live at
/wp-json/wp/v2/posts
Staging and publishing
The route being tested is Obsidian → GitHub → conversion → WordPress server.
Authentication uses application passwords rather than the account password. Generate one per client, store it outside the site, and revoke it when the client is retired — never commit one to a page.
Alternatives
Headless CMS and static site generators
Next.js (on Vercel), Gatsby (on Netlify), and Hugo all turn markdown — including an Obsidian vault — into a fast static or hybrid site, and all three integrate with ad networks, membership tools, and eCommerce plugins.
Monetization layers
- Memberful, Patreon, and paid Ghost supply embeddable membership, newsletter, and subscription commerce that bolt onto a static site.
- For heavy video, Dacast, Brightcove, Vimeo OTT, and Kaltura handle subscriptions, paywalls, and advertising.
Hosting
- Vercel and Netlify — global CDN, edge functions, custom domains, SSL, scalable bandwidth, analytics, SSO. The default pairing for a Jamstack wiki.
- Cloudflare Pages — deploys straight from GitHub, with DDoS protection, automatic SSL, and edge locations for low latency.
- AWS Amplify and Azure Static Web Apps — granular access control and authentication for static and dynamic apps alike.
Converting an Obsidian vault
- Pubsidian and similar open-source tools convert Obsidian markdown into pages ready to host on Netlify, Vercel, or AWS, and can run on every new page.
- Going the other direction, WordPress content can be exported, converted to markdown, and republished as a static site.
The short recommendation
Jamstack for the site (Next.js + Vercel, or Hugo + Netlify), a third-party membership or ad layer for revenue, and a markdown-to-HTML step — Pubsidian, Eleventy, or similar — to automate publishing from the site.