Recent & UpcomingResources |
eventThis article is a stub. You can help the IndieWebCamp wiki by expanding it. 📅 An event is a type of post that in addition to a post name (event title) has a start datetime (likely end datetime), and a location. For information on IndieWebCamp events themselves, see:
WhyWhy publish indie eventsYou should post events on your own site to own your events and so your friends with indieweb sites can directly RSVP to you (as well as post invitations to others) without depending on a silo to mediate your event related interactions. Why POSSE eventsYou should POSSE copies of your events to the silos where your friends without their own indieweb sites keep track of their events and/or calendar. How toHow to markupEvent posts must be marked up with h-event. Optionally they can be wrapped in an h-entry as well (though it's not clear this is necessary). Parsers should be prepared to handle events without an h-entry tag. (sample event post markup with a top level How to provide an RSVP UIEvent posts should have webaction buttons for RSVP actions and inviting others. E.g.
See Facebook's RSVP UI: How to accept RSVPsA site publishing event posts should accept rsvp webmentions and update the event's attendance information accordingly. See: http://microformats.org/wiki/rsvp How to accept invitationsA site publishing event posts should accept invitation webmentions and update the event's "invited" information accordingly.
How to limit capacitySome events have limited capacity and want to offer "tickets," ie only accept the first N RSVPs. To do this, the site that hosts the canonical h-event should set the capacity. When it renders the event, it should show the space remaining based on its current number of It should handle RSVP webmentions for the event in serial. When it gets a The host could also put overflow yes RSVPs on an ordered waiting list, mention that in the reject message, and automatically upgrade people on the waitlist when existing yes RSVPs are withdrawn. IRC discussion of whether/how this fits into the webmention spec. IndieWeb ExamplesIn implementation order: Ben Werdmuller
Aaron Parecki
Bret ComnesBret Comnes has implemented events inside of jekyll for bret.io since 2013-07-25. It supports receiving webmentions, but does not parse responses for RSVP status or display reply contexts at the moment. Example:
The event data is stored in the YAML which separates the final layout and the event data. A form is used to assist in creating the event post via prose.io. Jeena
Ryan BarrettRyan Barrett is manually posting events inside article posts on snarfed.org since 2014-01-15. Examples:
Kyle Mahan
gRegor Morrill
Shane Becker
IndieWeb ItchesThe following people either strongly want to implement events on their site, or are in the process of doing so, you may find some implementation clues in their notes Tantek
Prototype event as a note:
Amy Guy
Staged implementation[2]
BrainstormingAs ideas here are implemented, they should be moved to actual sections of their own with links to examples. Image headerTypical silos event posts (e.g. Facebook, Google+) provide (encourage) the option of an event image - used as a header for the event. This header is used at the top of the event permalink page, and also often shown in an event list view (e.g. on Facebook). Such header images are often quite a good visual/emotional draw for the event. Header images are typically representative of the event, sometimes displayed with the name of the event superimposed on top. If you're posting events, consider providing this option for yourself (in your event posting UI or otherwise as part of your publishing system) as part of your indieweb event posts as well. Since the photo would be deliberately chosen to represent the event, we could extend h-event to represent the photo as well with:
Note that Screenshots needed Map imageSome silos event posts (e.g. Facebook, Plancast) automatically generate a horizontal rectangle map view of the event location. In particular, on event posts, the location is shown *first* as a centered dot in a wide and short rectangle map that shows the local area, and then second underneath as text address. Showing a map and showing it early is both visually striking and instantly provides a sense of "is this near me", or "is this near somewhere I'd like to be or might be anyway". It quickly gives you context in a way that a purely textual address does not. Screenshots needed A horizontal map (banner map?) from a Facebook event:
AttendeesEvent posts should display attendees, RSVPs in general, and invitations. There are two typical existing approaches to displaying RSVPs:
Clusters are typically displayed as facepiles, either entirely, or abbreviated at some fixed number with a method to expand / view the whole set. Time order presentation usually include some text about the RSVP, e.g. "is going", "is attending" Silo AttendeesEvery event silo by default shows who else is has RSVPed that yes they're going, and more so, often first display who you know that's going to the event. Quickly seeing "who else is going" or might go or is invited is a huge sense of context/comfort as well, especially with little face icons. E.g. Facebook clusters (potential) attendees by:
(and declined is typically hidden) More screenshots needed Event attendees on Facebook:
Note the going/maybe/invited sections on FB first show *only* those you know (if any), and *only if* there's no one you know in a section, does the section show 5 icons of others who said they're going/maybe or were invited. In either case, the order of icons is most recently responded/invited first. Public events don't necessarily have a public list of invited users, depending on the system, but nonetheless list attendees. For example, on Plancast:
Plancast only shows invitees on an event to the event organizer, i.e. when the event organizer themselves is looking at the event permalink page. InvitationsMain article: invitation
People like being explicitly invited to events. One way to send invitations with indieweb events is:
The idea is that a person's site's webmentions queue sees webmentions from the event to the home page and interprets that as an invitation to the event. If needed we could add some markup like Also see indieweb messaging, which also uses a webmention to the user's homepage. POSSEHow and where should event posts be POSSEd?
Event-aware destinations to consider: POSSE to EventbriteEventbrite - has best API for creating events, getting updates, perhaps backfeeding attendees etc.
POSSE to FacebookFacebook - likely has broadest reach of people you might want to explicitly invite
POSSE to LanyrdLanyrd - has an API for creating events, getting updates, backfeeding RSVPs POSSE to PlancastPlancast - event-specific silo POSSE to Google+Google+ - another silo that has explicit event posts, but has enough challenges to be considered problematic:
POSSE to TwitterDespite not supporting event posts per se, Twitter is worth considering as a POSSE destination.
Events indexIndieweb sites with event posts (and perhaps even just RSVP posts) could also provide an index of what events they're attending, e.g.
From a human design perspective this makes sense as:
which is likely a union of personal event posts and RSVP yes (and maybe maybes too?) posts. Kind of like a view of your public calendar of events, regardless of whether you're organizing/hosting or just attending. Such an events index could be displayed as a list view (similar to the default view of fb.com/events) or as a calendar view (like gCal), or with an option to toggle between them. An easily-discoverable link should probably be displayed from the user's index or homepage.
Markup designMarkup for an h-event on a site must include a number of properties to enable presentation and user interaction as implied by some of the above brainstorming, and some of the better silo UX as documented in "Silo Examples" The following fields/properties are necessary in the markup somewhere:
Markup example:
Response context CRUDSimilar to the general reply context: CRUD protocol, when an event changes (name, location, times, description, etc.) you should send webmentions to all the responses to the event that you've accepted, e.g. to all:
What about when an event is cancelled? Options:
Silo ExamplesAttendingMain article: Attending
Attending is a nice looking event silo that allows RSVPing via Twitter, Facebook, LinkedIn, and email. Redesign 2015Sometime in 2015, Facebook redesigned their events presentation again, which in many ways seemed to regress even more, especially in the mobile web view: Mobile Web UI:
Redesign 2014-02-27Here is what the 2014-02-27 redesign (limited rollout as of that date, but subsequently broadly rolled out) looks like:
Before 2014-02-07This was perhaps the pinnacle of Facebook's event page design. Facebook has had one of the more interesting/nicer/cleaner event page designs for quite some time. Here is a screenshot of the 2014-02-12 Homebrew Website Club event (for the SF location) on Facebook, manually POSSEd by Ben Werdmuller from http://werd.io/2014/homebrew-website-club-meeting :
Before 2014Facebook pre-2014:
SessionsIndieWebCamp sessions about events:
See also |
Thank you to our sponsors of IndieWebCamp events!
