MicroPub API

[TomboFry]

This would mean any editor (such as quill, for example) could be used to create posts. This is arguably more important than the admin control panel #5

• [x] Supports x-www-form-urlencoded or multipart/form-data
• [x] POST to /micropub for h=entry
  • [x] h = entry
  • [x] name - If not provided, assume type is note, otherwise article
  • [x] content for the main post content
  • [x] summary - Make a max length of 160 for open graph? If not provided, take a snippet from content
  • [x] photo (if file not provided)
  • [x] in-reply-to, repost-of, like-of URLs
  • [x] category[] for tags
  • [x] mp-slug for manual slug entry (must return an error if the slug already exists).
• [x] POST to /micropub using JSON Content-Type
  • [x] Parse same items as above but ensure they are single element arrays
  • [x] content may contain html key to create post as HTML.
• [x] Create post, returning HTTP 201 status
• [x] Update post, using action=update and returning HTTP 204 status
• [x] Delete post, using action=delete and returning HTTP 204 status
• [x] Requires authentication of user - must be same user as is hosting the website.
  • [x] Create auth/callback script which validates the user via an IndieAuth site Almost, but this is not being implemented anymore (well, for now, at least).
• [x] Support q=config to return media endpoint and syndication (maybe)
  • [x] Return empty JSON object {} in the meantime, while neither of these features are implemented.
  • [x] Support further additions to the GET micropub?q=[...] routes using micropub extensions

[TomboFry]

The Micropub API is now in a working state, with access token verification performing successfully too! This means one could potentially use Microlight in a production environment. Don't quote me on that though :sweat_smile:

[TomboFry]

The last two tasks (updating, deleting posts) are dependant on #3 being completed, as there is currently no way to update posts within the database.

[TomboFry]

Post updates finally completed, as of 172efb3