Post or posts may refer to:
Having multiple posts on your own site is a requirement for IndieMark Level 1.
Individual items published on an indieweb site.
How to publish a post.
Why you should publish posts on your own site: see why.
Kinds of Posts
Experience has shown that there are different kinds of posts on indieweb sites, and publishing and display interfaces for them vary by type. ActivityStreams has a similar concept of "object types". Here are a few kinds of posts that indieweb community members are currently publishing:
Roughly ordered by apparent/anecdotal indieweb posting frequency:
Indieweb community members are working on publishing these real soon now:
Merely gleams in various eyes:
Inferring post kinds from properties
Alternative perspective: instead of explicit post kinds, infer the post kind (and thus presentation/UI) by what aspects/properties a post has. E.g.:
Obviously combinations of the above will have to be explored to see if they make sense, and given multiple possible inferred post kinds, which should "win" in terms of driving the presentation/UI.
Some of this is also noted/documented in http://aaronparecki.com/articles/2012/10/22/1/creating-content-on-the-indie-web#indieweb-posts.
New Post Types
In general, we should avoid creating new post types/kinds.
Both individually and as a community. Simpler is better and all that.
The key is whenever you think you have something new to post, try posting it as your simplest existing post type, which are likely just notes, maybe with tags, e.g. what User:Waterpigs.co.uk does with steps, and User:Sandeep.io does with tags as well. Then document here on the wiki why/how that doesn't work if you run into problems.
One reason why re-using an existing post type might "not work" is that you really want to present it differently, provide a specific UX for a particular kind of posts differently from any existing post type. This is the *primary* reason that should drive any desire to create new post types.
If there's no reason to present a different UX, then you likely shouldn't be thinking about a new post type.
And even if you do want to present a different UX, consider simply using the existence of specific properties (e.g. in-reply-to for replies) to drive the presentation of a different UX, rather than creating a new post type.
If you get that far, step one, document real world examples of such new UX (even from silos) with screenshots/mockups embedded on this wiki.
Pieces of a Post
At a minimum, indieweb posts should have:
Additional information about the post:
Footer sections. Posts sometimes have footers with links, references etc. Here are few known footer sections with a real world indieweb example in the wild of each.
IndieWeb community members' thoughts on some of the details of how they post and why:
There's many ways to style and display posts, on their own on permalink pages, as part of a stream (e.g. a home page or feed), and in a collection in an archive.
Here are some posts about post display design:
Posts about the IndieWeb
Main article: Posts about the IndieWeb