opengraph VS tailwindcss-jit

og:*: specified by the Open Graph Protocol for social media links rendering that determine their title, description, and images when you share them on social media or chat software such as Twitter(X), Discord, etc.

OpenGraph probably.

To explore more Open Graph properties, visit this website: Open Graph Protocol.

Since Netlify introduced Edge Functions we've had an ideal way to add a tiny bit of logic into our link shortener which will return a page template of our own to anything looking to unfurl the URL to display its opengraph image.

Recoil Gunworks doesn't have an Open Graph image tag defined in their product pages, so Reddit chooses something at random to use for a preview thumbnail. Neither OP nor the mods can do anything about it.

The idea behind the Semantic Web is, if anything, the exact opposite. Yes, it's still about meaning, in the end. But in this case, it's about the authors of content (mostly webpage developers) intentionally making their content more machine-discoverable, providing links and markup and metadata that computers can read without having to do finicky and error-prone extraction. Most major sites use some features of this! As an example, if you paste this page's URL into Discord, you'll get a fancy popup box with a little snippet of the text and maybe an icon, and this is through a Facebook-developed Semantic Web extension called OpenGraph.

I found this GitHub issue where someone wants to use CSS variables for padding, like so: p-[var(--app-padding)]

Just cruised the JIT docs & code on GitHub (merged into main branch).

> add non-default variations (mostly different heights/widths than what it ships with).

Check out https://github.com/tailwindlabs/tailwindcss-jit. It got released 3 weeks ago, and supports variable variables in width and height now.

About two weeks ago, Adam Wathan announced a new Tailwind experiment: Just-In-Time. In this article, I'll tell you what it's all about, and how you can take advantage of it.

In the latest Storybook update, we finally got support for PostCSS 8. So, to celebrate this occasion, I've put together a React Storybook environment that includes everyone's favourite utility-first CSS framework: TailwindCSS. The environment also utilizes the TailwindCSS JIT compiler & Webpack 5 to bring the build times as close to instant as possible. And to top it off, the repo includes a simple GitHub action that deploys the Storybook to GitHub pages every time something is pushed.

Tailwind CSS 2.0 with the Just-in-time version

It’s not a setup issue. The JIT works differently: there’s no “purging”. And the issue I described is a known problem: https://github.com/tailwindlabs/tailwindcss-jit/issues/71

Sidestepping the broader conversation, this "JIT tool" is apparently a postcss plugin, which means you have to spawn postcss process (e.g. at every save events or have build tool do the same).

Enter @tailwindcss/jit, a drop-in replacement (though not with 100% feature parity yet) that collects the classes used by your files and only generates the requested classes.