|
|
||
|---|---|---|
| .github/workflows | ||
| docs | ||
| src | ||
| .editorconfig | ||
| .eslintignore | ||
| .eslintrc | ||
| .gitignore | ||
| .npmrc | ||
| .tool-versions | ||
| CHANGELOG.md | ||
| esbuild.config.mjs | ||
| LICENSE | ||
| main.js | ||
| manifest.json | ||
| package-lock.json | ||
| package.json | ||
| README.md | ||
| styles.css | ||
| tsconfig.json | ||
| version-bump.mjs | ||
| versions.json | ||
obsidian-wordpress
This plugin makes you publish Obsidian documents to WordPress.
There are some introduction videos you can watch:
Usages
Set your WordPress URL in settings as well as username if you want.
Put cursor in a MarkDown editor, then use Publish to WordPress in Command Palette or you could show a button in side in settings. The document will be published to the WordPress URL that you set.
You could add YAML front matter in front of notes. The plugin will read meta-data from front matter such as override title or tags. Also, WordPress post ID and categories will be added to this front matter if the note published successfully in order to support edit.
For example, you could add as following:
---
title: Post title which will override note title, not required
tags:
- any tag you want
- not required
---
Note content here.
Limits
This plugin uses XML-RPC or REST protocol to publish to WordPress.
XML-RPC is enabled by default but some sites may disable it because of security problems. While some shared hosts might disable XML-RPC by default which you have no way to enable it. So this won't work if XML-RPC is disabled.
REST API is enabled since WordPress 4.7 by default. Some REST API need extra actions in order to protect writable APIs. Traditionally, it is done by installing plugins. WordPress 5.6 was introduced application passwords to do similar things. So if you are OK with WordPress 5.6, application passwords is preferred as no plugin in needed.
Read this page for more information.