What's the benefit of using this one vs the other native to Astro?

[adriangalilea]

I've seen a few OG image generators, is there any reason why you pref satori over those?

Just curious before I implement any, thank you.

[florian-lefebvre]

I think there are 2 cases really:

1. You don't need much customization, go for https://github.com/delucis/astro-og-canvas/tree/latest/packages/astro-og-canvas
2. You need a fully custom OG image, use this integration

[adriangalilea]

How well would this play with Astro content collections?

[florian-lefebvre]

It works well! After all, you can have such a setup:

• an endpoint for the og image
• getStaticPaths based on a collection that returns some props
• use that props in the endpoint to pass those to your satori template (for example as a component prop)

This package's API is pretty flexible but it has nothing built-in for content collections. It can be done easily with some basic Astro knowledge