#meta 2021-12-17
2021-12-17 UTC
Seirdy joined the channel
# 
Loqi [New Event] tracydurnell.com created "Jan 22, 2022 9:30am IndieWebCamp Popup: Analog Meets Online" https://events.indieweb.org/b8c2zEb33yBS
# Loqi [Event Updated] tracydurnell.com updated "Jan 22, 2022 9:30am IndieWebCamp Popup: Analog Meets Online" changed description https://events.indieweb.org/event/324/history/982/diff
# 
kaja.sknebel.net edited /User:Kaja.sknebel.net/upcoming-popups () "(-901) update from https://events.indieweb.org/tag/popup" (view diff)
# 
tracydurnell[d] It didn't occur to me to ask until I already set it up, but is there a template for what should be in a popup event listing? I just adapted from past events
# Loqi [Event Updated] tracydurnell.com updated "Jan 22, 2022 9:30am IndieWebCamp Popup: Analog Meets Online" changed description "fix etherpad url and make it a link" https://events.indieweb.org/event/324/history/983/diff
# Loqi [Event Updated] tracydurnell.com updated "Jan 22, 2022 9:30am IndieWebCamp Popup: Analog Meets Online" changed description "actually make it a link" https://events.indieweb.org/event/324/history/984/diff
# 
tracydurnell.com created /2022/Pop-ups/AnalogMeetsOnline (+938) "Created page with "'''<dfn>Analog Meets Online</dfn>''' will be an online IndieWebCamp popup discussion in 2022. == Details == * Organizer: [[tracydurnell]]<br> * Event: https://events.indieweb..."" (view diff)
# 
@ChrisAldrich Greg McVerry reminded me that I had a Rocketbook lying around, so I can use my Amenuensis app to post to my website via pen! #IndieWeb #FTW (https://boffosocko.com/?p=55799836) (twitter.com/_/status/1471670336664055811)
gRegor joined the channel
# Loqi Just generated the first draft of this week's newsletter! https://indieweb.org/this-week/2021-12-17.html I'll generate a draft again tomorrow, so please add to it before then! https://indieweb.org/this-week#How_to
# [tantek]1 GWG, "chew the fat" is presumably referring to meat fat, which might not appeal to vegetarians for example
# [tantek]1 schmooze has other connotations
# [tantek]1 I've heard "mind meld" if you're a Star Trek fan, I've also heard "meeting of the minds"
# [jeremycherfas]1 Chat?
# 
@ravisagar Let me show you how I have configured IndieWeb module on my Drupal 8 site. Hopefully it will help you in case you want to do the same thing.
#Indieweb #Granary #Drupal #Twitter #Bridgy (https://www.ravisagar.in/videos/how-configure-indieweb-drupal-module) (twitter.com/_/status/1471739451730759683)
# 
capjamesg[d] [tantek] "is "shoot(ing) the breeze" also an unnecessarily violent metaphor?" > I had never thought about that... I don't think we have a popular equivalent in the UK.
# capjamesg[d] [jeremycherfas] I love just "chat" 🙂
# capjamesg[d] GWG I'd love to see one on Microsub, particularly around key issues that need to be discussed / resolved for the spec to mature.
maik1 joined the channel
# maik1 hi
# 
@jmtd ↩️ The Indieweb movement already exists and addresses that area of imho (twitter.com/_/status/1471752905581641731)
# 
jeremycherfas Good morning IndieWeb and capjamesg[d] Less is more!
Seb[d] joined the channel
# 
@aral RT @Austin@indieweb.social
aral
Just reading your latest blog post. Apart from being interesting and apart from not tracking me. Hot Damn, that is a fast website! Ya hear that, Rest Of The Web? Get your act together!
https://indieweb.social/@Austin/107462275732238898 (twitter.com/_/status/1471823065394909194)
IntriguedWow[d] and [manton] joined the channel
Darius_Dunlap[d] joined the channel
# Loqi Generated a new draft of the newsletter! https://indieweb.org/this-week/2021-12-17.html
# 
[KevinMarks] less deadly is not clear yet - UK spread is fast but not worked through to hospital admissions yet, let alone deaths and SA has very different age profile from UK/US
# Loqi Generated a new draft of the newsletter! https://indieweb.org/this-week/2021-12-17.html
# 
@OYCar Admissions to London hospitals starting to trend higher than you would expect from the number of cases ten days earlier, so Omicron is either putting more people in hospital than each case of Delta or doing it quicker. https://pbs.twimg.com/media/FGwPq3IVIAIoZBd.png (twitter.com/_/status/1471568961649086473)
# 
@jmeowmeow Today I learned that 'ftfy' https://pypi.org/project/ftfy/ is a tool for resolving common text encoding mistakes like the ones I had a few weeks ago. Via #indieweb Slack. (twitter.com/_/status/1471885632473493506)
# capjamesg[d] That's a cool library ^
# Loqi Generated a new draft of the newsletter! https://indieweb.org/this-week/2021-12-17.html
# Loqi Generated a new draft of the newsletter! https://indieweb.org/this-week/2021-12-17.html
# [tantek]1 The replies to this are amazing: https://twitter.com/cabel/status/1471528602072064002
# 
@cabel I don’t know why, but this reply has really stuck with me. “web3 is promising because I once wasn’t allowed to squat on 1,200 twitter usernames that I planned to flip for profit”. It’s just… so revealing https://pbs.twimg.com/media/FGvrdvpVUAAVnZu.jpg (twitter.com/_/status/1471528602072064002)
# Loqi Generated a new draft of the newsletter! https://indieweb.org/this-week/2021-12-17.html
# Loqi Generated a new draft of the newsletter! https://indieweb.org/this-week/2021-12-17.html
# 
petermolnar.net edited /why (+929) "moved entries from "see also" to "Why have your own website" section" (view diff)
# petermolnar.net edited /why () "(-1544) entries were moved to the "Why have your own website" section" (view diff)
# Loqi Generated a new draft of the newsletter! https://indieweb.org/this-week/2021-12-17.html
# petermolnar.net edited /why (+156) "added Ana's smashingmagazine which was somehow not saved into our wiki" (view diff)
# Loqi Generated a new draft of the newsletter! https://indieweb.org/this-week/2021-12-17.html
# [tantek]1 petermolnar++ that's a lot of cleanup on a challenging long page! appreciated
# Loqi Generated a new draft of the newsletter! https://indieweb.org/this-week/2021-12-17.html
# 
petermolnar the /why page is a splinter in my toughts to be honest. I know it makes sense as is, but simultaneously I find it incredibly unreadable from a newcomer or non-tech person perspective.
# petermolnar I know it's a wiki, but it doesn't have a flow to read it
# petermolnar and I think that's my main problem, that people arrive at our wiki with the idea of reading through /why and they get immediately overwhelmed, because instead of a nicely written article they get an encyclopedia
# petermolnar I think adding a short summary in each major section with a few links to the outside world's nice articles could help.
# petermolnar so I seriously like the idea of the "Why have your own website" section with the outgoing links
# [tantek]1 I agree. Each section itself should be treated like a mini-article, with a easier to read summary at the top, before diving into a detailed list
# [tantek]1 This is also the challenge of figuring out both when and how to split longer pages into subpages, because rarely is it obvious how to do so, and different pages need different treatment (there's no universal "here's how you can split up every page!" that works while preserving easy access to content
# petermolnar I saw your todo: split identity loss, I fully agree with that
# [tantek]1 Key is to avoid the "don't make me click 4-5 times just to read something of substance" which is usually what happens when content gets divited up
# petermolnar I might have some time in the coming weeks to start that
# [tantek]1 I'm happy to help brainstorm that btw, just not right before the newsletter goes out.
# petermolnar why does /problems redirect to /use_case ?
# [tantek]1 I don't remember
# [tantek]1 maybe it was an attempt to get (mostly developers) to reframe their "problem" statement into an actual use-case
# [tantek]1 since so many developer problems start with things like "so I have this server problem" or "DNS problem" or "database problem" or "CMS problem"
# [tantek]1 or worse "I have this markup problem" and that's great for other discussions, but that's not an "IndieWeb problem"
# [tantek]1 attempt to get folks out of default plumbing-centric thinking
# petermolnar maybe we can recycle that redirect for some parts of /why
# petermolnar I'll keep thinking
# [tantek]1 if you're looking for pages to prioritize making more welcoming to newcomers, check out the stats for most visited pages
# edgeduchess[d] this might be more a general thought than about fixing the wiki, but if you're thinking about the newcomers flows I think there's value in thinking about what your goals are for them and actively building with those in mind
# edgeduchess[d] like, what does your ideal newcomer look like? What are their goals? How can you help them achieve them?
# edgeduchess[d] if you think about what your newcomers comes in the space seeking, and what you want them to learn in the first 15 minutes, that will help building an effective flow for newcomers onboarding
# Loqi Generated a new draft of the newsletter! https://indieweb.org/this-week/2021-12-17.html
# Loqi Generated a new draft of the newsletter! https://indieweb.org/this-week/2021-12-17.html
# Loqi Generated a new draft of the newsletter! https://indieweb.org/this-week/2021-12-17.html
marksuth[d] joined the channel
# [tantek]1 edgeduchess[d], mostly we're doing all that based on actual newcomers experiences, rather than trying to answer those questions a priori. listening to people's empirical experiences rather thank "thinking about", trying to understand the diversity of actual newcomers rather than an "ideal"
# [tantek]1 a lot of that top level experience/design has gone into the thinking behind the ongoing "three column" home page redesign so far
# Loqi Generated a new draft of the newsletter! https://indieweb.org/this-week/2021-12-17.html
Christian_Olivie joined the channel
# [tantek]1 yeah I'm going to do that thing where you create pages last minute before the newsletter that you really should avoid doing
# 
tantek.com deleted /link_in_bio "content was: "#redirect:[[Linktree]]", delete to create an actual content new page"
# Loqi Just generated this week's newsletter! You still have a few minutes to make changes, and I'll re-generate it 10 minutes before it gets sent out at 3pm Pacific time. https://indieweb.org/this-week/2021-12-17.html
# edgeduchess[d] [tantek]1: but can you answer those questions? 😛
# edgeduchess[d] i'm not saying you should answer them a priori
# edgeduchess[d] i'm saying having the answers is really helpful to design a good onboarding flow
# edgeduchess[d] 32
# edgeduchess[d] (cat)
# tantek.com created /link_in_bio (+2553) "start by extracting general content from the Linktree page" (view diff)
# [tantek]1 edgeduchess[d], the general types of questions are good to keep asking, and iteratively improving the answers we come up with
# [tantek]1 can folks give this a quick review before the newsletter goes out? (next 5-10min) https://indieweb.org/link_in_bio
# tantek.com edited /Linktree () "(-2079) moved generic information to separate link in bio page" (view diff)
# tantek.com created /link-in-bio (+25) "create redirect because this hyphenated form was used in a recent TechCrunch article" (view diff)
# petermolnar there's https://indiewebguides.org/ which I think is a very nice entry point for complete newcomers
# tantek.com edited /link_in_bio (+163) "move a coupel fo see alsos from Linktree to this page" (view diff)
# tantek.com edited /Linktree (-87) "/* See Also */ moved a few general see alsos to link in bio page" (view diff)
# [tantek]1 petermolnar, disagreed, that's good for developers, not for newcomers in general
# [tantek]1 e.g. it completely neglects turnkey services like micro.blog which are actually a lot nicer for newcomers
# edgeduchess[d] as a developer, it doesn't fully work for me too
# [tantek]1 setting up a webhost is *not* a "very nice entry point"
# edgeduchess[d] i could do a writeup of what i'd like to see, if people are interested
# edgeduchess[d] but later 😛
# [tantek]1 petermolnar, you have a very different assumptions of what a "complete newcomer" knows or wants
# [tantek]1 edgeduchess[d] sounds like a good blog post 🙂
# petermolnar well, they don't want an inconsistent, badly formatted wall of text in form of a wiki
# petermolnar that is for sure
# [tantek]1 nor do they want that replaced with something that makes them feel bad because they lack sufficient "will" or don't "get" the "simple" existing tools (which none of are actually simple)
# Loqi Generated the final version of the newsletter! This will be sent out at 3pm Pacific time. https://indieweb.org/this-week/2021-12-17.html
# petermolnar give me an example of a tool -any tool, in any context, real world, digital, anything - you believe it simple enough, please.
# petermolnar that doesn't require any kind of learning or getting accustomed to
# [tantek]1 petermolnar, binary questions like that are also useless and completely miss the point
# petermolnar it's not binary
# petermolnar I just need one example
# [tantek]1 tools are on a spectrum of usability and ignoring that means you might as well not try
# [tantek]1 "doesn't require any" is binary thinking
# petermolnar ?
# [tantek]1 less or more usable is spectrum thinking
# petermolnar and fuzzy math is fuzzy thinking, yes
# [tantek]1 absolutist statements like that about tools won't get you anywhere
# [tantek]1 nor will mocking spectrums and linear phenomena
# [tantek]1 it's not fuzzy math, it's just not binary 😛
# [tantek]1 edgeduchess[d], have you found successful techniques for getting more folks to understand/sympathize with the broader default desire for at least decent and preferably "nice" aesthetics?
# petermolnar my point: there are no such tools. Not even a hammer, because even that needs practice.
# [tantek]1 my point, that's a pointless point.
# tantek.com edited /2021-12-indieweb-gift-calendar (+160) "gifts for the 15th and 17th" (view diff)
# edgeduchess[d] [tantek]1: I think people do sympathize with that generally, but most often those people aren't necessarily in places like this
# edgeduchess[d] I think there's certain types of devs that just will never sympathize with that, and that's ok cause they can build tools for devs rather than for end users
# edgeduchess[d] anyway, I'll tell you what I'd consider the simple guide/tool I'd like to have for myself
# edgeduchess[d] 1) a list of what I'll need to implement to get my own self-hosted to ~Tumblr-levels of interactivity
# edgeduchess[d] (so people can discover and comment on it)
# edgeduchess[d] 2) a list of npm packages i can install in my JAMStack tool of choice to kickstart my journey
# edgeduchess[d] 3) where to go to ask for help/join the community
# [tantek]1 Tumblr as an indieweb-feature-set is an interesting exercise to consider
# edgeduchess[d] i am talking as a developer
# [tantek]1 clearly from mentioning npm 🙂
# edgeduchess[d] ofc eheh
# [tantek]1 what is JAMStack
# Loqi Jamstack is a web development architecture based on client-side JavaScript, reusable APIs, and prebuilt static pages served via a CDN https://indieweb.org/Jamstack
# edgeduchess[d] TBH complete NextJS e2e tooling/tutorial would be the best way to get interested devs started these days
# edgeduchess[d] but you *need* to think about their experience as users
# [tantek]1 that page needs a big update for an IndieWeb-relevant definition and "How To" section
# edgeduchess[d] you kinda want to make it so they go from bringing up their website to getting their first comment on whaetever the write to be a "delightful" experience
# [tantek]1 ^ that's a good characterization
# edgeduchess[d] like you offer a lot of tooling and choices, but you kinda need a minimum path to people being like "hey! there is a community of people here I can be part of! they'll listen to me!"
# capjamesg[d] Good points edgeduchess++
# [tantek]1 yes there's the whole SSG onboarding path that needs better paving
# [tantek]1 and you're right about that being a fairly big core segment of many devs these days
# [tantek]1 what is NextJS
# Loqi It looks like we don't have a page for "NextJS" yet. Would you like to create it? (Or just say "NextJS is ____", a sentence describing the term)
# capjamesg[d] I agree re: NextJS being quite big among personal sites. I used it for a while but it was too bloated / abstract for me. But many people love it and it’s good for commercial sites.
# capjamesg[d] How can that onboarding path be fleshed out [tantek]?
# capjamesg[d] I went from numerous tools — even Carrd — to NextJS to Jekyll to my own static generator.
# edgeduchess[d] capjamesg[d]: you want to go meet the dev community where it is
# [tantek]1 capjamesg[d], can you create a stub page for NextJS?
# edgeduchess[d] NextJS is one of those places
# [tantek]1 lol
# capjamesg[d] Oh dear 😂
# capjamesg[d] I don’t think Loqi can avoid that without amazing NLP functions.
# capjamesg[d] Good try Loqi!
# capjamesg[d] I can flesh out a Next.JS page this weekend. It’s getting late here but I’ll definitely do it.
# [tantek]1 capjamesg[d], that would be a good start
# [tantek]1 what is an 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
# capjamesg[d] Re: static sites, I have had a lot of success adding IndieWeb functions.
# capjamesg[d] I started by building a site then slowly added in IndieWeb features using existing tools like Webmention.I’m.
# capjamesg[d] *io
# capjamesg[d] As I built confidence I experimented with JS to add dynamic features like comments. Then I went deeper into each spec and realized I wanted to implement many of them 🙂
# capjamesg[d] What would you look for in that how to page? How to choose one?
# edgeduchess[d] also this made me think that really what you want is a good NextJS IndieWeb SSG website starter
# edgeduchess[d] Which is actually what I wanted to build for another project i have in mind
# edgeduchess[d] but it could be spun off in its own community thing
# capjamesg[d] I’d love that edgeduchess.
# capjamesg[d] Not for personal use but as a community resource.
# [tantek]1 that's been a lot more/better developed because there's frankly been more CMS folks in the community than SSG folks
# capjamesg[d] I’ll take a look! Thanks! I will try to write something over the weekend.
# edgeduchess[d] capjamesg[d]: just make a github repo people can clone to get startedd
# [tantek]1 edgeduchess[d], yes to "a good NextJS IndieWeb SSG website starter"
# [tantek]1 we already have this for static GitHub hosting
# capjamesg[d] Yeah, exactly.
# edgeduchess[d] [tantek]1: you should lead with this wherever possible, the info is way too buried 😛
# capjamesg[d] Then all someone needs is a git clone and an npm install to get started.
# [tantek]1 edgeduchess[d] lead with which?
# edgeduchess[d] the fact that you have a website starter
# capjamesg[d] Adding features like comments with webmentions through components would be really powerful.
# [tantek]1 it's part of the path on /Getting_Started
# capjamesg[d] And, of course, SSG / ISR should be used when possible 🙂
# [tantek]1 we don't have anything structured for SSG approaches because they've been a minority so far
# edgeduchess[d] [tantek]1: how many clicks away from the landing page? 😛
# [tantek]1 one
# edgeduchess[d] I count 2, because i consider the anchor to "self starter" to be one
# edgeduchess[d] and even when i get there, the info is way too buried
# [tantek]1 re: "meet the dev community where it is" <-- there is no one "the" dev community, that's why we have to offer multiple paths, and hopefully in a way that people can self-direct to the path that fits their dev approach
# [tantek]1 edgeduchess[d], that's fair
# capjamesg[d] I agree with the spirit of edgeduchess[d]’ statement.
# capjamesg[d] In that NextJS is popular and robust and used for personal sites.
# edgeduchess[d] it's true that there are multiple communities, but tools with hype and traction behind them should be prioritized and actively pursued
# edgeduchess[d] NextJS fits that bill
# [tantek]1 tbh first I've heard of it in this context
# capjamesg[d] Yep! That’s why I documented some of the ways in which I added IndieWeb features to my Jekyll site. And continue to do so as a static site.
# edgeduchess[d] also, if you don't syndicate with dev.to, you should do it more
# petermolnar > tools with hype and traction behind them should be prioritized and actively pursued - are you sure? Because hypes change every ~half year.
# edgeduchess[d] (what I mean is you should write articles for that audience, and make sure they show up there)
# edgeduchess[d] Nah, they don't. Some things stay stable.
# edgeduchess[d] like yeah sure some stuff comes and goes
# edgeduchess[d] but NextJS is at version 12?
# [tantek]1 nope, looks like it's been mentioned a bunch in the past 2 years
# petermolnar > Nah, they don't. Some things stay stable. - like Perl.
# edgeduchess[d] generally betting on JS tooling is the best thing to do here
# [tantek]1 2 years of steady growth beats that "change every ~half year" metric petermolnar
# edgeduchess[d] you pick the framework that's popular then, you can npm package a lot of stuff that's reusable across whatever comes next
# [tantek]1 edgeduchess[d] really? I mean, I agree with specific tooling that seems to be picking up, however, JS framework-du-jour is an endemic problem and merits the skepticism that petermolnar is talking about
# edgeduchess[d] I think it's generally true, but I think there's big players that are an easy target
# edgeduchess[d] React ecosystem
# edgeduchess[d] NextJS ecosystem
# [tantek]1 putting a lot of work into onboarding docs for a framework dead in 3-6 months is disheartening and demotivating
# [tantek]1 what is React
# Loqi React (also called ReactJS) is an open source client-side JavaScript web framework created by Facebook https://indieweb.org/React
# 
@indiewebcamp This week in the #indieweb https://indieweb.org/this-week/2021-12-17.html (twitter.com/_/status/1471982298228662274)
# petermolnar you want someone from the indieweb community to package tools for react?
# edgeduchess[d] now Remix is all the new rage, and I wouldn't suggest getting onboard with it soon, but if you had done the NextJS work it'd be easily portable
# petermolnar there is no fun in that
# edgeduchess[d] I indeed do want that
# petermolnar and why would anyone do that for free?
# [tantek]1 petermolnar, no need to dunk on React like that, just cite the wiki: https://indieweb.org/React#IndieWeb_Examples
# edgeduchess[d] cause they care about freedom of the web and people owning their independent websites
# petermolnar yes, *their own site*
# [tantek]1 petermolnar, people do it for the tools they themselves use
# edgeduchess[d] nextjs solves this
# edgeduchess[d] > Websites that use React often only render on the client-side, which means they are not curlable. The only HTML in the page on the initial browser load of such sites is typically an empty body and some links to Javascript files. This means that microformats parsers are unable to see any of the content there. Websites can solve this by adding Server-Side Rendering.
# edgeduchess[d] like out of the boix
# edgeduchess[d] [edit] like out of the box
# petermolnar so does raw html...
# edgeduchess[d] yeah and who's writing it these days?
# petermolnar o/
# petermolnar sometimes
# [tantek]1 petermolnar, please re-read /plurality
# [tantek]1 there's no need for "so does XYZ" comments
# petermolnar [tantek]1: do you honestly believe the best course ahead for indieweb is to package react & npm packages?
# [tantek]1 petermolnar, please stop with the strawmanning. no one said "best course ahead"
# [tantek]1 the fact that you even asked/framed the question that way shows you failed to read / understand /plurality, so please go re-read that
# tantek.com deleted /NextJS "accidental creation content was: "
{{stub}} '''<dfn>NextJS</dfn>''' is one of those places.", and the only contributor was "[[Special:Contributions/Loqi.me|Loqi.me]]" ([[User talk:Loqi.me|talk]])"# petermolnar edgeduchess[d] is recommending that someone here should pick up the task of creating indieweb nmp packages that are in theory cross-framework proof, so devs can pick it up. I'm saying nothing is stopping anyone from doing that, but it's unrealistic to expect that people will pick this up just for fun.
# petermolnar edgeduchess[d] if you know npm devs who'd like to pick this up, please involve them
# [tantek]1 I think that's a misinterpretation
# [tantek]1 edgeduchess[d], appreciate the raising the points about NextJS, looks like it has come up a few times in chat over the past couple of years, and is even mentioned in a few pages: https://indieweb.org/wiki/index.php?search=NextJS
# [tantek]1 ^ capjamesg[d] see those search results, might be helpful when you're stubbing the NextJS page
# edgeduchess[d] I actually have full intention of doing that when i start working on my own personal website, cause I strongly believe the lack of those is an extremely low hanging fruit to get more people into the ecosystem
# [tantek]1 edgeduchess[d]++ that would be awesome, and am more than happy to help link up such content so it's (more) discoverable
# edgeduchess[d] it is part of the reason I am not in the ecosystem myself, paired with no onboarding path that works with my brain
# edgeduchess[d] and a bunch of other stuff
# [tantek]1 yes, our onboarding path for SSGs in general is very poor right now
# [tantek]1 a good start would be here: https://indieweb.org/Getting_Started#Get_a_place_for_your_content
# [tantek]1 that might not even by the right framing "place for your content"
# [tantek]1 however I'd like to replace the "GitHub Pages & GitLab Pages" subsection there with instead something more welcoming to SSG approaches in general, including listing NextJS by name
# edgeduchess[d] have you considered making the font size different in h3 vs h4 more dramatic?
# edgeduchess[d] would improve legibility a lot
# edgeduchess[d] I know it's not what we're talking about, but the sections of the pages blend together for me
# edgeduchess[d] i just threw in a random number, but now i can skim
# edgeduchess[d] here my brain can't jump from a section to the next without reading every title inbetween
# edgeduchess[d] with the previous screenshot, i can tell easily that "get a place for your content" has 3 sections, once of which is GithubPages
# edgeduchess[d] I think if you do it this way, adding another section for SSG/JS frameworks (even if you didn't want to replace GitHub pages) would visually work
# [tantek]1 agreed about the "sections of the pages blend together" problem
# [tantek]1 IMO GitHub pages is "just" another SSG approach so it should be subsumed accordingly
# [tantek]1 I've had more success directing people to Netlify than GitHub pages recently to get started and setup their personal sites / blogs etc.
# edgeduchess[d] I think that makes sense, just be aware some people might not know what SSG is, even if they use Next
# edgeduchess[d] namedropping is good
# edgeduchess[d] yeah I would also personally prefer netlify
# [tantek]1 indeed, SSG can be an "abstract" term and it helps to mention specific examples that may resonate with people (that they've heard before)
# [tantek]1 right now we don't even have a dirt path for SSGs in general, or a page about NextJS, so we need those first
# [tantek]1 something even minimal for folks to read and follow
# [tantek]1 looks like [grantcodes] has had some positive experiences with NextJS too
# [tantek]1 edgeduchess[d] did you find https://css-tricks.com/jumping-into-webmentions-with-nextjs-or-not/ by any chance and was it helpful?
# edgeduchess[d] i did not, but i assume when i went to build it for myself I would have found it and found it useful
# edgeduchess[d] I've used similar tutotrials in the past and CSS-Tricks usually has good content
# [tantek]1 I'm asking because if we can at least link to existing tutorials like that to start with, it will help provide at least a path for folks while we write more docs
# [tantek]1 Since I'm not a NextJS dev, I don't know if that's a "good" article from a NextJS dev experience perspective, hence why I'm curious about your opinion of it
Seirdy joined the channel
# edgeduchess[d] anything that's good for a general webdev is also good for a nextJS dev 🙂
# edgeduchess[d] it hides the fact that it's a react framework really well
# [tantek]1 that's interesting because past experience has been that "general webdev" is very much at odds with a "react mindset"
# edgeduchess[d] i think it might be harder for a general webdev to get into using react stuff
# edgeduchess[d] but with nextJS, everything that works for general webdev, mostly works for nextjs too
# edgeduchess[d] at least that's my experience