Twitter
by @lukeisandberg
·
R to @obiabo_immanuel: next 16.3 shipped massive dev time memory fixes. So please try the latest version
next 16.3 shipped massive dev time memory fixes. So please try the latest version
Last updated 5m ago
next 16.3 shipped massive dev time memory fixes. So please try the latest version
Yeah, it's tricky! We have to limit the amount of feature flags we're running on server rendered content as a result... however we're at a scale where we can run experiments on subsets of brands which has been on our solution thus far.
We made enormous changes across the our stack. Biggest impact for us was storing rendered content/artifacts in R2 which is regionally cached and then quickly moving to Cloudflare's native SWR cache once it became available blog.cloudflare.com/workers-…
The flag hash in the cache key is the bit I'd have missed, one binary flag doubling the variant count is how a cache quietly stops hitting
Which change did more for that LCP drop on your side, the islands or the SWR caching on menu data?
I would check to see if it meets the standard that it was placed to. @vite_js_ and @astrodotbuild have spoiled me to a good extent. I can work fine without worrying about memory like it's a black hole. Thanks bro.
One of my first projects at @owner last year: Project Speed! @astrodotbuild islands + @Cloudflare Workers/R2 + SWR caching. Such a fun stack. Menu p75 LCP: 5.4s → 0.7s. Restaurant revenue: +4%! Very cool to help local restaurants grow while making the web faster. Owner (@owner) How we rebuilt our website infrastructure with @astrodotbuild and @Cloudflare , reduced menu-page loading time by 83%, and raised per-restaurant revenue by more than 4%. building.owner.com/project-s… — https://xit.otterlord.dev/owner/status/2110070663214211416#m
Let's go!!!
How we rebuilt our website infrastructure with @astrodotbuild and @Cloudflare , reduced menu-page loading time by 83%, and raised per-restaurant revenue by more than 4%. building.owner.com/project-s…
What a time to be alive. WordPress companies choosing AstroJS for their own websites(including ours). Everyone has their reasons. But the pattern is clear, WordPress loosing its market share to marketing/portfolio sites.
They should have ask an IA to create their Website... Awful. Still nothing to do with Astro, but man.
Our Astro integration is live in the @astrodotbuild library 🎉 One command and every page of your site has a live chat with unlimited seats and file uploads powered by Telegram. It stays open from page to page, view transitions included. npx astro add @human -reply/astro Video
This pun lands perfectly. Lonely Planet on Astro feels like a natural fit. Travel guides need to load fast when someone's halfway through packing. Clean work.
Love seeing this!
Where does an astronaut get their travel tips? From @lonelyplanet of course — built with Astro 🚀 lonelyplanet.com/
keeping the marketing page right next to the app code saves so much tab juggling. how's it been holding up in practice?
🚀 Just released @laravel + @astrodotbuild Landing! A simple way to keep your Astro landing page and Laravel app in the same repository, while deploying them independently. ✅ Scaffold from Astro templates or themes ✅ Deploy via GitHub Actions #Laravel #Astro
Today, I don't care if I use @eleven_ty or @astrodotbuild ... I just tell Claude to make the changes and it does beautifully....Don't really need to get into the intricacies of these SSGs. A few years back I would pour over documentation for these and waste time moving my blog from one platform to another....really don't need to anymore unless there is a very compelling reason!
oxfmt support for @astrodotbuild was merged!
I'm in love with @astrodotbuild and I don't care who knows it!
This is amazing
Me encantó seodraft! En la semana comparto otros post y alguna otra mejora que ya tengo en mente! Es una pata importante para la distribución de @zink_erp , compartir y ayudar a mas dueños de negocio
Con @DemaioFer armamos el blog de zinkerp hace mucho usando @astrodotbuild y el kraken ahora se puso a mejorarlo un montón. (en la imagen se ven algunos detalles interesantes) Este es el poder de crear con un Headless CMS, podés iterar todo lo que quieras tu frontend y personalizar hasta el último detalle. Antes tenías que instalar un plugin en WordPress... y cuando querías acordar tenías 300 plugins instalados sin mantenimiento y matando la performance de tu sitio. No tiene sentido actualmente con todo lo que podés desarrollar acompañado de tu agente favorito. Mi stack actual: - Frontend: next o astro. - Backend CMS: @thekeystatic (git-based) o @sanity_io , también @thebcms , @strapijs entre muchos más. Ustedes cómo vienen con sus blogs? btw: está empezando a gestionar los contenidos del CMS con seodraft .app integrado con Sanity. 🫶 seodraft le da procesos completos, skills, mcp para todos los agentes y gestión de la API de dataforSEO todo resuelto. 🧙♂️
Built a MCP into my Client Portal, setup a custom connection via #Claude Desktop (no API usage $). Now I can chat and take actions about Service Requests, Tasks, etc + PWA support with web notifications. All running on my framework, powered by #Astro @astrodotbuild
Sounds very helpful! Huge fan of Astro and TIL Astro is part of Cloudflare now. Which I also love
Oh hell yeah
Such an amazing thing, thank you 🙏
yuge
Consent isn't a React problem. One engine decides what a page may load. Next.js, @tan_stack Start, React, @nuxt_js , @vuejs , @astrodotbuild , @sveltejs and SvelteKit read it the same way. HTML, WordPress and Shopify get a script tag. @kaylee_dev built most of it.
Nice!!
Love it!
Awesome!!
Coming soon to @astrodotbuild we're adding a --timings flag you can have your agents run to figure out what is slowing down your build, and have it fix it.
Building Faster Content-Driven Sites with @astrodotbuild Learn why Astro is the best choice for building content-driven websites: 🚀 Island architecture keeps JavaScript off the page ✅ Pairs naturally with Strapi for content delivery 👉 Read more: strapi.link/4hKC8P0
Tell me about it.
He tested different sites 😂😂
Plain MDX files is a good call. No database to babysit. I'm building Runwai around the deploy step, so I always like seeing what people end up using.
Flue ( github.com/withastro/flue ) is an open-source TypeScript framework for building autonomous AI agents, created by the Astro team. github.com It is a harness framework (not just another LLM SDK). You write agents as ordinary TypeScript functions using a React-style hooks API (useModel, useSandbox, useTool, useSkill, usePersistentState, etc.). The framework supplies the surrounding runtime: sessions, durable state, tools, skills, filesystem access, and a secure sandbox so the model can actually do real work (edit files, run commands, call APIs, etc.) instead of just chatting. flueframework.com Dev is onboard and redirecting fees to his GitHub
@thsottiaux what do you think? super easy to manage and maintain by both agents and humans by design
Here is the link to the site: commonplace.syedumairali-617…
I just told the codex agent what I wanted and 2 hours later the site was deployed successfully.
Vibe coded a website for storing my notes in plain MDX files using @ChatGPT codex. The site is just a @astrodotbuild site with @shadcn styling for plain MDX files. I used GPT6-luna on the free plan and deployed it on @Cloudflare workers.
New updates to the @doubleosafety : - Add OpenGraph tags and sitemap generation thanks to @astrodotbuild sitemap library - Make the blog post design more readable. Example: doubleoenterprises.co/blog/s… Next step: configure @EmDashCMS for the /blog
Gran Zeku here: zeku.dev
But where Framer and managed platforms will win is DFY solutions. While in frameworks, you have to fine-tine everything yourself.
Most of those takes are for views, I hope you know that. An optimistic post will never go virals, you have to create rivalry. Eventually, it all comes down to how you package it. I guess you can give me 3d models and all those stuff and I'll make it work on any platform you say
of course you can't beat a hosted platform. Same as you can never compare WordPress/WooCommerce with Shopify; not apples to apples. take a look at retubeapp.com ; its Astro, and yes I am not using any client-side pixels, yet, other than @posthog .
Not a fair comparison. A head to head comparison should require you building the same website with the same assets on both platforms and host on the same quality of host. Also, @pagepilot has client-side pixels while GrowthSync, I assume, is using server-side tracking.
Tell me why!
This test makes no sense