Next steps for IndieWebCamp and IndieWeb efforts.
See something here you can help with? Jump in and help with incremental edits!
Questions? Ask in our discussion channels!
Roughly ordered by importance / oldest first.
- 1 Update How to Run an IndieWebCamp page/documentation
- 2 Improve Getting Started
- 3 Improve Why Explanation
- 4 Quoting Embedding Display
- 5 Tagboards
- 6 Process Criticism
- 7 Blog Update to Call For A Distributed Web
- 8 Blog State of the Interoperable Decentralized Web
- 9 Blog on Open Standards for the Decentralized Web
- 10 IndieWeb Homepage Live Modules
- 11 Archive sessions and chat logs
- 12 See Also
Update How to Run an IndieWebCamp page/documentation
- We need an easier/simpler/shorter "how to run an IndieWebCamp" page / documentation https://indieweb.org/IndieWebCamps
- We need IndieWebCamp in a box prepared to send to new organizers https://indieweb.org/IndieWebCamp_kit
- Things like "Hello my URL is" stickers, sticky notes for the grid, maybe masking tape. Or at least a list of things to order and have delivered to the venue
- Questions to ask registrants like: food prefs, childcare needs etc
- Decrease challenges like all the wiki pages, the nice pages at 2017.indieweb.org/ etc
- Keeping the choice of which ticketing system to use, for regional prefs. E.g. Tito eventbrite brownpapertickets or even Meetup
- Possible templates for typical camp pages and planning layout so it doesn't have to be reinvented
- Add more detailed steps to documentation on what types of information should be gathered via a ticketing system
- Add some specific tutorials regarding certain ticketing systems such as Tito in regards to best practices like copying an existing event as the beginning for a new event
Improve Getting Started
In progress of updating Getting Started steps to:
- simplify steps (create subpages if necessary for longer explanations)
- reduce steps to only those that are required and have direct benefits
- i.e. are direct steps toward achieving IndieMark levels in various areas.
- provide an explicit "Why?" quick and easily understandable explanation of the benefits, the motivating reasons for taking this step. What problems are solved? What new capabilities do you get by taking this step.
- re-order steps in order of ease of implementation / dependency
- move nice-to-haves, or simpler side options, to other pages.
I've updated Connect and Personal Domain accordingly (including subsuming short domain as a "bonus" subpart of personal domain) so far and will work on subsequent Getting Started steps accordingly. However, if you want to help with these updates, please go for it and edit accordingly! - Tantek 15:06, 7 May 2013 (PDT)
Currently working on:
- Partial Solutions - which needs a very heavy rewrite and likely moving of most (if not all) of its content to other pages, since partial solutions are a bit of a branch off/away-from real indieweb support.
Improve Why Explanation
- create subsections on why for frustration, fear, death
- provide good photo/summary page links (e.g. lightboxes of screenshots) for all corp site failures on site-deaths and why pages.
- copy each "why" citation for a silo to a Criticisms or Downtime section for that silo
Quoting Embedding Display
Quoting Embedding Display (QED) guidelines:
- Write IndieWeb versions of embedding/quoting display guidelines for when other sites display indie web posts/content
Create additional Tagboards (e.g. http://tagboard.com/indieweb ) for IndieWeb related things, and any tags used/mentioned by @indiewebcamp (or @indiewebcampuk) and link them to the respective wiki pages here.
- If/when you see IndieWeb critical (or silo apologist) articles, add to: challenges#Citations_to_process
- Go through challenges#Citations_to_process and analyze the articles, extracting new FAQs and specific challenges for the IndieWeb to overcome.
Blog Update to Call For A Distributed Web
(more than one person blogging about this would be good)
- Blog an update of the 2+ year old http://brewster.kahle.org/2015/08/11/locking-the-web-open-a-call-for-a-distributed-web-2/ from an IndieWeb perspective, what IndieWeb technologies have solve the problems in the original post, status of the experimental tech the original post mentioned, etc.
- Include references to https://rhiaro.github.io/thesis/ since it is newer than Brewster's post and has lot broader coverage of projects, efforts etc.
Bonus, also integrate the points / proposals / projects mentioned in https://www.oreilly.com/ideas/what-if-we-build-the-internet-we-always-wanted into the post such that the post responds to both at the same time (there's a lot of overlap).
Blog State of the Interoperable Decentralized Web
(more than one person blogging about this would be good)
Follow-up to previous blog post and http://dci.mit.edu/assets/papers/decentralized_web.pdf (PDF, sorry, academic source) with case studies on some projects from that blog post and the 2016 Decentralized Web Summit
Consider also explicitly citing and following-up to:
Document from most to least interoperably deployed decentralized web solutions.
Noting second to last anything mentioned in the MIT report that is deployed with real users but single-project monoculture with all the downsides of that, fragility etc.
Noting last anything mentioned in the MIT report that is either not deployed (e.g. academic / theory / hand-waving / hype), or experimentally deployed, but no real (even selfdogfood) users.
Blog on Open Standards for the Decentralized Web
(more than one person blogging about this would be good)
- Well deployed interoperable web standards (10+ interop impls with real world daily users across systems)
- Emerging interoperable web standards (3+ interop impls with real world daily users across systems)
- Other standards being implemented (1+ impls, maybe interop, with real world daily users within systems)
- Monoculture standards - "standards" only implemented (often driven by) a single implementation, summarize such monoculture problems etc.
IndieWeb Homepage Live Modules
Archive sessions and chat logs
Refer to Etherpad: Archiving IndieWebCamp notes.
- social web map
- Unprocessed to do items below here: (process/prioritize them and move them into the lists above)
- reply to https://twitter.com/estoner/status/918609048471183360 and thread with specific indieweb suggestions and invitations
- reply to https://twitter.com/estoner/status/918627524267016192 with mf2 h-card + XFN markup as a concrete existing (simpler?) alternative
- reply to https://twitter.com/michaelgorsuch/status/918628829454897152 with W3C Webmention (URL) and see h-entry for reply etc. markup
- Add Woodwind to all the tables in https://en.wikipedia.org/wiki/Comparison_of_feed_aggregators
- add h-feed and WebSub to the columns of this table https://en.wikipedia.org/wiki/Comparison_of_feed_aggregators#Web_feed_and_protocol_support, note which feed readers support either or both, and reach out to other OSS in that table requesting support (filing GH issues accordingly, and linking to them on their indieweb wiki pages!)
- help with tracking down (with citations!) the YYYY-MM-DD dates for the items listed here that would be helpful! timeline#Needs_Dates_and_incorporation_above
- Write a descriptions of how indieweb building blocks have been tied together in various implementations to make a clearer more complete independent (decentralized) social web picture
- Look into developing a "mf2 upgrade" module for the "soil" WordPress Plugin https://github.com/roots/soil that would upgrade any Theme/Frontend microformat etc. markup to use mf2, re-using code and logic from https://github.com/indieweb/wordpress-uf2
- Identify whole dead projects from https://indieweb.org/wiki/index.php?title=projects&diff=prev&oldid=41350 and move/archive them to another page accordingly, perhaps with archive-org links for their dead links
- write up something similar (as user-accessible and devoid of jargon) as https://macgenie.micro.blog/2018/04/10/a-guide-to.html adapted for IndieWeb, e.g. on "A Guide to the IndieWeb For People Who Have A Love/Hate Relationship With Twitter" obviously crediting the original as inspiration
- Create a page that lists / analyzes / shows IndieWeb Equivalents to https://medium.com/@anildash/the-missing-building-blocks-of-the-web-3fa490ae5cbc and is easily findable e.g. by searching for "Missing Building Blocks"
- low priority, but for comprehensiveness, make sure we have at least stub articles so we can have an updated place to document these (most of which we already do) https://www.w3.org/2005/Incubator/federatedsocialweb/wiki/Protocols
- Analyze litepub SSG for existing use of or potential for microformats2 markup per https://github.com/mirovarga/litepub#overview and submit minimal pull requests accordingly to improve LitePub’s mf2 support.
- "Why not just use your own domain for your to-do list and own your task. Here is my example: https://jgregorymcverry.com/my-to-do-list/ I send myself a webmention as updates. I have used Google Keep as well and just pin a “to-do, doing, done” (http://jgregorymcverry.com/6265-2/)" @jgmac1106 August 28, 2018
- split FAQ developer questions into their own developer FAQ (everything in FAQ should be written accessibly enough to answer anyone curious about IndieWeb, journalists, etc.)
- move Historical sections of pages to their own pages
- highlight best of breed screenshots for as many pages as possible near the tops of pages to immediately convey a product or spec or even concept
- update references to PuSH to use WebSub instead e.g. on friendly
- Create an issue on Coralproject / talk https://github.com/coralproject/talk/issues asking to "Support Micropub to keep a copy of your comments on your own blog", noting the use-case / real-world example that there are Coral users that created their own Tumblr to just to manually keep a copy of their comments!
- write-up a "debunking" misconceptions entry for "No IndieWeb is not just people who program their own websites" per https://mastodon.social/@Gargron/100548246348444630
- "@KevinMarks @cwebber @aaronpk I'm sorry but indieweb doesn't count, you're programming your own websites, you're not the general population. That method is not accessible for most people on here." @Gargron August 14, 2018
- Document when/how to setup initial yyyy.indieweb(.)org/cityname page as part of IndieWebCamp_Organizing#Before
- Document when/how to connect up tito registration to yyyy.indieweb(.)org/cityname page as part of IndieWebCamp_Organizing#Before, and be sure to uncomment / show Indie RSVPs!
- needs clean-up, some sort of IA/organization at a minimum clustering of similar "levels" of building blocks for easier chunking / understanding, and most of all, a set of diagrams illustrating how they interrelate
- do an iteration of updating IndieMark per recent tweet about it: https://twitter.com/eldelacajita/status/1091036825102307328
- submit patches to add microformats2 support to the HTML output from MHonArc
- ^^^ start here: https://github.com/Conservatory/MHonArc/blob/master/lib/mhamain.pl
- Good example of a series of diagrams to explain the progression of a technology, could be useful to do an IndieWeb building blocks version: https://hacks.mozilla.org/2018/10/webassemblys-post-mvp-future/
- fix the home page markup/styling in Template:Main_Page.css to be properly responsive for mobile widths so as to NOT overlap text (e.g. Discuss Events currently overlap the logo in mobile browsers, or narrow window on desktop), and to *not* use "position:absolute" on the nav UL as a horrible hack to "pull it up" to the top of the page.
- Incrementally update Getting Started on WordPress for accuracy and user-friendliness, see Chris Aldrich's work in progress on a rewrite: User:Boffosocko.com/wordpress-draft and feel free to merge from there into the current page.
- Simplify into a section with shortest possible list of IndieWeb Building Blocks necessary for interop, including using clustering to make fewer total blocks.