You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The problem is described here: mdn/content#5606
You can put a screenshot.png, for example, next to the index.(html|md) file and it will be picked up even though there might not be a single <img src="screenshot.png"> in the rendered and parsed HTML.
However, we only check for images. We need to support other somewhat arbitrary files too.
The text was updated successfully, but these errors were encountered:
One temporary and possible solution for mdn/content#5606 is to correct the CORS headers on that S3 serving. But we want to get away from using Kuma for the content.
The advantage of being able to check in the images into the content is self-containment. Now all the content is available offline. No need to depend on a centralized internet server.
peterbe
added a commit
to peterbe/yari
that referenced
this issue
Jun 7, 2021
The problem is described here: mdn/content#5606
You can put a
screenshot.png
, for example, next to theindex.(html|md)
file and it will be picked up even though there might not be a single<img src="screenshot.png">
in the rendered and parsed HTML.However, we only check for images. We need to support other somewhat arbitrary files too.
The text was updated successfully, but these errors were encountered: