quarto-dev / quarto-dev/quarto-cli
`image-placeholder` on listing page not copied into `_site` folder
@cscheid is already working on this.
Since Sep 9, 2024.
- Dominant language
- JavaScript
- Stars
- 6k
- Forks
- 458
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 41
Description
Bug description
A listing page with an image-placeholder set in the header yaml does not work, because quarto does not automatically find the image and copy it to _site when rendering. A workaround is to explicitly set resources: "*.png" in the _quarto.yml file, but my expectation is that Quarto should find this resource on its own.
Steps to reproduce
MRE repo (with the workaround resources: "*.png" line commented out) is here
Expected behavior
The image should be copied into _site and the listing page should render properly.
Actual behavior
The image resource is not copied into _site and the place holder image does not display.
Your environment
VS Code, MacOS X Sonoma 14.5
Quarto check output
Quarto 1.5.57
[✓] Checking versions of quarto binary dependencies...
Pandoc version 3.2.0: OK
Dart Sass version 1.70.0: OK
Deno version 1.41.0: OK
Typst version 0.11.0: OK
[✓] Checking versions of quarto dependencies......OK
[✓] Checking Quarto installation......OK
Version: 1.5.57
Path: /Applications/quarto/bin
[✓] Checking tools....................OK
TinyTeX: v2023.09
Chromium: (not installed)
[✓] Checking LaTeX....................OK
Using: TinyTex
Path: /Users/marcosh/Library/TinyTeX/bin/universal-darwin
Version: 2023
[✓] Checking basic markdown render....OK
[✓] Checking Python 3 installation....OK
Version: 3.10.14 (Conda)
Path: /usr/local/opt/miniforge3/bin/python
Jupyter: 5.7.2
Kernels: py311, sentencet, python3
[✓] Checking Jupyter engine render....OK
[✓] Checking R installation...........OK
Version: 4.3.1
Path: /Library/Frameworks/R.framework/Resources
LibPaths:
- /Library/Frameworks/R.framework/Versions/4.3-arm64/Resources/library
knitr: 1.44
rmarkdown: 2.25
[✓] Checking Knitr engine render......OK
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.