It happened! I’ve open sourced my exif-based photo blog as a (near) zero-config @vercel template. It uses all the things: ◆ Next.js App Router with Server Actions ◆ Next.js Image ◆ Next Auth ◆ Vercel Postgres ◆ Vercel Blob ◆ Vercel OG Template →

@JohnPhamous omg the ultimate employer perk

@JohnPhamous Unrelatedly, is Rodent in Residence a job?

@argyleink Agreed it's totally wild. Recently added an image viewer to my photo template and went with viewerjs because it was my best and also my only option?

@pranathiperii @joebell_ FACTS

@adamwathan Amazing! Favorite part of css-based config btw: native keyframes. Think part of me resisted tailwind animation classes because I dreaded defining them in JSON? Also, I'm now shipping 1 css file instead of 2 and total size went from 90k to 70k. So good.

Tailwind's migration utility is SO good. Would not have shipped this tonight without it.

@soleio Can confirm—as a parent—I'm an accelerant here, and don't feel great about it? But also struggle with the alternatives.

Specifically, is the at-apply usage in `tailwind.css` still kosher?

@mattgperry Any chance this could be used to support Next.js App Router page-level exit animations? Plz ignore if you're sick of hearing this question!

@mamuso 🖤

@gennyxdavila @prekesh__ a designer's highest calling

When do we get tailwind representation?

@styfle 🖤

yes album to the right is Sing dont at me