-
Notifications
You must be signed in to change notification settings - Fork 102
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
All pages should have OG metadata, for social sharing #303
Comments
@joeytwiddle I test the link https://eventyay.com/e/fa96ae2c/schedule on https://cards-dev.twitter.com/validator but it is displaying this- |
@joeytwiddle Can i work on this issue? |
@rohit-raje-786 It's not really my decision, but I have no objections. 😄 Some things to consider:
|
working on this issue. |
Hey, I would like to work on this issue |
Please go ahead. |
Hey , wanna work on this issue please assign it to me |
We don't assign issues to external contributors. Please comment that you're working on the issue after checking that no one else is, and then send a pull request for it. Thank You! |
ok |
When people share links in social media, some of them are very plain, and do not become an attractive card with an image.
For example in Telegram (and WhatsApp), there is no image, just a boring blue text link:
What I wish for: When sharing on social media, there should be enough metadata provided for the service to generate an attractive thumbnail with a title.
For example, something like this:
Even if we don't use an image specific to the conference, any image is better than no image. (Eventyay's logo would be good enough, if no other image was available.)
This page on CSS-Tricks explains that the following tags are needed:
These tools can help to test if it's working:
https://developers.facebook.com/tools/debug/?q=https%3A%2F%2Feventyay.com%2Fe%2Ffa96ae2c%2Fschedule
https://cards-dev.twitter.com/validator
I tested with this link: https://eventyay.com/e/fa96ae2c/schedule But ideally this should be done for all pages. Because a user may share any page. And it's (almost?) always desirable to make the shared link clear and attractive.
The text was updated successfully, but these errors were encountered: