shakedown.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
A community for live music fans with roots in the jam scene. Shakedown Social is run by a team of volunteers (led by @clifff and @sethadam1) and funded by donations.

Administered by:

Server stats:

285
active users

#gatsby

0 posts0 participants0 posts today
Replied in thread

@zachleat I really hate to say this, because I'm acquainted with some of the people involved, but GatsbyJS was/is a tire fire to actually work with.

I wrote a blog post on my experience, and it wasn't pretty. I tried like heck to be as open minded and fair as I could.

feoh.org/posts/mis-adventures-

Blind Not DumbMis-Adventures In GatsbyJSOver the last few years I've been feeling like living exclusively in my Python programming happy place is something I can't afford to do. Setting The Scene It's almost impossible to ignore the rise

1/ I want a simple blogging/site solution but I'm letting my goldilocks side come out and haven't been able to find "just right".

This community has been quite helpful when I've asked a number of oddball #questions, so I figured I'd throw this out and see if anyone has suggestions.

I could do #WordPress but I want super snappy and while there are ways to get that with WP I'd prefer something that just is that from the get go.

I could use a #SSG like #Gatsby or #Docusaurus but

#introduction since I moved instances 💃

I'm a software developer from South Germany. I hack with @activenode occasionally and organize the #WebDevBBQ in Stuttgart (there is big news upcoming btw :)) with him.

Currently learning #Rust (with a focus on #WASM), working with #Gatsby, and #NextJS.

I want to do many things but am hindered by a very small needy human in my building. And a somewhat taller needy human. And a needy dog.

Ask me about #archery, #chess, #WebPerformance, #keyboards.

Interesting little issue. #Gatsby 5.2.0 and #Node 18.12.1. Gatsby develop fails with error re: digital envelope routines::unsupported. My first thought is nvm down to Node 16 - prolly some fresh webpack hell - then Gatsby yells that it wants Node 18 🤦🏻‍♂️ npm run develop does the trick with Node 16.2.0 but wow. Gonna have to see what’s shaking in the Gatsby community regarding this in the morning lol 😂