The IndieWeb has a terminology for common post types - such as article, note, photo and so on. The authors have also focused on developing specifications as opposed to a bunch of products/services. They encourage the community to write products implementing these specs.
This is a double-edged sword.
However well-written the spec may be, the success of the idea is up to the community. Don’t get me wrong - this is great for the long term; but software in open source or open development often moves slow, which increases the odds of friction in the short and medium term for the average Jane setting up a blog.
For example, Omnibear doesn’t even exist on the Firefox extensions store anymore, IndieKit is a personal project — of Paul Robert Llyod — open-sourced so one is primarily on their own once an issue is encountered. Much of what I came across carried similar downsides or caveats.
Personally, I have had almost no success implementing all these post types on my static site. The only suitable Micropub endpoint I found for myself was IndieKit, which I referenced above, but could not get it working with Indigenous for Android. I am not in favor of using 2+ distinct applications to post individual post types either, which seems to be the case when it comes to photos, for example.
Still, I want to leave room for adoption of these post types in the future. With that in mind, in place of notes, I am going to be writing thoughts. They might lack finish of course, but I also wanted to keep my articles separate from my thoughts. The thoughts also syndicate on my existing feed so you don’t need to do anything extra on your end.
When I feel the ecosystem around IndieWeb is mature enough for an average front-end developer to use, I’ll retire thoughts and adopt the post types as mentioned on their wiki, including notes.