Building blocks are key design-patterns, technologies, and methods for building and improving your independent website.
See also: IndieMark, a way of measuring "how indieweb" is your website, and a good step-by-step guide to what feature(s) you should consider implementing next.
WhyWhy building blocks? This early quote from Tim Berners-Lee's Weaving The Web Chapter 4 page 39 summed it up well:
... if I had insisted everyone use HTTP, this would also have been against the principle of minimal constraint. If the Web were to be universal, it should be as unconstraining as possible. Unlike the NeXT computer, the Web would come as a set of ideas that could be adopted individually in combination with existing or future parts.
As was the Web, so is the IndieWeb.
The IndieWeb also comes as a set of (additional) ideas (as building blocks), that can be "adopted individually in combination with existing or future parts".
It is for these reasons that the IndieWeb is built with a set of building blocks, instead of on a monolithic "stack".
The act of having a personal website immediately creates an online identity which can be better established with:
Posts and variants are perhaps the building block of an indieweb site:
Stuff in/of posts:
The ability for one webpage to let another know the first has linked to the second is a vital indieweb building block.
The key mention technology for the indieweb is:
The ability to use your online identity (domain) to authenticate yourself on the web.
A web action is the interface and user experience of taking a specific discrete action, across the web, from one site to another site or application.
A link preview is what posts show about one or more embedded links, e.g. a headline, image, summary from the link destination.
A reply context similar to a link preview, except is the information that a reply post shows about the original post that it is in reply to. E.g. original post author (name, photo, link), original post content (or abbreviated summary).
- SWAT0 originally from the 2010 Federated Social Web Summit.
There are numerous historical building blocks which are no longer necessary (and in many cases, even supported) on the indieweb. They are listed here both as history, and to clearly communicate that each has been considered, and either rejected (e.g. Salmon), or iterated/improved upon (e.g. Pingback became Webmention).
- pingback & trackback - origins of webmention (which is also the replacement)
- salmon - was too complex/difficult for any more than a couple of implementations, unclear how much if any cross-implementation interoperability there ever was.
- OpenID - too difficult to consume. overly complex libraries often larger than the entirety of the rest of an indieweb implementation. too high a barrier for independent implementations.
- Historical significance:
- OpenID was the first even remotely practical federated URL-based identity protocol that gained adoption, and thus it helped explore a lot of URL-based-identity issues (UX and otherwise). Much of that experience informed the design of web-sign-in.
- OpenID was the URL-based-sign-in system used for this wiki and IndieWebCamp in 2011.
- Replacement: web-sign-in / indieauth, which have demonstrated better usability than OpenID.
- Historical significance:
Pages in category "building-blocks"
The following 33 pages are in this category, out of 33 total.