Opened 8 years ago
Last modified 4 years ago
#40852 new feature request
Support Micropub
| Reported by: |
|
Owned by: | |
|---|---|---|---|
| Milestone: | Awaiting Review | Priority: | normal |
| Severity: | normal | Version: | |
| Component: | General | Keywords: | |
| Focuses: | Cc: |
Description
Micropub is now a W3C Recommendation.
https://www.w3.org/TR/micropub/
It is used to create, update and delete posts using third-party apps.
Micropub uses OAuth 2.0 Bearer Tokens for authentication and uses traditional form posts as well as JSON posts, which is both simpler and more secure than an XMLRPC approach.
The REST API is specific to WordPress, whereas Micropub is platform agnostic, which has its advantages.
Change History (3)
This ticket was mentioned in Slack in #core by noisysocks. View the logs.
4 years ago
#3
@
4 years ago
Micropub continues to be a living standard(https://micropub.spec.indieweb.org/). The advantage of Micropub for WordPress would be wide support for posting to your site from a variety of clients that do not have to be built for WordPress. A recent example is photo posting app Sunlit for iOS(https://sunlit.io/).
While the API for Micropub uses the microformats vocabulary how the properties are published or ignored is up to the endpoint.
On a practical note, Micropub is a simple and customizable publishing standard that puts the rendering responsibility in the hands of the backend.
This was discussed briefly in a Core triage session today.
Upon reading the spec, I did have some question about whether microformats 2 were required (see #30783) but @dshanske clarified this was not the case.
As this is a large feature, it's probably best written up as a feature proposal and subsequently worked on as a plugin rather than going straight in to WP Core.