Here's the demo @BenDMyers and I put together using @astrodotbuild and the Shared Element Transition API ✨
Unlike my previous demo, this one handles network latency by transitioning to a `<template>` right away, and then replacing it with the real content when it comes in.
A new meetup is coming up! Next Tuesday, July 12. With three amazing speakers!
We welcome back on stage @dtanzer who will ask "To Mock, or not to Mock?"
Well, that IS the question!
RSVP here: https://t.co/6Vw89hC1bV
Can I also use #vue for layout files in @astrodotbuild ? Otherwise it's mixing astro/preact with vue -> harder to learn :/ next trip: #fresh in @deno_land 🦕
+1 — Tailwind has had the biggest impact on the speed and quality of my fronted output lately.
❌ Spending precious energy writing styles and class names
✅ Writing your design system in tailwind.config.js, and using bradlc/vscode-tailwindcss.
It feels like printing money.
We are *very* far away from what a smart compiler can do when pre-rendering and server-rendering. A Next.js page like so:
export default () => <p>hi</hi>
should yield `<!doctype html><p>hi</p>` and not a single extra byte
If you are interested in this type of challenge DM me!