Preview meta

[benjaminleonard]

Adds an OG image that's included only on Vercel deployments:

One downside maybe someone can chip in on is you can't import images within the vite.config file. That means that the OG image is included in the public directory and therefore even if the meta data isn't included, the image itself it. Not a big deal (only 90kb) – but certainly neater if we can remove it as part of the build process.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Updated (UTC)
console	✅ Ready (Inspect)	Visit Preview	Nov 28, 2023 10:44pm

[david-crespo]

I can rm the image as part of the build step in CI, but it might not be worth doing. I’ll think about it.

[david-crespo]

I was thinking what if we conditionally included the OG tag inside index.html and somehow referenced the image file in a way that it would be shaken out when the OG tag is not included. However:

For other use cases discussed in this issue, like conditionals we would suggest adopting a full-fledge HTML pre-processor or creating inline plugins for your projects.

vitejs/vite#3105 (comment)

Like I said I could rm it from the build tarball in the GH action that does it, but it's not a big deal. I'd rather just leave it.

Though it occurs to me... what if we left in the OG tag in production with an appropriate description?

[benjaminleonard]

Though it occurs to me... what if we left in the OG tag in production with an appropriate description?

My hesitation with that is that it's nice to preserve the idea that the rack is yours – part of the reason I've avoided too much branding on the console. If we were feeling fancy in the future we could use a templated design but swap the text out for the silo name at build time. Scratch that, that's not how it works. But in theory if we did have node on the the rack we could do it server side.