#meta 2021-11-17
2021-11-17 UTC
# 
tantek.com created /link_in_bio (+22) "until someone wants to make this an abstract page / phrase instead of just one service" (view diff)
# 
[tantek]1 close enough for now, opportunity for someone to write an abstract article for such services if they want!
# edgeduchess[d] [tantek]1: I think having a solid base to update is easier than creating from scratch
# edgeduchess[d] it might even be worth talking with someone from Open Web Docs to get their opinion: https://opencollective.com/open-web-docs
# edgeduchess[d] I'm sure they would have a lot of ideas on what could be effective
# edgeduchess[d] by track record you mean not keeping it up to date?
# edgeduchess[d] yeah, it's definitely a challenge
# edgeduchess[d] I'm also trying to keep the documentation for my own project in sync and it's a struggle
# edgeduchess[d] but I'm doing research on good ways to do it, so maybe as I learn more I'll find something that's effective
# [tantek]1 “solid base” - not clear you could even make such a thing as by the time you’d finished something “solid”, the details would have changed
# [tantek]1 Also I’ve never seen a “base” delivered by a “professionals” actually be something that a community could maintain
# [tantek]1 All sustainable community models I’ve seen have been built first & foremost by a community (eg wikipedia, Wordpress etc)
# edgeduchess[d] [tantek]1: are you talking about software or documentation? I think the two things have different properties
# edgeduchess[d] writing good documentation from scratch is a whole different skill than updating it
# [tantek]1 Yes, and writing good community maintainable documentation is a different skill than writing good documentation from scratch.
# edgeduchess[d] makes sense, yes
# edgeduchess[d] I'd actually be interested to know whether there's good writeups on best practices
# [tantek]1 Wikipedia has kinda evolved the best to date of those IMO
Seirdy joined the channel
# 
@superterrific This post started as "Hey, let's take a quick look at <time>" and ended up diving into @Eleventy content dates and how to participate in #IndieWeb. Whoops! https://danabyerly.com/articles/time-is-on-your-side/ (twitter.com/_/status/1460784834536685572)
nertzy, Matt4, [KevinMarks], [schmarty], [chrisaldrich], [tantek], [jacky], pfefferle, [snarfed], [jeremycherfas], IWSlackGateway, [Paul_Walk], [grantcodes], [chrisbergr], Matt5, [KevinMarks]1, [grantcodes]1 and [KevinMarks]2 joined the channel
# 
tracydurnell[d] edgeduchess[d] earlier this summer I tried to identify a few different audiences and what content they'd be interested in for the homepage, which I think would also apply to the getting started page, if you wanted to add on to that or steal anything from there https://indieweb.org/2021/homepage
# tracydurnell[d] yeah seems like there was some good discussion above
# 
[schmarty] one community approach to improving documentation would be to work with individual developers who are considering adding indieweb building blocks to their projects.
# 
Loqi Get started on the indieweb by connecting with the indiewebcamp community, getting a personal domain, a place for your content, and setting up your home page and other indieweb essentials https://indieweb.org/tutorial
# 
[tantek] like does anyone know if any of these still work? or when was the last time someone used any of them successfully? https://indieweb.org/Getting_Started#IndieWeb_CMS_and_Hosting
# [tantek] Good Example of a "solid base" that j12t took the time to write-up, but then no one has made non-trivial edits them in almost 4 years. E.g. https://indieweb.org/Tutorial_Set_up_an_IndieWebSite_using_WordPress_on_the_Amazon_cloud
# Loqi It looks like we don't have a page for "documentation" yet. Would you like to create it? (Or just say "documentation is ____", a sentence describing the term)
# 
aaronpk oh wow there's a bunch more https://indieweb.org/wiki/index.php?title=Category:tutorial
# aaronpk documentation is written text or audiovisual media that is used to describe or instruct how something works, for example how to [[get started]] on the IndieWeb, or how to install a particular piece of [[open source software]] to use on your personal [[website]]
Seirdy joined the channel
# samwilson.id.au edited /NASCAR_problem (-56) "Remove link from top as it's already present lower down and is not working with the pagelogo." (view diff)
# 
aaronparecki.com created /Category:tutorial (+22) "Created page with "See: [[documentation]]"" (view diff)
# aaronparecki.com edited /documentation (+1334) "add related wiki pages, external tutorials, indiewebcamp sessions, link to chat log that inspired this page" (view diff)
# aaronpk alright, i collected a bunch of links and other things that were discussed today here https://indieweb.org/documentation
edburns[d] joined the channel
# aaronpk edgeduchess[d]: please take a look at the new page and feel free to add any notes expanding on anything discussed today! https://indieweb.org/documentation some of the topics in chat could use summarization and capturing on the page for example
# edgeduchess[d] thank you, I'll take a look tomorrow morning!
# edgeduchess[d] that's a pretty useful page
[schmarty], [snarfed] and [KevinMarks] joined the channel
willnorris and jbove joined the channel
jbove and inertia joined the channel
# 
Murray[d] edgeduchess++ Really interesting conversation. I've long felt that a Smashing Mag/CSS Tricks style site for Indie Web topics would be an asset; somewhere centralised for high-quality tutorials and resources on how to set up certain IndieWeb technologies on different platforms, what the purposes are behind them, etc.
# Murray[d] I think a site like that could also operate as a sort of prime example of IndieWeb tech directly by implementing and utilising most building blocks, a little like the Wiki does as an example of a use case for IndieAuth, but more broadly. Webmentions for interactions, IndieAuth for community, Micropub for article submission etc.
MarkJR84[d], Agnessa[d], barryf[d], jjuran, strugee_, GWG, sayanarijit[d], [tantek]2, [grantcodes], [jacky]1, [chrisaldrich]1 and [chrisbergr] joined the channel
# tracydurnell[d] aaronpk++ thanks for gathering all that info together, seems like it'll be useful!
# tracydurnell[d] do you think it would be helpful to have like a wishlist of tutorials that don't exist yet?
# [schmarty] i would really love to see guides for writing micropub clients
# [tantek]2 what is document
# Loqi It looks like we don't have a page for "document" yet. Would you like to create it? (Or just say "document is ____", a sentence describing the term)
# [schmarty] (which should also cover IndieAuth clients)
# [tantek]2 document is /documentation
# tantek.com edited /principles (+13) "link the "document" principle since we now have a page for it!" (view diff)
# Seb[d] [schmarty]: Micropub / IndieAuth from scratch? as in coding it up? A lot of it depends on the language and CMS used, and there might be packages / libraries / plugins available too, which then will vary in compatibility over the years
# [schmarty] heck yeah they will!
# 
tracydurnell.com edited /documentation (+344) "/* IndieWeb Documentation */ add wishlist section, add section for popup videos (or should that go under sessions?) with a couple wordpress related videos" (view diff)
# 
capjamesg[d] [schmarty] I'd love to see that to!
# capjamesg[d] tracydurnell++
# capjamesg[d] For the docs.
# capjamesg[d] I think implementation guides would be helpful for someone who is trying to get started and provide some assurance regarding project direction.
# capjamesg[d] Specifications are ultimately the best place to go if you have a question (second to asking someone to help :)) but tutorials tend to be a bit more intuitive / easier to digest.
Seirdy joined the channel
# [tantek]2 capjamesg[d], yes re: implementation guides, and those should parallel the specs on the wiki