-
Notifications
You must be signed in to change notification settings - Fork 320
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
Option to disable default image functionality #5251
Comments
If you are referring to social preview, same as your question in Discussion, you can configure this in some settings https://quarto.org/docs/reference/projects/websites.html#social If you are referring to listing feature, we have some information at https://quarto.org/docs/websites/website-listings.html#listing-fields to change the image Or do you want no image at all ? |
Yes, I would like no image at all |
No image at all where ? in a Listing page ? In social preview ? |
No image in the listing and social preview.
…On Thu, 20 Apr 2023 at 13:31, Christophe Dervieux ***@***.***> wrote:
Yes, I would like no image at all
No image at all where ? in a Listing page ? In social preview ?
—
Reply to this email directly, view it on GitHub
<#5251 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAEISACFD5ZPTHOQPXRHMLDXCENCHANCNFSM6AAAAAAXFKEQVM>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Right now I don't think there is a way to disable this - the auto discovery is always finding an image. We have a couple of options:
|
Thanks @dragonstyle! I agree on the |
Using the
I was able to disable images in the listing by setting |
@nsfinkelstein We need a reproducible document to test. |
Thanks for the response. I am happy with the approach of setting |
I can reproduce this ( |
Apologies if I'm missing something, but there doesn't seem to be a way to disable Quarto from setting the image of a post to the first image. I was thinking of something like setting
image: null
in the post metadata.The text was updated successfully, but these errors were encountered: