#@DEGoodmanWilsonTrying very hard to understand the #indieweb and how to implement various bits of it, but I'm finding the resources at http://indieweb.org essentially incomprehensible. Is there a better resource for the complete beginner? Does this even exist? (twitter.com/_/status/1466393142404472834)
#aaronpkit's not really surprising, the getting started page is written to people who are really just getting started from nothing, and then all the headers under "indieweb self-starters" describe the what, but not the why
gRegor, [fluffy], jooo, angelo and [manton] joined the channel
#[manton]I wonder if Getting Started should be split into multiple pages? There’s a lot of info on that page… I can see how someone would get lost trying to figure out what they need to know.
#[manton]Or more advanced topics at least put somewhere else. Running a home server, URL-shortener, etc. are all things that very few “getting started” people will need.
#[tantek]1This seems like a key insight: "using a static site generator, so the three paths in the Getting Started don't speak to me"
#[tantek]1the descent into "getting started for a developer" in #indieweb is not helpful IMO
#[tantek]1Loqi was right, that was when the conversation should have been taken to #indieweb-dev
#[manton]Yeah, the steps for someone using a static site vs. a hosted blog system are very different, usually. Those might be the 2 main paths.
#[tantek]1we need to capture examples we're encountering of "I'm a smart/experienced/technical person and I'm confused by Getting Started" because they are helpful both for improving the actual Getting Started, and point to ways we can improve /welcoming to help guide folks to understanding that expertise in one area doesn't mean everything is unconfusing
#[tantek]1[manton] hard to tell, if you check the Bridgy/webmention stats, traditional CMS's (WordPress, Drupal) dwarf both of those "2 main paths" combined.
#[tantek]1by "hosted blog system" do you mean WPcom or WPorg on your own web host?
#[manton][tantek] I guess both, potentially… Perhaps it’s not quite right but I was thinking there’s a difference between people who are basically going to need to work in HTML directly (adding link tags, JS, whatever) and people who mostly need to configure existing tools and plug-ins.
#[tantek]1agreed, and we've previously discussed a completely separate "Getting Started For Developers" page for the former
#[manton]That makes sense to me. It’s just a different skillset to add (for example) Webmention to WordPress vs. Hugo.
#[tantek]1refocusing "Getting Started" on solutions that requires zero coding (even seeing code) and zero command lines
#[schmarty]it also sounds a bit like we could use a "getting started" type doc that is focused on understanding what is possible and choosing goals.
#[schmarty]including basics like "have my own content on my own domain" but also "interact with other indieweb sites" and "allow other indieweb sites to interact with me"
#[schmarty]like common compositions of building blocks.
#[tantek]1"understanding what is possible" is something the home page should convey to some extent, with longer pages for details.
#[tantek]1that kind of "value proposition" needs to be up front