Did you see Tantek’s call to action at WordCampUS last November, but wondered how to get started?
Do you have a WordPress website where you want to better own and control your own data?
Do you want to use your own website to interact with other websites or even social media silos?
Are you a teacher or student and need a platform you control for communicating on the web while you’re stuck at home? Don’t want to rely on a toxic corporate social media site to do it?
David Shanske and I are hosting an IndieWebCamp pop-up session/workshop for WordPress beginners to learn a bit more about how to add some of the basic IndieWeb building blocks to their websites.
Whether you’re new to the process or have some questions about how to improve your site, stop by and join us this weekend.
Getting Started with WordPress, an IndieWebCamp Pop-up Session on August 1, 2020 at 9:30 – 11:30am Pacific. Everyone is welcome. RSVP at the event site or by replying on Twitter.
If you don’t already have a domain name or need help getting WordPress set up on a host, stop by one of the Homebrew Website Clubs this week or ask for some help in the IndieWeb chat so you can follow along at the workshop on Saturday.
July 25, 2020 at 09:30AM- July 25, 2020 at 11:30AM
The Micropub protocol is used to create, update and delete posts on one's own domain using third-party clients.
This session will be to iterate on proposed extensions to Micropub, listed on the Micropub-extensions page.
We will discuss which extensions can be moved to stable, try to better define those proposed, and to see who is willing to implement what proposal.
Saturday, August 1, 2020 9:30 – 11:30am (America/Los_Angeles)
This will be a broad-based introduction to the IndieWeb session specifically focused on using WordPress. Our aim is to help people get set up and running a self-hosted IndieWeb-based website with WordPress though some of our discussion will work for WordPress.com versions as well.
- Grab a cup of coffee and get an IndieWeb site up and running in just a few hours.
- Have questions or problems with your current WordPress IndieWeb site? Stop by and get some help.
- Just figuring out what IndieWeb is about? Much of what we’ll discuss is applicable to other platforms and may be useful to other beginners as well.
- All levels of experience welcome
- (Note: for those without a domain registered or web hosting, we may have a brief pre-session to help you out so we can be more productive during the main session.)
- Notes for the session will take place at: https://etherpad.indieweb.org/WordPressQuickStart
- Create week: Following the session, we’ll give people a chance to create something for their site to do remote demos.
- Demos: When we’re done, we’ll have a short online demo session so people can show off the new sites and maybe demo their favorite functionality.
Code of Conduct: indieweb.org/code-of-conduct
With traditional in-person two day camps on hold for the foreseeable future as the result of the coronavirus, doing some smaller one day or even one session topics seemed like a good idea at the time. After having done it once, I now think they’re an even better idea. A variety of things came out of the experience that I wouldn’t have anticipated.
I posted the notice for the event to my website and to events.indieweb.org about two weeks in advance. This helped give me enough time to invite about 15 people I expected to be interested in the particular topic. A few tweets as reminders helped in addition to the announcement being early enough to make it into two of the IndieWeb newsletters.
I held the session at 10am Pacific so that we might be able to draw people from the late evening time zones in Europe, mid-afternoon people on the East coast of the U.S. but still late enough in the morning so that people on the West coast of America wouldn’t have to be up too early. This seems to have worked out well though I feel bad that we did likely shortchange several people in India, Asia, and Australia who might have attended.
I expected that I would be starting out small and simple and honestly only expected about 3-6 people to show up. I was initially thinking a tiny, one-topic Homebrew Website Club, but on a weekend.
On the day of the event my guess was that we had about 25 attendees, but statistics after the fact showed that 35 people logged into the session. There were still people arriving into the room at the two hour mark! According to the numbers, there have already been 210+ views of the archived video since it was posted later on the day of the event.
I suppose that future sessions will give additional data to bear the hypothesis out, but one of the side-benefits of having a specific topic announced a few weeks in advance seemed to have brought in a large number of people interested in the particular topic and who were generally unaware of the IndieWeb as a group or a movement. I’ve seen several of these people at subsequent Homebrew Website Club meetups, so using these sessions to help spread the principles of IndieWeb does seem to have been generally useful. About half of the attendees hadn’t been to an IndieWeb event previously. I did try to start with a brief introduction to IndieWeb at the start of the session and offered some follow up at the end, but I probably could have planned for this better.
I wish I had collected people’s emails, but I’ll have to do this manually somehow if we do so now. The traditional signup and organization structure for full camps would have done this, but it would be nice to have a simple workflow for doing this on a lower key basis for pop-ups. Emails would also have helped to put together a post-event questionnaire to potentially create a follow up session.
Thanks certainly goes to all the people who have built pre-existing infrastructure and patterns for pulling off such an event so easily.
Since the session, I’ve gone into the IndieWeb wiki and created a stub pseudo-IndieWebCamp listing to help make organizing future stand-alone pop-up sessions a bit easier (particularly for documenting the results after-the-fact.)
The key is to make doing these as easy as possible from an organization standpoint. Having pre-existing pages on the wiki seems to help a lot (or at least feels like it from a mental baggage perspective).
Here are the relevant pages:
One of the things that was generally missing from the program was some of the hallway chatter and getting-to-know-you preliminary conversation. I think if I were doing another session I’d schedule 15 minutes of preliminary chat and dedicate about 30 minutes of introduction time into the process and encourage people to have a cup of coffee or drink to help make the atmosphere a bit more casual and conversational.
On thing that surprised me was that despite scheduling about an hours’ worth of time to the session we still had a sizeable crowd talking about the topic nearly two hours later. I think having more than just the traditional hour of conversation at a camp was awesome. It helped us not only dig in a bit deeper into the topic, but also helped in managing things given the larger number of attendees over the usual camp setting where 5-15 session attendees has been the norm. Doing it again, I might outline a three hour mini-event to allow covering a bit more material but still keeping things small and relatively casual.
I certainly benefited by the presence of a few old hands in the IndieWeb community showing up and helping out on the day of, particularly in terms of helping to manage Zoom infrastructure and format. A single person could certainly plan and execute a pop-up session, but I would highly recommend that at least two people show up to co-host on the day of the event, especially if the attendance goes over 10 people.
The IndieWeb Zoom set up prevents organizers from allowing users to share their screens during a session. (This issue has popped up in a few HWCs lately too.) This was potentially helpful in the earlier days when it was easier for zoombombers to pop into rooms and disrupt a conversation. There have been enough changes to Zoom with precautions built in that this part of the lock down probably isn’t needed any longer, particularly given how useful screen sharing can be.
Despite having many places to indicate RSVP’s I had very little indication of how many would show up. Something to improve this would be nice in the future, though isn’t necessarily mission critical.
I’ve definitely experienced the organizer decompression time required after putting together something big. I feel like there was less of the traditional post-event stress for this one session which allowed me to focus more of my time and attention after-the-fact on the content of the session and getting some work relating to it done. For me at least, I consider this a big personal win.
Traditional camps set aside day two for people to create something related to the session(s) they attended on day one. We didn’t do that for this session ahead of time, but I desperately wish we had created a better space for doing that somehow. Later on the afternoon of the session, I posted a note encouraging people to write, create, or do something tangible. I wish I had created a specific time for either the following day (or even a week later) for everyone to reconvene and do a short demo session as a follow up.
Simply having a blog section and demo page on the wiki did help encourage people to write, blog, and continue thinking and working on the session topic afterwards.
One of the things I’ve appreciated since the session is the level of conversation in the general IndieWeb chat rooms, on people’s blogs, and peppered around Twitter and Mastodon. Often when couched into a larger IndieWebCamp there are so many sessions and conversations, the individual topics can seem to be lost in all the hubbub. Fifteen sessions concentrated on one weekend is incredibly invigorating, but because all of the concentration was on just a single topic, there was a lot more focus and energy spent on just that one thing. I sort of feel like this concentration has helped to carry over in the intervening time because I haven’t been as distracted by the thirty other competing things I’d like to work on with respect to my website since.
There has been a lot of specific article writing about this one session as some camps get in entirety.
Perhaps pop-up sessions on broader topics and problems that haven’t had as much work or which have only one or two small examples may benefit from this sort of concentrated work by several people.
I do wonder what may have happened if we had had a broad conversation about the top level topic for an hour and a half and then broken into smaller groups for 45 minutes to talk about sub-topics?
In the end, the session went far better than I ever expected for the amount of time I invested into it. I definitely encourage others to try to put together similar sessions. They’re simple and easy enough to be organized by one person and they can be carried out by one person, though I’d recommend two.
I encourage others to suggest topics and set up other sessions.
Even if you’re not interested in the organization portion, why not propose a topic? Perhaps someone else with a more organizational bent will come along and help you make it happen?
I’m happy, as always, to help people plan them out and deal with some of the logistics (Zoom, Etherpad, wiki, etc.) should anyone need it.
Thank you everyone!
For those who attended yesterday’s, thank you for participating! I honestly only expected 4 or 5 wiki fans to show up, so I was overwhelmed with the crowd that magically appeared from across multiple countries and timezones.
I’ve heard from many–both during the session and privately after–that it was a fantastic and wide-ranging conversation. (I never suspected memory palaces or my favorite 13th century Franciscan tertiary to be topics of discussion.) Several have suggested we host not only a continuation of the session, but that they’d be interested in other pop-up IndieWebCamp sessions. If you’re interested in future follow ups or sessions shoot me a quick email (you can find it on my home page) and I’ll be sure you get an invite. You can also follow future events via events.indieweb.org or find them in the IndieWeb’s weekly newsletter that is emailed out every Friday afternoon.
If you’re interested in hosting or suggesting other topics for future sessions, there’s a stub page on the IndieWeb wiki for doing so.
Our session went on far longer than I ever could have anticipated and I suspect we could have easily gone all day and still not touched on a fraction of all the topics we all outlined. Special thanks to the larger majority of those who were interested enough and had the free time to stay well past the hour mark and on to the end. I will say it’s nice to be able to cover so much ground and so many ideas without the threat of 5 more sessions following you.
Video and Notes
For those who missed it and are interested or those who have inquired, the video link and the notes from the session have been posted to the IndieWeb wiki.
If you write up any notes or posts about the session, do add a link to them in the IndieWebCamp Pop-Ups page under blog posts/articles or photos. If you can’t log into the wiki (with your own website), feel free to ping me with the URL and I’ll add them for you.
I’ll try to write up an organizer’s post-mortem with a few ideas about doing future sessions for others to consider. I hope to rewatch the session myself and add to the growing list of notes and thoughts about it.
Because this was just a single IndieWebCamp-style discussion session and we hadn’t specifically planned a traditional creator’s day or hack day, I did want to throw out a small challenge to those who either attended or who are interested in participating.
For most, the IndieWeb is more about creating something than just talking about it. So in that spirit, I’ll challenge everyone to spend a few hours today/tomorrow or sometime this week and create something on your website or wiki related to the session. It can be a summary of ideas, a blog post about wikis (or anything you like really), a small change you’ve always wanted on your site (a CSS improvement, adding bi-directional links to your wiki, Webmention support, etc.), or anything else you might have found interesting from the conversation. The best part is that you can choose what you create on your own site! Make something you’ll use or appreciate. Have fun!
My personal plan for the challenge is to continue some work to my TiddlyWiki to support bi-directional links using TiddlyBlink. I might also take a crack at doing some design and building work to show some incoming webmentions on my TiddlyWiki. (If anyone is interested in test-driving Mike Caulfield’s implementation of Wikity on WordPress in conjunction with Webmention, I could be game for that too!)
Once you’ve made your creation, post a link to your article or notes or make a quick 2-3 minute demo video of the new feature or write up a post about it and add them to the IndieWeb wiki page for Pop-up Session Demos. Again if you can’t log into the wiki with your own website yet, drop me a note and I’ll add them for you or you can ask for help on how to do it in the IndieWeb chat.
Thanks again everyone! I look forward to seeing what you come up with.
cc:( ), ( ),