Looking for some feedback from #webdev folks.. I'm experimenting with migrating a #nextjs project to Astro. On paper, the site is a great candidate - content-focused (blog, articles) looking for lighter client experience and better dev experience. https://astro.build/
I have a CMS wired up and have started migrating a couple React components. What gotchas are hiding deeper in this project? Where are the common pitfalls with Astro?
Hey folks, we're kicking off a new pledge drive to accelerate the development of Bridgetown, an "alt #Ruby" web framework which starts off in the #Jamstack and vanilla-first, #HTML-first, #WebComponents-friendly development, but provides the ability to scale up to dynamic fullstack applications & publications.
Version 2.0 is underway with modernization, performance, and of course new features all on the table!
Consider sponsoring today to ensure 2.0 absolutely rocks. 🤘
When I was promoting #Jamstackyears ago one of the points that I emphasized most was that it's great to avoid technology- and vendor lock-in.
But then the vendors came.
I guess that was inevitable. If all you offer is a "nicer" way of building and distributing static sites then companies who can do it cheaper will catch up. It's most likely just the same infra underneath. You need to offer something that makes people prefer your platform over others.
The entire point and the beauty of static website is that they are self contained and portable. By adding more and more APIs for sure makes it less portable and fragile to some extend. Simplicity is not simple anymore.
😶🌫️ @zachleat on the future of #jamstack
📊 @ChenxinLi2 on bad graphing practices
🩺 Taylor Otwell announces #Laravel Pulse
⏳ @maxim on long term refactors
📚 Spencer Baugh makes the case for libraries over services
🎙 hosted by @jerod
Being able to search a blog, on the blog's site and without Google, is awesome. You should do it. Maybe this method will help you. Let me know if you do!
I have also created an open source Eleventy (@eleventy, @zachleat) starter project, as a minimalist and elegant template. If you like it leave me a star ⭐ in the repo:
#11ty / #Jamstack friends: what are your preferred methods for automatically rebuilding your static site daily (or at some other regular interval)?
This is just one step in an overall demo for a meetup, so I'd prefer not to have to focus on it too heavily. Bonus points if it's simple, intuitive, and reproducible at home.
Still trying to find a good image optimisation pipeline for @astro that has good support for being used in framework components and can work with arbitrary paths (as in load content from variables). astro-imagetools is alright, but it doesn't seem to be actively maintained anymore and does a little too much. 🤔
It's the one thing I really miss from #Gridsome. 😅
Maybe I should try building something on top of the built-in asset system in v3. 🤔
After 10+ years of building my personal website with Jekyll, I took the leap and wrote my own static site generator based on makesite.py. It's great to work in the Python ecosystem now. I never got the hang of proper Gem-management, so updating Jekyll was always a bit of a chore.
I also updated the design, following the guidelines from https://brutalist-web.design/ by @davetron5000.
The demise of #Jamstack and #Netlify as an indie-first, "static site" hosting company feels like an end of an era. But why did it have to happen like this? Where did things go wrong? And which companies can #WebDev folks turn to for streamlined, pragmatic web hosting and architecture?
Here's my take on it, serving as a reply of sorts to @remotesynth's excellent coverage of the topic: