oasis.nvim has zero images and doesn't show up as a color scheme after being posted manually to dotfyle

[uhs-robert]

I'm using my plugin as an example, but this likely impacts others as well. Something is wrong here, and I'm not sure what the root issue is. Here are the steps I took, which may have caused this issue:

1. I created a plugin that has over 28 images in the README.md and published it on GitHub
2. I posted my plugin oasis.nvim on dotfyle manually as a color scheme
3. I noticed that zero images were added to the dotfyle page
4. I waited a few days till the page showed a resync, but still no images appeared
5. Two months later, and there are still no images on the landing page/preview.
6. The plugin also doesn't show up in the color scheme section.

Meanwhile other sites like vimcolorschemes are completely functional without these issues.

Is there anything that I need to do differently in my GitHub repo to support dotfyle? Or is there any additional information that I can provide you to help resolve this issue?

[codicocodes]

There is some image parsing logic with associated unit tests, you can see if the way you store images in the Readme are covered: https://github.com/codicocodes/dotfyle/blob/eecf0bee398d20f4ad2474b28d5ef57883725c79/src/lib/server/media/parser.spec.ts

By taking a quick look at your readme and the unit tests, I don't think relative asset urls are supported currently.

[uhs-robert]

Thanks for the pointer to the tests! I was at a loss 😅. I’ve updated my README to hopefully match the parser:

• Switched all screenshots from .webp to .png.
• Replaced github.com/user-attachments/... with repo-relative links.
• Markdown images use ./assets/...

I'll wait for the next resync and see if that fixes the issue 🙏🏻

Looks like .webp extensions aren't being picked up in the relative URLs or the relative markdown links.

[uhs-robert]

@codicocodes After the weekly sync, the images have been uploaded! Thanks for your help.

However, I did notice a few other issues that I'm happy to report separately if these are things that you think would enhance the project:

1. The Media was parsed and uploaded in a random order that is inconsistent with their appearance in the README. This causes a couple of issues for authors/users when a plugin has multiple images:
   • Cover image is determined randomly (rather than defaulting to the 1st image from the top of the README) when multiple images exist.
     • e.g, It is currently using the 17th image from my README as the cover image.
   • Images that are grouped in the README appear out of order.
2. The "Social Preview" from my repo is not being parsed, and it is not being used as the cover image.
   • This is probably the ideal image to use, if it exists, for the cover image. Since it is designed for social previews, it follows a strict and predictable image dimension for website presentation and gives authors control over how the plugin appears on dotfyle.