Frontend

walletbeat

Thanks to the hard work of @darrylyeo, https://beta.walletbeat.eth.limo has moved from Next.js to Astro!
Snappier, more optimized pages, and faster rebuilds.

Next.js → Astro migration successful! 🚀

https://github.com/fluidkey/walletbeat/pull/104

https://warpcast.com/polymutex.eth/0xdea98ef2

/frontend dev・founder/decentralized data wrangler /blockhead・UI/UX abstractionist・DeFi/web3 builder・dropout・24・prev /dydx, ritual.net・x.com/darryl__yeo

@day---break, day---break.com // nf.td/iam

React Native Developer. Experimenting with consumer apps.

repo is out of date, but it's pretty straight forward

father, husband, css golfer, ux engineer, silently defining variables as /sdv sdv.wtf

repo is out of date, but it's pretty straight forward https://github.com/iammatthias/simple-astro-frame

that's a v1 frame right? I know nothing about v2, so idk how different it is

yeah, this is v1. @stevedylandev.eth has a solid v2 tutorial that should work nicely for Astro

DX Engineer | Head of Developer Relations at /pinata | Building orbiter.host | stevedylan.dev/links

yeah, this is v1. @stevedylandev.eth has a solid v2 tutorial that should work nicely for Astro https://orbiter.host/blog/how-to-deploy-a-v2-frame-on-orbiter

Yup! I need to experiment more with a rudimentary V2 Astro frame. Our marketing site is a minimal V2 frame but I’d like to add more functionality using the SDK, which might just end up being a react component inside Astro

Astro recommends against using <head> in a component, but you could probably get away with astro-seo or astro-capo (or both?) at the page level. Or just pass it all up to your layout? Been meaning to mess with this, but it keeps getting kicked down the road. https://docs.astro.build/en/guides/troubleshooting/#using-head-in-a-component
https://github.com/jonasmerlin/astro-seo
https://github.com/natemoo-re/astro-capo

Oh yeah totally. The meta tag and the manifest are pretty easy, it’s just using the SDK to send a ready signal that I haven’t messed with much. I used a cheat from @horsefacts.eth here: https://github.com/orbiterhost/marketing-site/blob/main/src/pages/index.astro#L16-L42

However I think it could be as simple as using the CDN or packaged SDK in a script tag similar to what @samuellhuber.eth did here:

Oh yeah totally. The meta tag and the manifest are pretty easy, it’s just using the SDK to send a ready signal that I haven’t messed with much. I used a cheat from @horsefacts.eth here: https://github.com/orbiterhost/marketing-site/blob/main/src/pages/index.astro#L16-L42

However I think it could be as simple as using the CDN or packaged SDK in a script tag similar to what @samuellhuber.eth did here: https://github.com/dtechvision/simplest-farcaster-frame/blob/master/index.html#L34-L37

honestly I don't mind having react islands, I still think that using astro as a react framework is worth it