Skip to content

Conversation

@eric-burel
Copy link
Contributor

I figured the hard way that most social platforms won't actually support SVG open graph cover images, which might be confusing since we use the logo as the default cover image, and the default logo is SVG.

I've added a warning to detect this scenario, and added some documentation.

Maybe we could later improve the default setup to provide a default .png cover image directly? I've tested setting "meta.image" at tutorial level for all lessons and it works perfect, so maybe we could include a TutorialKit cover as "cover.png" and configure it directly there, rather than falling back on the logo.

@bolt-new-by-stackblitz
Copy link

Review PR in StackBlitz Codeflow Run & review this pull request in StackBlitz Codeflow.

@eric-burel eric-burel changed the title warning when using SVG open graph image doc: warning when using SVG open graph image Oct 16, 2024
@eric-burel eric-burel changed the title doc: warning when using SVG open graph image docs: warning when using SVG open graph image Oct 16, 2024
@AriPerkkio AriPerkkio requested a review from sulco October 18, 2024 08:14
@AriPerkkio
Copy link
Member

Let's host a static png/jpg on tutorialkit.dev that used by default, instead of the default logo.svg. But let's also include this warning message from this PR.

@AriPerkkio AriPerkkio changed the title docs: warning when using SVG open graph image fix: warn when using .svg in meta.image Nov 25, 2024
Copy link
Member

@AriPerkkio AriPerkkio left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good, thanks @eric-burel!

I'll do a follow-up PR that changes the default og-image to 'https://tutorialkit.dev/tutorialkit-opengraph.png' instead of logo.svg.

@AriPerkkio AriPerkkio merged commit 6e1edc1 into stackblitz:main Nov 25, 2024
13 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants