- 2016-08-27..28 IndieWebCamp NYC2 (New York City, New York)
- 2016-11-04..06 IndieWebCamp LA (Santa Monica, CA)
See events for more upcoming IndieWeb related events (IndieWebCamps, Homebrew Website Club, IndieWeb talks at conferences etc.)
Photos from previous IndieWebCamps!
- Flickr indiewebcamp OR indieweb - please feel free to link/embed photos from sessions on their respective pages!
IndieWeb Summit 2016
- When: to
- Where: Portland, Oregon
- URL: http://indiewebcamp.com/2016
IndieWebCamp Düsseldorf 2016
- When: to
- Where: Düsseldorf, Germany
- URL: http://indiewebcamp.com/2016/Düsseldorf
IndieWebCamp Nuremberg 2016
- When: to
- Where: Nuremberg, Germany
- URL: http://indiewebcamp.com/2016/Nuremberg
IndieWebCamp MIT 2016
- When: to to
- Where: MIT, Cambridge, MA
- URL: http://indiewebcamp.com/2016/MIT
IndieWebCamp NYC 2016
- When: to
- Where: Mozilla NYC, New York City, NY
- URL: http://indiewebcamp.com/2016/NYC
IndieWebCamp SF 2015
- When: through
- Where: Mozilla SF, 2 Harrison st., San Francisco, CA
- URL: http://indiewebcamp.com/2015/SF
IndieWebCamp MIT 2015
- When: through at
- Where: Room G882, MIT Stata Centre, 32 Vassar St, Cambridge, MA
- URL: http://indiewebcamp.com/2015/MIT
IndieWebCamp Edinburgh 2015
The first IndieWebCamp in Edinburgh, but just one of many IndieWebCamps!
The importance of owning your data is getting more awareness. To grow it and help people gettings started, we're meeting for a bar-camp like collaboration in Edinburgh for two days of brainstorming, working, teaching, helping.
Join us in Edinburgh and learn how to use open web technologies to empower and – maybe more importantly – encourage users to own their own content and identities.
IndieWebCamp Portland 2015
IndieWebCamp Portland 2015 was the 5th annual main IndieWebCamp!
- When: to at
- Where: ESRI PDX, Portland, Oregon.
- URL: http://indiewebcamp.com/2015
- Cost: Free
- 2015 Schedule for session notes.
- 2015 Guest List
- 2015 Demos
- IRC Logs 2015-07-11, 2015-07-12
Major milestone: We achieved full SWAT0 interoperability across three different implementations running on three different personal sites, by people using them in three different cities!
IndieWebCamp Brighton 2015
IndieWebCamp Brighton 2015 is one of many IndieWeb events.
The importance of owning your data is getting more awareness. To grow it and help people get started, we're meeting for a bar-camp like collaboration in Brighton for two days of brainstorming, working, teaching, and helping.
Join us in Brighton and learn how to use open web technologies to empower and – maybe more importantly – encourage users to own their own content and identities.
IndieWebCamp Germany 2015
IndieWebCamp Germany 2015 is one of many IndieWeb events.
Own your data.
Rather than posting content on third-party silos of content, we should all own the content we're creating. Publish on your own domain, and syndicate out to silos.
Join us at sipgate for two days of a BarCamp-style gathering of web creators building and sharing open web technologies to empower users to own their own identities & content, and advance the state of the indie web!
IndieWebCamp Cambridge 2015
IndieWebCamp Online 2014
IndieWebCamp Cambridge 2014
IndieWebCamp UK 2014
IndieWebCamp 2014, the first main IndieWebCamp held simultaneously in three locations (Portland, New York City, Berlin), took place on and across all three time-zones continuously. See the Guest List for who participated.
IndieWebCamp NYC 2014
- 2014/NYC Schedule for session notes. Click on the session title to add notes to the page. To see all session notes, see Category:Session Notes
- 2014/NYC Sessions
- 2014/NYC Guest List
- 2014/NYC Planning
- 2014/NYC Demos
- IRC Logs http://indiewebcamp.com/irc/2014-04-26, http://indiewebcamp.com/irc/2014-04-26.
IndieWebCamp SF 2014
- 2014/SF Schedule for session notes. Click on the session title to add notes to the page. To see all session notes, see Category:Session Notes
- 2014/SF Sessions
- 2014/SF Guest List
- 2014/SF Planning
- 2014/SF Demos
- IRC Logs http://indiewebcamp.com/irc/2014-03-07, http://indiewebcamp.com/irc/2014-03-08.
IndieWebCamp Hollywood 2013
IndieWebCamp UK 2013
IndieWebCamp UK 2013, the second IndieWebCamp in the UK, took place on and immediately following dConstruct 2013 on 6 September. See the 2013 UK Guest List for who participated (see also: listings on lanyrd, Lighthouse, and Brighton Digital Festival)
IndieWebCamp 2013, the third IndieWebCamp in Portland, took place on and immediately following OSBridge 2013 on June 18-21. See 2013 Planning for how we made it happen and the 2013 Guest List for who participated (see also: listings on calagator, lanyrd, and plancast)
- 2013 Schedule for session notes. Click on the session title to add notes to the page. To see all session notes, see Category:Session Notes
- 2013 Sessions
- 2013 Guest List
- 2013 Planning
- 2013 Demos
- Photos from the Classof2013
- IRC Logs http://indiewebcamp.com/irc/2013-06-22, http://indiewebcamp.com/irc/2013-06-23.
IndieWebCamp UK 2012
IndieWebCamp 2012, the second IndieWebCamp, took place on and immediately following OSBridge 2012 on June 26-29. See 2012 Planning for how we made it happen and the 2012 Guest List for who participated (see also: listings on calagator, lanyrd, and plancast)
- 2012 Schedule for session notes. Click on the session title to add notes to the page. To see all session notes, see Category:Session Notes
- 2012 Sessions
- 2012 Guest List
- 2012 Planning
- 2012 Demos
- Photos from the Classof2012
- IRC Logs http://indiewebcamp.com/irc/2012-06-30, http://indiewebcamp.com/irc/2012-07-01.
IndieWebCamp 2011 was on and immediately following OSBridge 2011 on June 21-24. See 2011 Planning for how we made it happen. Check out the amazing Demos that were worked on in Day 2 of IndieWebCamp 2011.
How to organize
How to organize an IndieWebCamp.
Consider first organizing a Homebrew Website Club meetup
To organize an IndieWebCamp, you need:
- 2-4 organizers - in practice that's worked best.
- only 1 organizer means more chance things get dropped on the floor
- having co-organizers helps keep mutual motivation going, everyone encourages everyone else
- 2 is the minimum viable: 1 for physical venue stuffs, 1 for virtual stuffs is a good split to start
- 4 is what 2011 had
- More than 4 hasn't happened in practice.
- Add to Planning even if you just want to start the idea, add it to Planning
- Simple wiki page with the year and city. Start with just minimal notes and questions, e.g. see the first version of 2014/NYC.
- If your event is multiple days, have notations for what portion people will attend for.
- Divide up key organizing responsibilities (venue, sponsors, food, tables/chairs, volunteers)
- Venue with network access (donated / sponsored)
- Sponsors (see recent IndieWebCamps for an explicit list) for:
- travel assistance (see 2016.indieweb.org example)
- kid related or child care (note available upon request (e.g. ), make preparations for all day both days)
- Update wiki page as more is known, including creating subpages
- Track venue capacity, waitlist if necessary
- Remind Attendees, send out some sort of notification/email/text to all attendees and remind them of the event in advance.
- See message-before-iwc for message templates to use!
- Surge Protectors/Power Strips/Extension Cords - We all need power, and best to make it easy to secure.
- Displayport Adapter
- Markers (for nametags)
- Large Postit notes/papers for scheduling
- Video streaming kit and microphones.
When actually doing the IndieWebCamp, you need to at least do:
- venue tables/chairs/projectors/whiteboards/session grid setup
- food/snack/coffee delivery (or bring in)
- do the Introductions session
- organize sync-up for lunches/dinners/coffee
- take photos
- run the demo session
- set up a main Etherpad for the event and direct participants to How to take notes during IndieWebCamp
- organize collaborative cleanup and return venue to a cleaner state than when you showed up
After (or during if you can keep up)
- upload & post photos on the wiki
- make sure session Etherpads are captured into session notes archives pages on the wiki
- apply information learned from sessions to topical pages on the wiki
Tips for having a better, more effective, enlightening, productive, inspiring IndieWebCamp experience. Please share yours in === subheads === !
Try to get a feel for the general experience level of the participants. Should there be an introductory session to microformats? Did people just drop in because they want to start running their own website?
Sitting down with people who are new to the web can be extremely beneficial for more experienced developers. When was the last time you had to explain closing HTML tags? Or how to change the font size of some text? This will also enable people to better understand the hurdles others face when they first try to start their own website.
Teaching can be your hackday goal. Maybe you do not get anything done on your own site, but someone else gets their first domain and self-written page of HTML online!
You might have to offer teaching someone. If they say they don’t want to keep you from your own project, make it clear to them that you do not mind. Keep lowering the bar.
Enable people to ask questions
People might not want to ask questions when they see everyone being busy with personal projects during hackday. Try to break the ice for them by having more seasoned people stand up and declare what they will help with. Let it be clear that they do not mind being interrupted with questions.
Are there any people willing to help setting up HTTPS? Are they willing to make time? Let them call this out. Or maybe there are people who have extensive experience with WordPress? And others are just getting started having their own website and have chosen to use WordPress? Point them at each other.
Why is there a high bar for registering
Q: Why is there a high bar for registering for an IndieWebCamp event? (signing in using IndieAuth and adding yourself to the wiki)
A: In short, because we have very high respect for IndieWeb creators and especially for their time.
IndieWeb creators that participate in IndieWebCamp create (code/UX/design/style/graphics) and openly share & contribute at least some of their creations.
Longer: to see if IndieWebCamp is right for you. See also: Who is the audience for IndieWebCamp.
Every aspect of signing up for IndieWebCamp has been deliberately designed for you and other creators to be maximally productive during your scarce and valuable time at IndieWebCamp.
- Personal site passion. IndieWebCamp is focused on the IndieWeb and those that are passionate about it firsthand.
- Are you passionate about having & using your own website for your identity and your content?
- Then IndieWebCamp may be for you!
- Having a personal site. Having a personal site shows that you're willing to invest the few minutes it takes to buy a domain and set it up. Want to but don't know how? Check out Getting Started. Which brings us to:
- Interested in learning. IndieWebCamp is for folks hungry to learn about how to make themselves even more independent on the web.
- Ok asking for help. IndieWebCamp is a community which partly means we help each other out, which definitely means that asking for help is strongly encouraged!
- Are you ok with asking for help?
- Did you get stuck with any part of Getting Started?
- Did you ask in our Chat Forum?
- If you're in one of the cities they happen, did you come to Homebrew Website Club to get started?
- We are building a community of people who are comfortable with admitting they don't know everything, and thus actively ask questions. Which is also another indicator of interested in learning.
- Setting up IndieAuth. This takes mere minutes, with the help of Getting Started, and if you get stuck, our chat forum. By spending just a few minutes setting up your site with IndieAuth, you demonstrate that there's a much better chance you will be productive for several hours at IndieWebCamp, both with working on your own site, and hopefully with collaborating with other such creators as well!
- Adding yourself to the wiki. This also takes mere minutes, and very importantly demonstrates that you are willing to make at least small edits to the wiki.
- IndieWebCamp as a community thrives and depends on community contributions of time:
- to setup and run IndieWebCamps
- to lead and participate in sessions
- to take collaborative notes in Etherpad
- but most importantly, to contribute to our community wiki.
- By wikifying, yourself, session notes, and helping improve subject matter pages, you demonstrate that you're not only interested in the IndieWeb, but in IndieWebCamp as a community, and that commitment to community is important to us.
- If that's not your thing, that's ok too, you may use all of the resources on the IndieWebCamp wiki for free, CC0, because that's how strongly we believe in this community.
- We do want you to benefit from the wiki, regardless of whether you contribute to the wiki or not.
- IndieWebCamps events themselves are specifically for this community, for those that believe in contributing to and helping to grow an intentional positive community, and enjoy doing so.
- IndieWebCamp as a community thrives and depends on community contributions of time: