Thinking about sessions for the #IndieWeb Summit

As I am wrapping up my two week experiment with going all-in on #IndieWeb WordPress I have had the pleasure of learning from so many great people. I recently discussed session ideas with David Shanske and Matthias Pfefferle about different ideas as we brainstormed sessions.

My ultimate goal is to provide the documentation support to David and Mathias and other people who work on the technical side. I want to provide as David suggested, “a functional solution.” Here were some ideas I had:

A WordPress Theme Developers Guide to to the #IndieWeb

As I finish my two week WordPress experiment I am using Alan Levine’s new theme publishing posts under a variety of conditions and then checking out how microformats2 get rendered based on post kind. Be cool with folks to work on best practices to creating IndieWeb child themes. Each we can focus on our favs or the most popular. I chose Dimensions because I think the whole #rhizo #ds106 and Virtually Connecting crowd would dig how #IndieWeb stuff works. Many of them will use what Alan build because when the cogdog barks you howl back.

I also want to try to do the same with Hueman. I like that theme and I think it will just be a matter of removing bad microformat classes. This could have great benefits for the WordPress #IndieWeb community. Creating some rules for folks would rock.

You Rock - You Rule

You Rock – You Rule flickr photo by Skyflash shared under a Creative Commons (BY-NC-ND) license

Post-Type Discovery Pages

Text structure matters as much on the front end as it does in the back end. During my experimenting folks shared the Post Discovery Pages on the wiki. Anyone trying to learn how to update their blog with microformats2 would love this resource. We can make it better. The pages describing each post kind lack parallelism. Compare the page on note, article, and bookmark. Some post kind discovery pages like article stubs while others could pass Kerouac novels. Any easy but important update to the wiki would involve designing a template and make each post-kind that links from the post-discover page to match each other. We need to make the layout of wiki articles as predictable as basic math.

school math GIF

What I build

In #IndieWeb spirit you showcase something you have hacked together. For me I am working on three pieces academics and teachers could use. A static page for a professional organization, a syllabus, and a course website. Each resource will use CSS Grid and microforamts2. I am trying to keep the HTML as plain as possible to encourage sharing and remixing. Some day not in the distant future I hope to use these as th backbone for a decentralized LMS and professional network.
origins hacking GIF

1 response on “Thinking about sessions for the #IndieWeb Summit”

  1. Other Random session ideas for #IndieWeb summit:
    Again going to default how I can best support #WordPress community but other ideas:
    How to debug for the beginner
    Increasing Non-Technical Contribution for your Open Source Project
    I don’t want slow down folks on bug fixes with bad info but we have no resources to point people to when devs say, “Just fire up your console and tell me what you see in the debugger about Apache,” or “run a quick curl test and tell me what it says” Just having a couple how-to guides for common tests you might need could help.
    The folks who build the plumbing are amazing but they are all volunteers. They don’t have the time to write documentation, share news about updates, or create tutorials. We need to think about getting non-technical contributors such as myself more involved.

Leave a Reply

Your email address will not be published. Required fields are marked *

To respond on your own website, enter the URL of your response which should contain a link to this post's permalink URL. Your response will then appear (possibly after moderation) on this page. Want to update or remove your response? Update or delete your post and re-enter your post's URL again. (Learn More)