#meta 2023-02-28

2023-02-28 UTC
#
gregorlove.com
edited /Bridgy_Fed (+532) "/* gRegor Morrill */ +article screenshots, note about fed.brid.gy link"
(view diff)
CobyPear, gRegor, mro, IWSlackGateway, vilhalmer, [KevinMarks], [Murray], AramZS, [0x3b0b], pmlnr1, petermolnar[m], jbrr[m], [tantek], M85CD[m], plantroon[m], [aciccarello], jeremycherfas, jjuran, Skyther[d], lanodan, IWDiscordRelay, ben_thatmustbeme, omz13, chee, strugee, willnorris, BinyaminGreen[m], voxpelli, klez_, Kaja, cali-iwc, GWG, jan6, mcint, aaronpk, Zegnat, Ruxton_, Seirdy_, jbove, capjamesg, tommorris, Saphire, sebsel, benji, vikanezrimaya, laker, saptaks and petermolnar joined the channel
#
gregorlove.com
edited /follow (+156) "/* How to publish */ +markup example"
(view diff)
mro and [jacky] joined the channel
#
gRegor
Do we have a page/subsection to link people to for Webmention options with SSG? /Webmention is pretty daunting
#
gRegor
Worth setting up a "Webmention for static sites" page?
#
gRegor
I guess even a Category page would work for that
#
gRegor
what is webmention.js
#
Loqi
webmention.js is a common name for a Javascript library for displaying comments and likes from the webmention.io service https://indieweb.org/webmention.js
[snarfed] and mro joined the channel
#
[tantek]
what is SSG
#
Loqi
Static site generators or SSGs are programs that take a set of flat text files on disk and transforms them into a set of static HTML files ready to be served by a standard web server, or some variation of this example https://indieweb.org/SSG
#
[tantek]
gRegor this page has that subsection: https://indieweb.org/static_site
#
gRegor
ah thanks, was looking at /ssg
#
[tantek]
yeah top of /ssg has a link directing to that
#
[tantek]
that could be more explicit
#
[tantek]
about that use-case
#
tantek.com
edited /static_site_generator (+45) "make How to / webmentions more prominent/discoverable"
(view diff)
#
gRegor
looks good, thanks!
[tw2113_Slack_] joined the channel
#
gregorlove.com
edited /static_site (+219) "/* Receiving Webmentions */ +Morris"
(view diff)
[schmarty] joined the channel
#
[aciccarello]
I'd love to have time to improve the SSG wiki pages
#
[aciccarello]
Alas, time is fleeting
vilhalmer joined the channel
#
[aciccarello]
It's a common enough architecture that we should have clear guidance
mro and mro_ joined the channel
#
aaronpk
meta question about events, I had always envisioned the pages at events.indieweb.org being able to completely replace posting event-related stuff on the wiki
#
aaronpk
like, archiving the HWC etherpads on the events.indieweb.org page instead of the wiki and such
#
aaronpk
is that a good idea or not? and what would it take to make it a full replacement if so? and if not, what benefits are there for keeping the split?
#
gRegor
Hm, I think it could be really nice if notes were in the same spot. A couple weeks ago I even tried updating the event to put the wiki page in the website field so it was easier to find them after archiving
#
gRegor
I forget, does Meetable use Markdown?
#
gRegor
("in the same spot" meaning in Meetable)
#
gRegor
Edits are already connected to wiki logins, so should be as easy to edit in Meetable. Switching from MW syntax to Markdown might be the only friction, though more people are probably familiar with Markdown
#
aaronpk
it does support markdown
#
gRegor
https://indieweb.org/Template:Homebrew_Website_Club is the only other manual thing I can think of, though maybe we could add a link to https://events.indieweb.org/tag/hwc and stop updating it at some point.
#
gRegor
Er, the 'past' version of that
#
aaronpk
could also automate updating that template from the tag feed
#
aaronpk
one thing that might be nice is being able to link to MW pages with `[[page]]`
#
aaronpk
that's doable
#
gRegor
Oh, we use sparklines in etherpads too like {{gregor}}
#
aaronpk
ah right
#
gRegor
What are meetable backups like? vs https://github.com/indieweb/wiki
#
Loqi
[preview] [indieweb] wiki: Wiki backup and issue tracking for indieweb.org
#
aaronpk
json files
#
aaronpk
did i not already set up a github repo for them?
#
aaronpk
apparently not, but it is storing backups on the disk right now
mro and [manton] joined the channel
#
[tantek]
basically, unless you plan on embedding Mediawiki page engine support inside an event page, I don't think it's worth doing
#
[tantek]
there's a much easier flow of notes -> wiki page with links and such already that's A LOT OF work to reproduce (said MediaWiki page engine)
#
[tantek]
and then there's the nice history of edits that you can browse and see diffs etc. across
#
[tantek]
sure, that's good for a single edit. I use the "show diff for range of edits" radio buttons all the time in MediaWiki
#
[tantek]
there's also more flexibility in wiki model which we take advantage of, e.g. IWCs have a session grid of actual sessions that we've collaboratively incrementally improved the UX of over the years
#
[tantek]
we can do that because lots more people can edit tables & text in a wiki page (ironicaly), than edit code to display them, nevermind get into debates that have to be resolved before code is committed
#
aaronpk
i agree the session grids are good on the wiki, but that's different
#
[tantek]
and then there's the one-to-many relationship of a IWC -> sessions -> session notes
#
[tantek]
it's not different, it's part of the question of "can we just put notes on events.indieweb" and the answer is no, not for IWCs
#
[tantek]
we also have event pages for events that no one here runs, but merely people have gone to, or perhaps spoken at
#
[tantek]
and it's inappropriate to create fake-but-real-looking events.indieweb events for such events
#
[tantek]
the easier to collaborate to evolve UX is not to be underestimated
#
[tantek]
e.g. our archive index of HWCs is very information dense and fits on a screen: https://indieweb.org/Homebrew_Website_Club#Meetings
#
[tantek]
and it too has evolved over time
#
[tantek]
I'm very much in the "use content to evolve UX faster" camp, rather than "all UX must be generated by some piece of code"
angelo joined the channel