Post or posts may refer to individual pieces of content published on an indieweb site such as notes, articles, & responses, or the act of creating the aforementioned content (present tense), or Posts about the IndieWeb.
In list form:
Having multiple posts on your own site is a requirement for IndieMark Level 1.
Why you should publish posts on your own site: see why.
How to publish a post.
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. Here are a few kinds of posts that indieweb community members are currently publishing:
Roughly ordered by apparent/anecdotal indieweb posting frequency across different sites / implementations:
Posted by only a couple of indieweb sites so far
Posted by only one indieweb site so far:
Posts of various types may also be implicit mentions of other posts by linking to them, but the difference only matters to the receiver — i.e. there is no dedicated UI for people to publish a “mention” of something.
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.:
The above list is very roughly ordered and likely requires implementation experience (of multiple post types/kinds) to better understand which properties should more primarily determine a post type than others.
Combinations of the above will also 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. E.g.
Articles about implied post types
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.
After you've documented existing UX of a post type, see if you can find something similar in ActivityStreams's similar concept of "object types", and thus re-use their name/terminology.
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.
Inline and other references
Some post to other post or page references are inline in a post or elsewhere but not in a separate footer per se.
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:
Here are some tools for testing indieweb posts: