You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi all — I’m exploring a small API that generates OG images for docs, changelogs, and release notes from metadata instead of manual screenshots or custom templates.
I’m trying to validate whether this is a real pain point for content-heavy VitePress sites.
A few concrete questions:
Do you currently generate social preview images manually, with screenshots, or with a custom script?
For docs / changelog pages, would a simple HTTP API that returns a ready-to-use og:image PNG be useful?
What would block adoption most: design flexibility, caching, self-hosting, or reliability?
I’m not pitching a finished SaaS here — just trying to learn whether this problem is painful enough to solve properly. If anyone is open to sharing how you handle OG images today, I’d really appreciate it.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Hi all — I’m exploring a small API that generates OG images for docs, changelogs, and release notes from metadata instead of manual screenshots or custom templates.
I’m trying to validate whether this is a real pain point for content-heavy VitePress sites.
A few concrete questions:
og:imagePNG be useful?I’m not pitching a finished SaaS here — just trying to learn whether this problem is painful enough to solve properly. If anyone is open to sharing how you handle OG images today, I’d really appreciate it.
All reactions