I have a few questions about support for additional parts of the Micropub spec while I’m working on converting a site to Micro.blog
Setting summary
The summary
field, which is part of the Micropub spec, would be useful so long posts in the main timeline can show a brief overview instead of the full article (while still having precise control over the content of the summary instead of relying on Hugo’s autogenerated summary). As far as I can tell, it’s ignored. Is it possible to add a summary/excerpt content with any Micro.blog API or plans to support including a summary
param on the Micropub endpoint?
Setting the post type
q=config
on Micro.blog’s Micropub endpoint says it includes support for post types including note
, article
, and photo
, but it doesn’t seem to include a type other than post
as a param available to templates, which makes it difficult to query by type for theming/filtering. With Indiekit
, for example, a type
param can be set. It seems other folks have used mp-type
. Is there a way to set the type through the Micropub endpoint?
It would be nice if there were a way to explicitly set the type when creating a post and have Micro.blog use the algorithm for Post Type Discovery and include the inferred type in posts params when the type isn’t explicity set.
mp-slug
Not a part of the spec, but a common extension many Micropub servers support (e.g. Indiekit, the Micropub plugin for WordPress, etc).
Micro.blog does not support this as far as I can tell and it would be helpful when migrating posts, but also nice to have more control over the URL that is displayed.
Custom fields
Barring support for these specific fields, other Micropub servers seem to save any extra params as properties of the item being created. So passing, e.g. type=article
would make that available at .Params.type
w/o Micro.blog having to have specific support for that param (not sure that’s best approach, but it’s an idea )
Appreciate any insight/feedback/help the community has