Loading video...

Video Failed to Load

Go Home

Building SPA-like experiences with Next.js With 𝚌𝚊𝚌𝚑𝚎𝙲𝚘𝚖𝚙𝚘𝚗𝚎𝚗𝚝𝚜, the data behind a page can persist across navigations, so a revisit skips the loading fallback. Mark the read with '𝚞𝚜𝚎 𝚌𝚊𝚌𝚑𝚎' so its result is cached instead of re-queried on each render. That cache also persists in the browser, so revisiting...

29,082 views • 1 month ago •via X (Twitter)

0 Comments

No comments available

Comments from the original post will appear here

Related Videos

I built a clone of the Yeezy store with Next.js. This was a fun challenge — the site has some smooth animations and feels very fast. But it was bothering me that I couldn't use the browser back button. Can we do better? So I rebuilt the site with v0 and Motion. Here's how it works: 1. When you click on a product, Motion is able to animate the original position of the product in the grid, to the zoomed in product detail page. 2. During this transition, we also shallow update the URL with the `/p/slug` route for the page. 3. If you press the back button in the navbar, or use the browser back button, or press escape — all options will take you back to the main product listing page. 4. If you reload the page while looking at a product, or someone sends you a link to a specific product, it still works! This is the best parts of a SPA and MPA mixed together. In the future, I can make this even better with View Transitions (I wasn't able to get the product animation just right, but if you can I'd love to see it!). I also took some creative liberties from the original design. The whole 1/2/3 size thing, where you needed to click the "?" to see SM/MD/LG was strange, so I just went directly to those sizes. Similarly, I prefered the more traditional style sheet/modal with the background color change, versus the full screen takeover. If you wanted to actually hook this up to Shopify now, you can swap the cart implementation with Next.js Commerce, which has all the APIs you need + optimistic writes 🔥 Should I make a video walking through the code?

Lee Robinson

148,937 views • 1 year ago

I just built a Claude Code skill that scores whether your landing page actually keeps your Meta ad's promise 🤯 Drop in your ad and the page it points to. It reads both, scores the "ad scent" from click to page, and finds the exact line where the page breaks the promise that won the click. All inside Claude Code. Perfect for DTC brands and media buyers who pour everything into the ad and the CPA but never grade the seam in between. If you're scaling spend on a winning ad, the click is landing on a page that opens with something slightly different, the ad promised 50% off and the page shows full price, the ad hooked "for oily skin" and the page is a generic homepage, and nothing looks broken, but the visitor feels it and bounces... That gap has a name in conversion work: message match. And you already paid for the click you're losing. Here's what it does: → Drop in your ad (headline, copy, offer, CTA) and the landing-page URL → It fetches the live page and reads what's actually above the fold → Grades 7 continuity dimensions: promise, offer, angle, CTA, audience, proof, visual → Shows your ad's words next to your page's words, so every gap is right there → Rewrites your hero headline so the page keeps the ad's promise → Renders a dashboard with a Match Score out of 100 No guessing why the click bounced. No blaming the creative for a page problem. No buying more traffic to fix a copy problem. What you get: → A Match Score on every ad-to-page pair before you scale → The ad-side vs page-side quotes, side by side, for every leak → A hero rewrite you can paste straight onto the page → A dashboard you can hand to your team or client I'm giving away the full skill completely for free. Built 100% in Claude Code. No API keys. Want the skill? > Like this post > Comment "MATCH" And I'll send it over (must be following so I can DM)

Mike Futia

10,787 views • 2 months ago