-
Notifications
You must be signed in to change notification settings - Fork 10
Add meta tags for twitter? #21
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
Comments
@gohai great catch! I've been reading up on how the social tags are output in Hugo. Turns out there are some internal templates that do most of the work automatically: And this website for another Hugo theme details the use of default image (kinda what discourse pic showed): Basically we need to start using "images" array in the default config file and also in the posts. If you tell me what image to use throughout the site if none is in the article/post, I can quickly add that to |
@msurguy We have a bunch of logos in https://github.com/processing/processing-pi-website/tree/master/themes/processing/static - perhaps just the most high-res one as the fallback? |
@gohai great, I'll try out the 512x512 logo that is in the folder you provided. For Facebook it is: For Twitter: So after I try out the default 512x512 image, we might need to come up with a way that will work between various networks and still produce an OK result. |
@msurguy I believe the Processing Discourse image is square and still looks reasonably good on twitter. That's all that I would shoot for, it looking okay on twitter. |
I was curious why this showed the default grey placeholder icon for the link preview, whereas the link to the Discourse showed the logo:
Turns out that there are specific meta-tags that govern this behavior. Perhaps worth modifying the hugo theme to include them? (I believe even a global, static logo - like the one displayed with the Discourse link - would be a nice touch.) What you think @msurguy?
If twitter is also picking up the more general OpenGraph tags, than it'd be probably better to make use of those.
The text was updated successfully, but these errors were encountered: